The mailing list for listmasters using Sympa

["Stefan Hornburg (Racke)" <address@concealed>]

On 19/05/2022 13:51, Goltz, Immo wrote:
> Hello Racke,
>
> no, this does not fix this problem.
>
> Still get
> sympa  move -d --log_level=3 ...
> Unknown robot ...
> Even with debug no more output.

Hello Immo,

can you show the contents of your robot.conf?

Which log are you looking at? I noticed that on my setup the logs from the 
CLI actions ends up
in the syslog instead of sympa.log.

Regards
        Racke

> Mit freundlichen Grüßen
>
> Immo Goltz
>
> IT-Systemmanager / Bereich 71 Informationstechnik
> Goethe-Institut Zentrale
> Oskar-von-Miller-Ring 18
> 80333 München
> Deutschland
> Tel.: +49 89 15921 642
> Email: address@concealed
> Homepage: www.goethe.de
>
>
> ________________________________________
> Von: address@concealed <address@concealed> 
> im Auftrag von Stefan Hornburg (Racke) <address@concealed>
> Gesendet: Mittwoch, 18. Mai 2022 07:14
> An: address@concealed
> Betreff: [EXTERN] Re: [sympa-users] creating new robot/vhost issue
>
> On 17/05/2022 14:11, Goltz, Immo wrote:
> > Dear list,
> >
> > I am quite sure creating a robot worked this way (last done some months ago):
> >
> > 1. create robot domain say newsletter.example.com in /etc/sympa
> > 2. inside create file robot.conf with listmaster, title, wwsympa_url entries
> > 3. restart sympa, wwsympa
> >
> > Now on 6.2.68 this does not work.
> >
> > After steps 1-3 I tried to:
> > sympa move --mode=copy address@concealed address@concealed
> > which gave error:
> > Unknown robot "newsletter.example.com"
>
> Hello Immo,
>
> the new commandline interface introduced with 6.2.68 is in fact buggy. Please 
> check if https://github.com/sympa-community/sympa/pull/1344 fixes your 
> problem.
>
> Regards
>             Racke
>
> > Then pointed browser to https://newsletter.example.com/sympa/ which worked 
> > fine! Tried to create an account which gave no error in the gui and log:
> > May 17 13:32:03 sympa-server wwsympa[359166]: info 
> > main::do_requestpasswd(address@concealed) [robot newsletter.example.com] 
> > [session 45672154794598] [client IP]
> >
> > May 17 13:32:03 sympa-server wwsympa[359166]: notice 
> > Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template 
> > <address@concealed,793>; 
> > address@concealed; 
> > address@concealed; 
> > address@concealed; address@concealed; 
> > template=sendpasswd; action=requestpasswd; reason=firstpasswd
> > May 17 13:32:03 sympa-server wwsympa[359166]: notice Sympa::Spool::Outgoing::store() 
> > Message Sympa::Message::Template 
> > <address@concealed,793> is stored into bulk spool as 
> > <address@concealed,359166,8230>
> >
> > But the mail never left sympa instead ended up in 
> > /var/spool/sympa/bulk/bad/msg . No entry (even with debug3) in sympa log.
> > Fetching the password set link from the "bad" message I was able to create 
> > the account, login and create a new list. Once this was done sympa move worked, 
> > creating accounts worked (password mail was sent).
> >
> > Is this a regression in Sympa 6.2.28 or did I forget something needed beyond 
> > steps 1-3?
> >
> > Thank you in advance,
> > Immo
>
>
> --
> Automation expert - Ansible and friends
> Linux administrator & Debian maintainer
> Perl Dancer & conference hopper


--
Automation expert - Ansible and friends
Linux administrator & Debian maintainer
Perl Dancer & conference hopper

Attachment: OpenPGP_signature
Description: OpenPGP digital signature