Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to request or reset lists passwords #1936

Open
GingkoFr opened this issue Feb 6, 2025 · 1 comment
Open

Unable to request or reset lists passwords #1936

GingkoFr opened this issue Feb 6, 2025 · 1 comment
Labels

Comments

@GingkoFr
Copy link

GingkoFr commented Feb 6, 2025

Version

Sympa, version 6.2.70, running on Linux Debian 12 (bookworm)

Installation method

Installed from Debian native packages, using apt or apt-get.
I have about 15 mailing-lists, there, using 6 different domains, mostly migrated from a previous Mailman 2 obsolete installation, with different levels of activity.
Some of them are there only for testing purposes.
The widest one have about 1650 members.

Messages are sent using the Postfix software (version 3.7.11-0).

Expected behavior

On these mailing lists, I have several users, moderators or owners who tried to create or request a new password, using the web interface.

Each time, they get a message saying that an email has been sent to them, allowing to define a new password, and asking them to check their mailbox.

Of course, these emails are expected to have been sent.

Actual behavior

Actually they receive absolutely nothing.
I checked myself with my own emails, and the result is the same: I do not receive anything.

Additional information

If I read my Postfix log files, I cannot find anything around the requesting time suggesting that something has been sent, not sent or even just tried.
But if any email is sent to the list, I can properly see there the log lines corresponding to all messages sent to all users.

This is true for all of the domains on which I tried this feature.

If I read the Sympa log files (which is defined with log_level 0) I can read the following, added on that time (private data has been munged) :

Jan 17 20:13:02 srv5 wwsympa[3718023]: info main::do_requestpasswd(the_email@to_request.org) [robot listdomain.fr] [session 32352707980684] [client 2a01:<my server ipv6 address>:7d39]
Jan 17 20:13:02 srv5 wwsympa[3718023]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template ; [email protected]; [email protected]; recipients=the_email@to_request.org; [email protected]; template=sendpasswd; action=requestpasswd
Jan 17 20:13:02 srv5 wwsympa[3718023]: notice Sympa::Spool::Outgoing::store() Message Sympa::Message::Template  is stored into bulk spool as <[email protected]_s,3718023,7352>
Jan 17 20:13:02 srv5 wwsympa[3718023]: notice Sympa::WWW::Tools::_get_css_url() Template file /usr/share/sympa/default/web_tt2/css.tt2 or configuration has changed; updating CSS file /var/lib/sympa/css/listdomain.fr/style.css

This does not contain any information telling if the message has been sent or not sent.

Increasing the log level adds a lot of garbage, but nothing that seems more significant.

I notice, however, in the middle of these logs, several “sender” addresses like [email protected] or [email protected] which are likely not valid.
They should likely be [email protected] or [email protected].
listes.listdomain.fr is the web server domain, but list related emails should only end by @listdomain.fr.
I don't know how to change that.

Messages are expected to be DKIM signed.

It seems to me that it did worked a little on the past, however, as otherwise I couldn't have created my own administrative passwords.

Please could you tell me what I did wrong, and how I can allow my list users, moderators and owners to create or request a password on their emails in order to access the list web interface?

Previous attempt for getting help

I previously tried to ask this question on the community list at [email protected] on a topic where messages had "Unable to request or reset lists passwords" in their subjects.
But after several answers, I'm still stuck with the same problem.
You should be able to read this discussion there : https://lists.sympa.community/arc/en/2025-01/

However I got there, or after, the following additional information:

Another user had the following log data on similar requests, where this was working for him:

Jan 21 11:42:42 mail.server wwsympa[1591]: info main::do_renewpasswd() [robot lists.domain.org] [session 77894897859517] [client 123.456.789.10]
Jan 21 11:43:09 mail.server wwsympa[1591]: info main::do_requestpasswd([email protected]) [robot lists.domain.org] [session 77894897859517] [client 123.456.789.10]
Jan 21 11:43:13 mail.server syslogd: last message repeated 1 times
Jan 21 11:43:13 mail.server wwsympa[1591]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <[email protected],2325>; [email protected]; [email protected]; [email protected]; [email protected]; template=sendpasswd; action=requestpasswd
Jan 21 11:43:13 mail.server wwsympa[1591]: notice Sympa::Spool::Outgoing::store() Message Sympa::Message::Template <[email protected],2325> is stored into bulk spool as <[email protected]_s,1591,322>
Jan 21 11:43:13 mail.server bulk[3020]: notice Sympa::Spindle::ProcessOutgoing::_twist() Start sending message Sympa::Message <[email protected]_s,1591,322/s> to lists.domain.org (priority 1) (starting 0 seconds after scheduled expedition date)
Jan 21 11:43:13 mail.server bulk[3020]: notice Sympa::Mailer::store() Done sending message Sympa::Message <[email protected]_s,1591,322/s> for lists.domain.org (priority 1) in 0 seconds since scheduled expedition date
Jan 21 11:43:46 mail.server wwsympa[1591]: info main::do_arc(2008-12, msg00017.html) [robot lists.domain.org] [session 02115510855952] [client 54.36.149.80] [list pho-postfix]

... meaning that mine stops after the line containing "notice Sympa::Spool::Outgoing::store()".
Note that on this line, I have missing tokens between "Template" and "is stored" (but two spaces between).

All of my Sympa services are properly running if I do "systemctl status 'sympa*'".

If I look inside the /var/spool/sympa/bulk/bad/msg/ directory, I can find files containing all of the emails which should have been sent, but have been dumped there instead.

I may suspect some permission problems, but how can I locate them without any log reporting this?

Regards.

@ikedas
Copy link
Member

ikedas commented Feb 11, 2025

Hi @GingkoFr ,

Please read through the documentaion and make sure you set up correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants