The LMTP server needs to check acceptable aliases

Bug #1170726 reported by Barry Warsaw
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNU Mailman

Bug Description

The LMTP server currently does a sanity check on the To field of the incoming message, to ensure that it is addressed to a valid mailing list. This check ignores acceptable aliases, but it should honor them.

Tags: mailman3
Revision history for this message
Ian Eiloart (iane) wrote :

Does "the To field of the incoming message" mean the RCPT TO argument of the LMTP session? Or the "To:" header of the message. I think it should mean the former, since the latter needn't be related at all, if the list permits BCC.

Revision history for this message
Mark Sapiro (msapiro) wrote :

BCC is the whole point of this bug. If a list requires 'explicit destination', the list address or an acceptable alias must be in the To: or Cc: headers of the message. The bug says acceptable aliases aren't checked and it means against the To: or Cc: headers.

Checking against the envelope recipient is irrelevant since if the list weren't the envelope recipient of the message, the list's chain wouldn't be seeing the message in the first place.

Revision history for this message
Abhilash Raj (raj-abhilash1) wrote :

This bug has been moved to the new gitlab repo here:

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.