-
Notifications
You must be signed in to change notification settings - Fork 103
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
Mail loop with sympa-request address because of misconfiguration #957
Comments
my mailq indicates multiples mails : 6273D23F* 3553 Thu Jun 11 09:49:24 MAILER-DAEMON 0E8A223B* 3552 Thu Jun 11 09:49:23 MAILER-DAEMON 9AB86242* 3553 Thu Jun 11 09:49:24 MAILER-DAEMON 7A1CC236* 3553 Thu Jun 11 09:49:24 MAILER-DAEMON 1DD8B197* 3552 Thu Jun 11 09:49:23 MAILER-DAEMON 3F09523C* 3553 Thu Jun 11 09:49:24 MAILER-DAEMON 2398622D* 3553 Thu Jun 11 09:49:23 MAILER-DAEMON CFAA421C 3552 Thu Jun 11 09:49:24 MAILER-DAEMON -- 33 Kbytes in 9 Requests. |
@jth56000 , |
What is the change in mail server configuration between 6.2.52 and 6.2.54 ?
I can provide you my postfix main.cf and master.cf, I did not touch to them during my migration.
I can also provide my sympa.conf if that can help.
Jean
<https://github.com/jth56000> @jth56000 ,
Have you read the chapter " <https://sympa-community.github.io/manual/install/configure-mail-server.html> Configure mail server" in the administration manual?
If you have done, please show us all of settings (for Sympa along with mail server) described in corresponding sections of this chapter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#957 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMTAPYBTCFLUMSHDXKFRYADRWCFS5ANCNFSM4N3DHDBQ> . <https://github.com/notifications/beacon/AMTAPYCFWXGV7ADGK7FN6TTRWCFS5A5CNFSM4N3DHDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZFYE6I.gif>
|
First of all please show us these: |
Addition: |
Here are the requested files.
De : IKEDA Soji <notifications@github.com>
Envoyé : jeudi 11 juin 2020 10:20
À : sympa-community/sympa <sympa@noreply.github.com>
Cc : THOMAS Jean <jean.thomas@ext.dsi.cnrs.fr>; Mention <mention@noreply.github.com>
Objet : Re: [sympa-community/sympa] Issue when upgrade from 6.2.52 to 6.2.54 : (#957)
Addition: list_aliases.tt2. And recently added lines of aliases file (the location is speficied by sendmail_aliases parameter).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#957 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMTAPYGIZHMHZCEJCUQQTB3RWCHRPANCNFSM4N3DHDBQ> . <https://github.com/notifications/beacon/AMTAPYFSBU4EABTM5MY6HJ3RWCHRPA5CNFSM4N3DHDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZF2EBA.gif>
|
Sorry, attachments in e-mail are removed. Can you sign-in to GitHub web UI? |
sympa.zip |
Also, please show these:
|
here is the log from when I sent a message 👍
The list exist, messages are correctly transmitted but I have some error message described in "Actual behavior" that I don't understand and are verbose in the sympa log. Attache file : content of postfix directory. The all thing was working in 6.2.52. |
In /var/spool/postfix/maildrop I have a lot of messages like 👍 T1591933637 432325Arewrite_context=localFSR$sympa-request@listes-rec.dsi.cnrs.frMNGDKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=listes-rec.dsi.cnrs.fr;N( h=message-id:date:to:from:mime-versionNA :content-transfer-encoding:content-type:subject; s=lists; bh=mRsNA hggdgSkVPKbd1a1hsuHD0PKXtJmNIHevX6vvaYFc=; b=E5Oas2NOIBxWB+H2V8xNA jgirULPrBUgKgHpiksHpUjSEXNoVeEAAk2Qn6iqc9fhjoJJY1z9FCQXlt8CuseAINA FHaTjkY0VhzzzCjtSbJMSIh0DNqahGLEidUo8YtuYa99FUsFSJbYqk6zbk/2HNimN v/LQ7kwbUdsUO8pUjXbcL8Dk=N?Message-Id: sympa.1591933636.43368.550@listes-rec.dsi.cnrs.frN%Date: Fri, 12 Jun 2020 05:47:16 +0200N(To: sympa-request@listes-rec.dsi.cnrs.frN4From: "SYMPA" sympa-request@listes-rec.dsi.cnrs.frNMIME-Version: 1.0NContent-Transfer-Encoding: 8bitNAuto-Submitted: auto-repliedN=Content-Type: multipart/report; report-type=delivery-status; NK boundary="----------=sympa.1591933636.43368.957@listes-rec.dsi.cnrs.fr"NSubject: Liste inconnueN$X-Loop: sympa@listes-rec.dsi.cnrs.frNX-Mailer: Sympa 6.2.54NN$This is a MIME-encapsulated message.NNA------------=sympa.1591933636.43368.957@listes-rec.dsi.cnrs.frNontent-Disposition: inlineN!Content-Description: NotificationN)Content-Type: TEXT/PLAIN; charset="UTF-8"N+Content-Transfer-Encoding: QUOTED-PRINTABLENMIME-Version: 1.0NContent-length: 461NN?Ceci est une r=C3=A9ponse automatique du robot de listes Sympa.N9Probl=C3=A8me de diffusion de votre message pour la listeN('sympa-request@listes-rec.dsi.cnrs.fr' :NN/L'adresse suivante n'est pas une liste connue :NN% sympa-request@listes-rec.dsi.cnrs.frNNHPour chercher l'adresse de la liste, consultez la liste des listes de ceNserveur :NN4 mailto:sympa@listes-rec.dsi.cnrs.fr?subject=3DWHICHNNFPour plus de d=C3=A9tails, contactez listmaster@listes-rec.dsi.cnrs.frNNA------------=sympa.1591933636.43368.957@listes-rec.dsi.cnrs.frN%Content-Type: message/delivery-statusNN*Reporting-MTA: dns; listes-rec.dsi.cnrs.frN-Arrival-Date: Fri, 12 Jun 2020 05:47:16 +0200NN=Final-Recipient: rfc822; sympa-request@lisStatus: 5.1.1N'Remote-MTA: dns; listes-rec.dsi.cnrs.frN9Diagnostic-Code: X-Sympa; Bad destination mailbox addressNNA------------=sympa.1591933636.43368.957@listes-rec.dsi.cnrs.frN5Content-Type: text/rfc822-headers; charset="US-ASCII"Nontent-Disposition: inlineNContent-Transfer-Encoding: 7BITNMIME-Version: 1.0NContent-length: 1018NN>Received: by tcgesympa2.dsi.cnrs.fr (Postfix, from userid 503)N4 id AE83A1F3; Fri, 12 Jun 2020 05:47:01 +0200 (CEST)NGDKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=listes-rec.dsi.cnrs.fr;N( h=message-id:date:to:from:mime-versionNA :content-transfer-encoding:content-type:subject; s=lists; bh=1xwNA d+VfOkv3diefdHO10e76yN7S5jB3h8zNVWDgZf1Y=; b=CItUz6HQZUnZ92KTUBRNA Zt5NJxG2X73C4UaxKIeHgWeM/EVvAJPSEiXHlInWExDgsSfJEIPZF4Mv/X/xbnKDNA yWCR9stedVCuG9hUC/nJ9z+Cus/JOaLWLWchu53WUZmDzx4iNvmiuEUIley7VDN/N iq8vT64oAzSJekwhFZL6hxb0=N?Message-Id: sympa.1591933620.43368.169@listes-rec.dsi.cnrs.frN%Date: Fri, 12 Jun 2020 05:47:00 +0200N(To: sympa-request@listes-rec.dsi.cnrs.frN4From: "SYMPA" sympa-request@listes-rec.dsi.cnrs.frNMIME-Version: 1.0NContent-Transfer-Encoding: 8bitNAuto-Submitted: auto-repliedN=Content-Type: multipart/report; report-type=delivery-status; NK boundary="----------=sympa.1591933620.43368.970@listes-rec.dsi.cnrs.fr"NSubject: Liste inconnueN$X-Loop: sympa@listes-rec.dsi.cnrs.frNX-Mailer: Sympa 6.2.54NNNC------------=sympa.1591933636.43368.957@listes-rec.dsi.cnrs.fr--XE |
@jth56000 , the log in June 12 indicates no problem. It is not what I asked. Please try following things:
|
Hello Soji,
I did what you asked and it seems the problem is solved.
I found more than 1 million messages in $SPOOLDIR/msg/bad that I removed.
I had the issue on two servers (integration and pre-production server) and the issue is solved on both of them.
I hope I will not have the issue on the production server…
Thank you for your help.
Regards,
Jean
<https://github.com/jth56000> @jth56000 , the log in June 12 indicates no problem. It is not what I asked.
Please try following things:
1. Stop syma and postfix services.
2. Clear messages in Sympa' s incoming spool ($SPOOLDIR/msg), outgoing spool ($SPOOLDIR/bulk/msg & $SPOOLDIR/bulk/pct) and Postfix's queue.
3. Start postfix and sympa services.
4. Post a message to the list.
5. Check if problematic logs are shown.
6. Show us Sympa's log during 3. to 5. above.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#957 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMTAPYGOR2KPQAXQ3CFMAALRWNCYVANCNFSM4N3DHDBQ> . <https://github.com/notifications/beacon/AMTAPYDPWHJZ4MFZN4GS3GDRWNCYVA5CNFSM4N3DHDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZOIVPA.gif>
|
There seems a message that triggered some sort of mail looping (one message leads Sympa to send another message, and they are repeated). When you observe flood of messages, please show us the log from the beginning of mail looping to some minutes after. |
Hello Soji,
I May have talk to rapidly, this morning I had more than 1500 messages in /datasan/sympa/spool/msg/bad .
I Played again your procedure :
1. Stop syma and postfix services.
2. Clear messages in Sympa' s incoming spool ($SPOOLDIR/msg), outgoing spool ($SPOOLDIR/bulk/msg & $SPOOLDIR/bulk/pct) and Postfix's queue.
3. Start postfix and sympa services.
4. Post a message to the list.
5. Check if problematic logs are shown.
I’m waiting to see if the problem occurs again and I send you the log.
Regards,
Jean
De : IKEDA Soji <notifications@github.com>
Envoyé : mardi 16 juin 2020 05:27
À : sympa-community/sympa <sympa@noreply.github.com>
Cc : THOMAS Jean <jean.thomas@ext.dsi.cnrs.fr>; Mention <mention@noreply.github.com>
Objet : Re: [sympa-community/sympa] Issue when upgrade from 6.2.52 to 6.2.54 : (#957)
<https://github.com/jth56000> @jth56000 ,
There seems a message that triggered some sort of mail looping (one message leads Sympa to send another message, and they are repeated). When you observe flood of messages, please show us the log from the beginning of mail looping to some minutes after.
—
You are receiving this because you were mentioned.
Reply to this email directly, <#957 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AMTAPYBCMC6YHH67UHJVTZDRW3Q75ANCNFSM4N3DHDBQ> unsubscribe. <https://github.com/notifications/beacon/AMTAPYAYIFBNEE4SRJ6G4WLRW3Q75A5CNFSM4N3DHDB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEZVG4LQ.gif>
|
…pa-community#957) <sympa-request> address should not be forwarded to any functions of Sympa. To avoid mail loop by such misconfiguration, discard messages bound for this address.
@jth56000 , could you please apply this patch and check if the problem will be dissaolved? |
…pa-community#957) <sympa-request> address should not be forwarded to any functions of Sympa. To avoid mail loop by such misconfiguration, discard messages bound for this address.
Mail loop with sympa-request address because of misconfiguration (#957)
Since I upgrade my sympa server from 6.2.52 to 6.2.54 I have lots of following messages in sympa log :
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,8135/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.12@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,7561/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.952@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,7330/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.498@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,3028/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.834@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Version
6.2.54
Installation method
RPM package on RedHat 7.6
Expected behavior
THe log should be less verbose, such messages should not appear.
Actual behavior
The log says lots of delivery status notification failed 👍
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,8135/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.12@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,7561/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.952@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,7330/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.498@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Jun 11 08:09:20 tcgesympa2 sympa_msg[57145]: notice Sympa::Spindle::ProcessTemplate::_twist() Processing Sympa::Message::Template <sympa@listes-rec.dsi.cnrs.fr.1591855760.57145,3028/shelved:dkim_sign>; envelope_sender=<>; message_id=sympa.1591855760.57145.834@listes-rec.dsi.cnrs.fr; recipients=sympa-request@listes-rec.dsi.cnrs.fr; sender=sympa-request@listes-rec.dsi.cnrs.fr; template=delivery_status_notification; action=failed; status=5.1.1
Additional information
The text was updated successfully, but these errors were encountered: