The mailing list for listmasters using Sympa

["Silvers, Tim" <address@concealed>]

Hi Stefan,

 

Thank you for the quick response. Attached are the log entries from the crash. I see the email address of the sender in the log prior to the crash event [1]. The subscriber is no longer a member of the list. He had received an email Feb 19 15:11:21, which was a few hours prior to the attempt to unsubscribe and the subsequent Sympa service crash. The database is hosted on a separate server and it was up at the time.

 

Let me know if I can provide anything else. I can also provide a copy of the bad message with full headers directly to you if you or other Sympa developers would like to examine it.

 

[1] “…Unable to gather information for user: address@concealed...

…DIED: bug in logic. Ask developer at /usr/share/sympa/lib/Sympa/Database.pm line 439….”

 

 

Thank you,

 

Tim

 

From: address@concealed <address@concealed> on behalf of Stefan Hornburg (Racke) <address@concealed>
Date: Tuesday, February 22, 2022 at 1:25 AM
To: address@concealed <address@concealed>
Subject: [External] Re: [sympa-users] Bad message caused Sympa crash

On 21/02/2022 14:40, Silvers, Tim wrote:
> Hi. We recently experienced a Sympa service crash due to receiving a bad message. It appears to have been generated by from iPhone by a user initiating Apple’s safe unsubscribe feature, as indicated by the header and the body content [1].
>
> The email was removed from the spool and Sympa was able to be started. Before removing the email, Sympa would simply silently fail to start, but there were errors in the logs (see attached) and in the journalctl output. It was just odd that SystemD in our CentOS 7 install didn’t indicate a failure.
>
> Anyway, I am providing these details because these “safe unsubscribe” features are more pervasive now in many clients and I wonder if others have experienced any issues due to these unsubscribe requests, and whether this is something Sympa can address? It’s probably more of a fault of the clients sending these and hitting mailing list services that handle unsubscribe requests differently, so more of a client issue than a Sympa issue. But I honestly don’t know why this message would crash Sympa. I will say that I can open the email in Apple’s Mail client on my Mac, but Outlook crashes each time I try to open it. Also, the email was sent to the service address with no command. I thought Apple’s client might have attempted to send to the listname-unsubscribe@domain address to request removal, as it is in the headers of emails sent from Sympa, but alas, it did not.
>
> An interesting issue, for sure.
>
> [1] X-Mailer: iPhone Mail (19C63)
>
> Apple Mail sent this email to unsubscribe from the message =E2=80=9CFresh Eg=
>
> gs for Sale=E2=80=9D.=
>

It would be useful to see the crash error messages from the Sympa log ...

Regards
         Racke

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

Feb 19 17:58:35 list-app sympa_msg[1746]: err main::#243 > 
Sympa::Spindle::spin#95 > Sympa::Spindle::DoCommand::_twist#120 > 
Sympa::Spindle::spin#95 > Sympa::Request::Handler::signoff::_twist#74 > 
Sympa::List::delete_list_member#1561 > Symp
a::List::insert_delete_exclusion#1887 > Sympa::List::get_list_member#2094 > 
Sympa::Database::do_prepared_query#361 Unable to get a handle to sympa 
database
Feb 19 17:58:35 list-app sympa_msg[1746]: err main::#243 > 
Sympa::Spindle::spin#95 > Sympa::Spindle::DoCommand::_twist#120 > 
Sympa::Spindle::spin#95 > Sympa::Request::Handler::signoff::_twist#74 > 
Sympa::List::delete_list_member#1561 > Symp
a::List::insert_delete_exclusion#1887 > Sympa::List::get_list_member#2109 
Unable to gather information for user: address@concealed
Feb 19 17:58:35 list-app sympa_msg[1746]: err main::#243 > 
Sympa::Spindle::spin#95 > Sympa::Spindle::DoCommand::_twist#120 > 
Sympa::Spindle::spin#95 > Sympa::Request::Handler::signoff::_twist#74 > 
Sympa::List::delete_list_member#1621 > Sympa::Database::commit#439 DIED: bug 
in logic. Ask developer at /usr/share/sympa/lib/Sympa/Database.pm line 439.
Feb 19 17:58:35 list-app systemd: sympa.service: main process exited, 
code=exited, status=255/n/a
Feb 19 17:58:35 list-app systemd: Unit sympa.service entered failed state.
Feb 19 17:58:35 list-app systemd: sympa.service failed.
Feb 19 17:58:35 list-app archived[1770]: notice main::sigterm() Signal TERM 
received, still processing current task
Feb 19 17:58:35 list-app systemd: Stopping Sympa mailing list manager 
(archiving)...
Feb 19 17:58:35 list-app archived[1770]: notice main:: Archived exited 
normally due to signal
Feb 19 17:58:35 list-app systemd: Stopping Sympa mailing list manager (bounce 
processing)...
Feb 19 17:58:35 list-app bounced[1769]: notice main::sigterm() Signal TERM 
received, still processing current task
Feb 19 17:58:35 list-app systemd: Stopping Sympa mailing list manager (task 
management)...
Feb 19 17:58:35 list-app bounced[1769]: notice main:: Bounced exited normally 
due to signal
Feb 19 17:58:35 list-app systemd: Stopping Sympa mailing list manager 
(message distribution)...
Feb 19 17:58:35 list-app bulk[1768]: notice main::sigterm() Signal TERM 
received, still processing current task
Feb 19 17:58:35 list-app bulk[1768]: notice main:: Bulk exited normally due 
to signal
Feb 19 17:58:35 list-app task_manager[1748]: notice main::sigterm() Signal 
TERM received, still processing current task
Feb 19 17:58:35 list-app task_manager[1748]: notice main:: Task_Manager 
exited normally due to signal
Feb 19 17:58:35 list-app bulk[3695]: notice main::sigterm() Signal TERM 
received, still processing current task
Feb 19 17:58:35 list-app bulk[3695]: notice main:: Bulk exited normally due 
to signal
Feb 19 17:58:35 list-app bulk[3690]: notice main::sigterm() Signal TERM 
received, still processing current task
Feb 19 17:58:35 list-app bulk[3690]: notice main:: Bulk exited normally due 
to signal
Feb 19 17:58:35 list-app bulk[3687]: notice main::sigterm() Signal TERM 
received, still processing current task
Feb 19 17:58:35 list-app bulk[3687]: notice main:: Bulk exited normally due 
to signal
Feb 19 17:58:36 list-app systemd: Stopped Sympa mailing list manager (bounce 
processing).
Feb 19 17:58:36 list-app systemd: Stopped Sympa mailing list manager (message 
distribution).
Feb 19 17:58:36 list-app systemd: Stopped Sympa mailing list manager 
(archiving).
Feb 19 17:58:36 list-app systemd: Stopped Sympa mailing list manager (task 
management).



/log/store/sympa/arch/sympa.local1.2022.02.19.log.gz:Feb 19 17:58:35 list-app 
sympa_msg[1746]: notice Sympa::Spindle::ProcessIncoming::_twist() Processing 
Sympa::Message <address@concealed>; 
address@concealed; 
address@concealed; 
address@concealed
/log/store/sympa/arch/sympa.local1.2022.02.19.log.gz:Feb 19 17:58:35 list-app 
sympa_msg[1746]: notice Sympa::Spindle::ProcessMessage::_twist() Processing 
Sympa::Request 
<action=signoff;address@concealed;address@concealed>
/log/store/sympa/arch/sympa.local1.2022.02.19.log.gz:Feb 19 17:58:35 list-app 
sympa_msg[1746]: err main::#243 > Sympa::Spindle::spin#95 > 
Sympa::Spindle::DoCommand::_twist#120 > Sympa::Spindle::spin#95 > 
Sympa::Request::Handler::signoff::_twist#74 > 
Sympa::List::delete_list_member#1561 > 
Sympa::List::insert_delete_exclusion#1887 > Sympa::List::get_list_member#2109 
Unable to gather information for user: address@concealed