[Mailman-Developers] [ mailman-Feature Requests-224058 ] Wishlist: New Header X-Subscribed-as:

[noreply@sourceforge.net]

Feature Requests item #224058, was opened at 2000-12-01 11:56
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224058&group_id=103

Category: mail delivery
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: Eduardo Marcel Maçan (emacan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wishlist: New Header X-Subscribed-as:

Initial Comment:
I run a very busy and large list with mailman and frequently face the
following problem:

	Many people subscribe using and e-mail redirector, or changes
jobs/provider leaving a mail  redirection in the former address. When
the new mailbox is full, or worst, when it is not valid anymore we get
e-mails bouncing from an Address not subscribed to the list. The
offending address cannot be taken care automatically by mailman,
and most of the times the list administrator cannot find it by using
list_members or by browsing logs, because he does not necessarily
has access to the server running his mailing list (Browsing all users
in the web interface is not effective in this case, specially for large
mailing lists).
 
	Other similar situation is that some large ISPs use internal
e-mail routing rules to map address@somewhere.com to things
like user1342@state.somewhere.com for an example, and errors usually
return to list-admin in the second form.

	By using a header similar to X-Subscribed-as: email@somewhere.com in the message headers we could easily identify
such offending e-mails, and maybe even  take actions automatically. 




----------------------------------------------------------------------

>Comment By: Barry Warsaw (bwarsaw)
Date: 2002-05-03 01:07

Message:
Logged In: YES 
user_id=12800

Mailman 2.1 will (optionally) support verp and personalized
messages.  Yes, it increases the load on the mail server.

With verp/personalization enabled, MM2.1 does not add a
separate X-Subscribed-As: header, but I also don't think
it's necessary, since the subscribed address is encoded in
the envelope sender, so it should always be extractable both
automatically and manually.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2001-10-06 08:22

Message:
Logged In: NO 

The thing about the incerased Load is only partly true.  On the one Hand qmail threads a message to several people already as several seperate messages at least concerning SMTP handling, on the other hand a lot of features whished for mailman really really need per subscriber messages.

* VERP
* Easy unsubscribe
* Customized Messages , "Dear Mx. X,"

--drt@un.bewaff.net

----------------------------------------------------------------------

Comment By: Cord Beermann (cord)
Date: 2001-08-16 15:43

Message:
Logged In: YES 
user_id=50101

If you don't want to add such a header it would be nice if
Mailman sends one bounce through to the List-admin, so
he/she can deal with it.

Yet there are only log-entries which can only be vied by
someone with an acoount on the computer.

Cord

----------------------------------------------------------------------

Comment By: Thomas Wouters (twouters)
Date: 2001-02-26 03:25

Message:
Logged In: YES 
user_id=34209

The problem with this is that it requires sending each
message seperately. Mailman currently does it in bulk, which
for big lists greatly (and I mean *greatly*) reduces the
load on both the Mailman machine and the SMTP server that it
uses, not to mention mailservers that host a lot of the
subscribers to that list. 

Still, might be worth doing optionally, if both the site
owner and the list owner (and possibly the subscriber
themselves, though maybe not :) enable it.

(Not a mailman developer, just a user giving his opinion ;)


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224058&group_id=103