The mailing list for listmasters using Sympa

[Victoriano Giralt <address@concealed>]

Hi,

We are having trouble with one of our lists, that is marking as bad
messages that arrive without the Message-Id header. It complains in the
logs[1] and saves the message in "bad".

The mail filtering antivirus, Kaspersky in our case, lets them pass in.
I know that Amavis does not.

My first reaction was to tell the anti-virus administrators to get it
to refuse messages without Message-Id, but, after a careful read of
RFC5322 section 3.6.4[2], it is a SHOULD, not a MUST, so, in purity,
those messages are not totally out of RFC compliance ...

Is there a way to tell Sympa to be nicer with this borderline RFC
offenders? We do not want to start a useless fight with the sending
party, with the usual "but our messages get delivered to other
universities..." type of conversation.

Thanks. I wish that this message finds all the Sympa community in as
good shape as possible in this complicated times we are living.

[1] Log file excerpt:
2021-01-22T10:23:30.926756+01:00 sympa sympa_msg[334]: err main::#243 >
Sympa::Spindle::spin#83 > Sympa::Spindle::ProcessIncoming::_twist#111
Message Sympa::Message <address@concealed> has no message ID

[2] https://tools.ietf.org/html/rfc5322#section-3.6.4

-- 
Victoriano Giralt                             Innovation Director
Digital Transformation Vicerectorate          University of Malaga
+34952131415                                  SPAIN
==================================================================
Note: signature.asc is the electronic signature of present message
A: Yes.
> Q: Are you sure ?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email ?

Attachment: signature.asc
Description: This is a digitally signed message part