Skip to Content.
Sympa Menu

en - Re: [sympa-users] sympa 6.2.48 "Message <recipient> has no message ID"

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: "Stefan Hornburg (Racke)" <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] sympa 6.2.48 "Message <recipient> has no message ID"
  • Date: Tue, 10 Dec 2019 16:28:36 +0100

On 12/10/19 3:08 PM, stefano.antonelli@cnaf wrote:
> Dear All,
>
> we have happily (:-)) upgraded to sympa 6.2.48 but we are facing this
> problem:
>
> some, many, messages from alarm, monitoring systems arrive to mailing lists
> without Message-ID field in the header and
> are moved to /var/spool/sympa/msg/bad. Moving these mails to
> /var/spool/sympa/msg doesn't solve the problem.
>
> At the moment, we've not been able to bypass this problem; is there a way
> (scenario, list configuration, etc.) to change
> sympa behaviour?
>
> thank you
> cheers
> Stefano
>

You should rather fix these monitoring systems :-)

Regards
Racke

--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration. Provisioning with Ansible.

Attachment: signature.asc
Description: OpenPGP digital signature




Archive powered by MHonArc 2.6.19+.

Top of Page