The mailing list for listmasters using Sympa

["Goltz, Immo" <address@concealed>]

Dear Sympa list,

I have trouble with firstpasswd / renewpasswd function and robots aka virtual 
domains.
These mails silently ending up in bad/msg spool. However distributing 
mailings in lists works well.

I am on CentOS7 and had Sympa 6.2.48-2.el7 installed from epel. Upgrading 
(6.2.62-1.el7) did not solve it.
Probably only a configuration error I cannot find.

Configuration is like this:
sympa.conf
domain         sympasoap11-dev
wwsympa_url    http://sympasoap11-dev/sympa

listen-dev/robot.conf
domain         listen-dev # this was not defined here but adding it had no 
efffect
http_host      listen-dev
wwsympa_url    http://listen-dev/sympa


Requesting the first passwword in webgui gives success message. So I guess 
logs from wwsympa process are not relevant thus just posting bulk process 
ones.

Password mails reuested via http://sympasoap11-dev/sympa/firstpasswd will be 
send. Sympa log:
bulk: debug3 Sympa::Spool::unmarshal_metadata(/var/spool/sympa/bulk/pct, 
1.5.1623313318.1623313318.125935.sympa@sympasoap11-dev_s,7598,3589/s, 
qr<(?^:\A(\w+)\.(\w+)\.(\d+)\.(\d+\.\d+)\.(\@?[^\s\@]*)\@([\w\.\-*]*)_(\w+),(\d+),(\d+)/(\w+)\z)>)
bulk: debug3 Sympa::Spool::unmarshal_metadata() 
messagekey=1.5.1623313318.1623313318.125935.sympa@sympasoap11-dev_s,7598,3589/s,
 context=sympasoap11-dev, priority=1
bulk: debug2 Sympa::Message::new(Sympa::Message, ...)
bulk: err main::#160 > Sympa::Spindle::spin#78 > 
Sympa::Spool::Outgoing::next#151 > Sympa::Message::new_from_file#236 > 
Sympa::Message::new#169 > Sympa::Message::_get_sender_email#294 Invalid 
sender address "sympa@sympasoap11-dev"
bulk: notice Sympa::Spindle::ProcessOutgoing::_twist() Start sending message 
Sympa::Message 
<1.5.1623313318.1623313318.125935.sympa@sympasoap11-dev_s,7598,3589/s> to 
sympasoap11-dev (priority 1) (starting 0 seconds after scheduled expedition 
date)
bulk: debug3 Sympa::Mailer::store() Open = 0
bulk: notice Sympa::Mailer::store() Done sending message Sympa::Message 
<1.5.1623313318.1623313318.125935.sympa@sympasoap11-dev_s,7598,3589/s> for 
sympasoap11-dev (priority 1) in 1 seconds since scheduled expedition date
bulk: debug2 Sympa::Process::_reap_child() Child process 7650 for 
<1.5.1623313318.1623313318.125935.sympa@sympasoap11-dev_s,7598,3589/s> exited 
normally


But via http://listen-dev/sympa/firstpasswd they end up in bas/msg spool. 
Sympa log:
bulk: debug3 Sympa::Spool::unmarshal_metadata(/var/spool/sympa/bulk/pct, 
1.5.1623313193.1623313193.813330.sympa@listen-dev_s,7596,8772/s, 
qr<(?^:\A(\w+)\.(\w+)\.(\d+)\.(\d+\.\d+)\.(\@?[^\s\@]*)\@([\w\.\-*]*)_(\w+),(\d+),(\d+)/(\w+)\z)>)
bulk: debug3 Sympa::Spool::unmarshal_metadata() 
messagekey=1.5.1623313193.1623313193.813330.sympa@listen-dev_s,7596,8772/s, 
context=*, priority=1

And the spool directory:
/var/spool/sympa/bulk/bad/msg
1.5.1623313193.1623313193.813330.sympa@listen-dev_s,7596,8772


Maybe the behavior is triggered here:
In a robot Sympa::Spool::unmarshal_metadata set's context=* where in the main 
site context=sympasoap11-dev is set.

What do I wrong in configuring robots?

Thank you in advance!
Cheers,
Immo