Skip to Content.
Sympa Menu

en - Re: [sympa-users] [External] Re: Bad message caused Sympa crash

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "Silvers, Tim" <address@concealed>
  • To: "Stefan Hornburg (Racke)" <address@concealed>, "address@concealed" <address@concealed>
  • Subject: Re: [sympa-users] [External] Re: Bad message caused Sympa crash
  • Date: Tue, 8 Mar 2022 20:48:57 +0000

Stefan,

 

I should mention that we have been able to replicate this same behavior in our non-production environment. We can conduct further testing there and even test with the log level set higher if needed. Let us know what we can provide or do to help resolve this issue.

 

Thanks,

 

Tim

 

From: address@concealed <address@concealed> on behalf of Silvers, Tim <address@concealed>
Date: Monday, March 7, 2022 at 1:55 PM
To: Stefan Hornburg (Racke) <address@concealed>, address@concealed <address@concealed>
Subject: Re: [sympa-users] [External] Re: Bad message caused Sympa crash

Stefan,

 

Another couple of events over the weekend. Attached are the logs. Both emails that were received prior to the crashes were unsubscribe requests. Again, as with other incidents, one was from Gmail and one was from an iPhone/iOS device. One had ‘unsubscribe’ in the subject and one had ‘sig’ in the subject, both followed by the list names from which the subscribers wished to be removed. And in both cases, the subscribers were removed from the lists.

 

Tim

 

From: address@concealed <address@concealed> on behalf of Silvers, Tim <address@concealed>
Date: Tuesday, March 1, 2022 at 1:10 PM
To: Stefan Hornburg (Racke) <address@concealed>, address@concealed <address@concealed>
Subject: Re: [sympa-users] [External] Re: Bad message caused Sympa crash

Hi Stefan,

 

Right. I should have included the version. It is 6.2.68. We didn’t have this issue with the prior version, 6.2.64. The upgrade was performed Feb 13. The log level has been changed to 2 from zero. Is that going to be an acceptable level? If not, let me know.

 

Tim

 

From: Stefan Hornburg (Racke) <address@concealed>
Date: Tuesday, March 1, 2022 at 11:19 AM
To: Silvers, Tim <address@concealed>, address@concealed <address@concealed>
Subject: Re: [sympa-users] [External] Re: Bad message caused Sympa crash

On 01/03/2022 17:11, Silvers, Tim wrote: > Stefan, > > We experienced another service crash yesterday evening. Again, it was an unsubscribe request from an iPhone. The log error was the same as the previous two incidents. Let me know if you need further details. > > Tim Hello Tim, which Sympa version do you use? That would be helpful to relate the lines from the logs with the source code. Also can you raise the log level so next time we get more information. Regards Racke > > *From: *address@concealed on behalf of Silvers, Tim > *Date: *Monday, February 28, 2022 at 9:42 AM > *To: *Stefan Hornburg (Racke) , address@concealed > *Subject: *Re: [sympa-users] [External] Re: Bad message caused Sympa crash > > Stefan (Sympa team), > > Another crash occurred over the weekend. Again, it was a bad message with an unsubscribe request. This one did not come from an iOS or Mac client, as far as I can tell. Again, it complains about the same line in /usr/share/sympa/lib/Sympa/Database.pm, which is from the ‘commit’ subroutine. > > Feb 27 06:23:45 list-app sympa_msg[29853]: info Sympa::List::delete_list_member() Unable to remove list member address@concealed from list Sympa::List : Not on list > > Feb 27 06:23:45 list-app sympa_msg[29853]: 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 27 06:23:45 list-app sympa_msg[29853]: info Sympa::List::delete_list_member() Unable to remove list member address@concealed from list Sympa::List : Not on list > > Feb 27 06:23:45 list-app sympa_msg[29853]: 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. > > Tim > > *From: *address@concealed on behalf of Silvers, Tim > *Date: *Tuesday, February 22, 2022 at 8:53 AM > *To: *Stefan Hornburg (Racke) , address@concealed > *Subject: *Re: [sympa-users] [External] Re: Bad message caused Sympa crash > > 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 on behalf of Stefan Hornburg (Racke) > *Date: *Tuesday, February 22, 2022 at 1:25 AM > *To: *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 > -- Automation expert - Ansible and friends Linux administrator & Debian maintainer Perl Dancer & conference hopper




Archive powered by MHonArc 2.6.19+.

Top of Page