Make all outgoing mails RFC 3834 compliant

Bug #558289 reported by lkoeller
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
New
Undecided
Unassigned

Bug Description

Hi,

please make all outgoing mail RFC 3834 compliant, to
help reasonable processing in an RFC 3834 compliant MTA.

Especially the vacation/autoreply functions of all up to date (e.g. SUN JSMS, Sophos PMX) mail servers respect these header tags and helps keeping the list admin free of managing dump reply mails.

Details:

http://www.ietf.org/rfc/rfc3834.txt

Thanks!

Revision history for this message
jimpop (jimpop-users-sf) wrote :

Logged In: YES
user_id=3142
Originator: NO

Care to provide any specifics on just what exactly it is that you deem non-compliant? It's been a while since this debate has seen the light of day.... come prepared. :-)

Revision history for this message
lkoeller (lkoeller-users) wrote :

Logged In: YES
user_id=412469
Originator: YES

Most of the automatic processing mail engines like autoresponder/vacation/SPAM-digest systems respect RFC 3834 mail header. So it is useful to add the RFC 3834 headers to any auto generated mail Mailman sends out, e.g.: subscribe, unsubscribe messages, password reminders, and perhaps any regular distributed post to the list (see rfc and search for list), cause it makes no sense to send back e.g. a vacation message to the originatin mail list for any of these types of messages.

For the right header tags and details see the rfc 3834.

The presence of the casual List-..... headers are not sufficient so far.

Hope this helps ... :-)

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.