Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed?
Thank you,
S Gruver Unix system administrator Center for Information Services Bellevue, WA 98004 phone 425.803.9753 fax 425.803.9652
Gruver, Sandi wrote:
Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed?
No. It only means that a member will not receive the post from the list if (s)he in specifically addressed in To: or Cc: of the post.
If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10 can be used to avoid these duplicate messages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
That's interesting.
I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-)
(No need for action from anyone - I was just mumbling aloud).
Allan
At 16:49 -0800 12/14/07, Mark Sapiro wrote:
Gruver, Sandi wrote:
Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed?
No. It only means that a member will not receive the post from the list if (s)he in specifically addressed in To: or Cc: of the post.
If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10 can be used to avoid these duplicate messages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
Allan Hansen writes:
That's interesting.
I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-)
What do you mean by "get"? I "get" both messages in my system mailbox, but because I have duplicate suppression on in my MUA, I only "see" one. The MUA automatically skips any message with a Message-ID that it has already seen.
I would assume you've got a similar feature, perhaps not in your MUA but in the MDA or MTA.
(No need for action from anyone - I was just mumbling aloud).
Allan
At 16:49 -0800 12/14/07, Mark Sapiro wrote:
Gruver, Sandi wrote:
Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed?
No. It only means that a member will not receive the post from the list if (s)he in specifically addressed in To: or Cc: of the post.
If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10 can be used to avoid these duplicate messages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/stephen%40xemacs.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Stephen J. Turnbull wrote:
Allan Hansen writes:
That's interesting.
I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-)
What do you mean by "get"? I "get" both messages in my system mailbox, but because I have duplicate suppression on in my MUA, I only "see" one. The MUA automatically skips any message with a Message-ID that it has already seen.
I would assume you've got a similar feature, perhaps not in your MUA but in the MDA or MTA.
This is definitely a gmail 'feature' to the extent that you won't see your own list posts because they are 'duplicates' of the sent message.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Sapiro wrote:
This is definitely a gmail 'feature' to the extent that you won't see your own list posts because they are 'duplicates' of the sent message.
I meant to say "... to the extent that you won't even see your own list posts ...".
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
I have Three lists list1@domain.com (1000 members) and list2@domain.com (1500 members) and list3@domain.com . Now, In list3@domain.com I have only two members i.e. list1@domain.com and list2@domain.com.
If I send any message to list3@domain.com it goes to all the members of list1 and list2 but the members who are in both list1 and list2 gets duplicate copies. How to prevent that? I don't want to send duplicate messages.
Please advise.
Regards, Vinita Aggarwal
-----Original Message----- From: mailman-users-bounces+vinita.aggarwal=un.org.in@python.org [mailto:mailman-users-bounces+vinita.aggarwal=un.org.in@python.org] On Behalf Of Mark Sapiro Sent: Monday, December 17, 2007 1:01 AM To: Stephen J. Turnbull; Allan Hansen Cc: mailman-users@python.org Subject: Re: [Mailman-Users] no dupes across lists?
Stephen J. Turnbull wrote:
Allan Hansen writes:
That's interesting.
I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-)
What do you mean by "get"? I "get" both messages in my system mailbox, but because I have duplicate suppression on in my MUA, I only "see" one. The MUA automatically skips any message with a Message-ID that it has already seen.
I would assume you've got a similar feature, perhaps not in your MUA but in the MDA or MTA.
This is definitely a gmail 'feature' to the extent that you won't see your own list posts because they are 'duplicates' of the sent message.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/vinita.aggarwal%40un.or g.in
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
On Dec 27, 2007 4:45 AM, Vinita Aggarwal <vinita.aggarwal@un.org.in> wrote:
I have Three lists list1@domain.com (1000 members) and list2@domain.com (1500 members) and list3@domain.com . Now, In list3@domain.com I have only two members i.e. list1@domain.com and list2@domain.com.
write cron script that does something similar to this (typed free hand, mileage may vary), or perhaps runs opportunistically, so that your creating the actual list membership nearly on the fly
LIST=/tmp/list3.lst ./remove_members list3 (./list_members list1; ./list_members list2) | tr -t '[:upper:]' '[:lower:]' |sort -u > ${LIST} ./add_members -w=n -a=n -r=/tmp/list3.lst list3 rm ${LIST}
Thanks for your suggestion
Regards, Vinita Aggarwal
-----Original Message----- From: mailman-users-bounces+vinita.aggarwal=un.org.in@python.org [mailto:mailman-users-bounces+vinita.aggarwal=un.org.in@python.org] On Behalf Of Gabriel Millerd Sent: Thursday, December 27, 2007 7:33 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] no dupes across lists?
On Dec 27, 2007 4:45 AM, Vinita Aggarwal <vinita.aggarwal@un.org.in> wrote:
I have Three lists list1@domain.com (1000 members) and list2@domain.com (1500 members) and list3@domain.com . Now, In list3@domain.com I have only two members i.e. list1@domain.com and list2@domain.com.
write cron script that does something similar to this (typed free hand, mileage may vary), or perhaps runs opportunistically, so that your creating the actual list membership nearly on the fly
LIST=/tmp/list3.lst ./remove_members list3 (./list_members list1; ./list_members list2) | tr -t '[:upper:]' '[:lower:]' |sort -u > ${LIST} ./add_members -w=n -a=n -r=/tmp/list3.lst list3 rm ${LIST}
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/vinita.aggarwal%40un.or g.in
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Hi,
Is there any way by which I can find out the date on which a particular email id was added in mailman mailing list?
Please suggest
Regards, Vinita Aggarwal
On 12/28/07, Vinita Aggarwal wrote:
Is there any way by which I can find out the date on which a particular email id was added in mailman mailing list?
Look in the logfile "/usr/local/mailman/logs/subscribe".
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
Hey, I received an email from mailman-bounces@mydomain.com notifying me that a member has been unsubscribed. This person has not requested to be removed nor was notified to be removed. This happened about 3 weeks ago but with about 10 members in one day. How do I keep my members from being randomly removed? Thanks for your help! Tonya
Tonya Robison wrote:
I received an email from mailman-bounces@mydomain.com notifying me that a member has been unsubscribed. This person has not requested to be removed nor was notified to be removed. This happened about 3 weeks ago but with about 10 members in one day. How do I keep my members from being randomly removed? Thanks for your help!
I suspect these members were removed by automated bounce processing. See Mailman's bounce log and the admin Bounce processing page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Probably as a result of monthly passwords being sent out at the first
of the month.
This is a typical issue for Mailman-hosted mailing lists and users who
either change e-mail addresses often, or who frequently have
overflowing mailboxes, or set up auto-responders that are not
intelligent in how they generate their responses, etc....
-- Brad Knowles <brad@shub-Internet.org>
Sent from my iPhone
On Jan 3, 2008, at 2:15 PM, Mark Sapiro <mark@msapiro.net> wrote:
Tonya Robison wrote:
I received an email from mailman-bounces@mydomain.com notifying me
that a member has been unsubscribed. This person has not requested to be
removed nor was notified to be removed. This happened about 3 weeks ago but
with about 10 members in one day. How do I keep my members from being
randomly removed? Thanks for your help!I suspect these members were removed by automated bounce processing. See Mailman's bounce log and the admin Bounce processing page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/brad%40shub-internet.or...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
I never saw a log for bounces in the admin interface. I looked under bounce processing and never saw it. If I get in to this situation this usser is in where is hte log loacated so I may find it. I don't run the ist from my own machine. it is run by a web service provider.
SA&G ----- Original Message ----- From: "Mark Sapiro" <mark@msapiro.net> To: "Tonya Robison" <tonyar@indigenthealthcaresolutions.com>; <mailman-users@python.org> Sent: Thursday, January 03, 2008 12:15 PM Subject: Re: [Mailman-Users] Un-subscribe notification
Tonya Robison wrote:
I received an email from mailman-bounces@mydomain.com notifying me that a member has been unsubscribed. This person has not requested to be removed nor was notified to be removed. This happened about 3 weeks ago but with about 10 members in one day. How do I keep my members from being randomly removed? Thanks for your help!
I suspect these members were removed by automated bounce processing. See Mailman's bounce log and the admin Bounce processing page.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/marrie12%40gmail.com
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Sarah wrote:
I never saw a log for bounces in the admin interface. I looked under bounce processing and never saw it.
Because Mailman's logs are not available in the web admin interface. They are global logs and are thus only available to people who can access the underlying file system on the host machine.
If I get in to this situation this usser is in where is hte log loacated so I may find it. I don't run the ist from my own machine. it is run by a web service provider.
You don't really need access to the bounce log. That is only to find out after the fact what happened. If you turn on the bounce_notify_owner_on_disable notification, you will get a notice when the member's delivery is first disabled due to bouncing, which should be all you need to determine if the member's address is in fact not good before the member is removed as long as bounce_you_are_disabled_warnings is > 0.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/3/08, Sarah wrote:
I never saw a log for bounces in the admin interface. I looked under bounce processing and never saw it. If I get in to this situation this usser is in where is hte log loacated so I may find it. I don't run the ist from my own machine. it is run by a web service provider.
The log is on the server. None of the Mailman logs are available via the web. You need to get your service provider to look at the logs on your behalf.
-- Brad Knowles <brad@shub-internet.org> LinkedIn Profile: <http://tinyurl.com/y8kpxu>
At 2:34 +0900 12/17/07, Stephen J. Turnbull wrote:
Allan Hansen writes:
That's interesting.
I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-)
What do you mean by "get"? I "get" both messages in my system mailbox, but because I have duplicate suppression on in my MUA, I only "see" one. The MUA automatically skips any message with a Message-ID that it has already seen.
More detail:
One message from a subscriber's MUA goes to two lists in Mailman because that person is addressing it using
To: list1@abc.com, list2@abc.com
The subscriber (who is not I) is subscribed to both lis1 and list2 (I verified this). I'm also subscribed to both list1 and list2 (also verified).
Mailman is the actual recipient of this message. However, being a listserver, Mailman becomes the originator (literally) of two new messages, one for the subscribers of list1 and another for the subscribers of list2. It has to be two messages, because one message has additional headers and a footer added for list1 and the other has headers and a footer added for list2. In fact, Mailman even adds the Sender: header with the list as the sender.
I'm subscribed to both list1 and list2, so I'll expect to see two different messages being picked up by my MUA. One message with Sender: list1@abc.com and another with Sender: list2@abc.com.
This, in fact, is how it worked in a previous list server (ListStar) that I used before Mailman.
In Mailman I'm seeing only the message corresponding to list2.
My MTA is Postfix and my MUA is Eudora (both running under Mac OS X 10.4.11).
I cannot imagine my MUA comparing the two messages and throwing one out, as the message bodies are, in fact, different. Ditto for the MDA and MTA.
Allan
I would assume you've got a similar feature, perhaps not in your MUA but in the MDA or MTA.
(No need for action from anyone - I was just mumbling aloud).
Allan
At 16:49 -0800 12/14/07, Mark Sapiro wrote:
Gruver, Sandi wrote:
Does the 'no dupes' option mean that members will not receive a messages sent to more than one list to which they are subscribed?
No. It only means that a member will not receive the post from the list if (s)he in specifically addressed in To: or Cc: of the post.
If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10 can be used to avoid these duplicate messages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/stephen%40xemacs.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
Check your Message-ID: headers. IIRC, Mailman doesn't change those
when taking an incoming message and sending that back out.
In addition I happen to know from personal experience that Eudora has
some very powerful duplicate suppression capabilities -- they are one
of the few tools that helps keep me sane.
-- Brad Knowles <brad@shub-Internet.org>
Sent from my iPhone
On Dec 17, 2007, at 2:52 AM, Allan Hansen <hansen@rc.org> wrote:
At 2:34 +0900 12/17/07, Stephen J. Turnbull wrote:
Allan Hansen writes:
That's interesting.
I run Mailman 2.1.5 (Mac OS X 10.4) and have the 'problem' that when someone posts to two lists at a time, I get only one message. I actually do want to get both for archival purposes. If this is not a function of Mailman 2.1.5, I wonder where the other message is cut. :-)
What do you mean by "get"? I "get" both messages in my system mailbox, but because I have duplicate suppression on in my MUA, I
only "see" one. The MUA automatically skips any message with a Message-ID that it has already seen.More detail:
One message from a subscriber's MUA goes to two lists in Mailman
because that person is addressing it usingTo: list1@abc.com, list2@abc.com
The subscriber (who is not I) is subscribed to both lis1 and list2
(I verified this). I'm also subscribed to both list1 and list2 (also verified).Mailman is the actual recipient of this message. However, being a
listserver, Mailman becomes the originator (literally) of two new
messages, one for the subscribers of list1 and another for the
subscribers of list2. It has to be two messages, because one message
has additional headers and a footer added for list1 and the other
has headers and a footer added for list2. In fact, Mailman even adds
the Sender: header with the list as the sender.I'm subscribed to both list1 and list2, so I'll expect to see two
different messages being picked up by my MUA. One message with
Sender: list1@abc.com and another with Sender: list2@abc.com.This, in fact, is how it worked in a previous list server (ListStar)
that I used before Mailman.In Mailman I'm seeing only the message corresponding to list2.
My MTA is Postfix and my MUA is Eudora (both running under Mac OS X
10.4.11).I cannot imagine my MUA comparing the two messages and throwing one
out, as the message bodies are, in fact, different. Ditto for the
MDA and MTA.Allan
I would assume you've got a similar feature, perhaps not in your MUA but in the MDA or MTA.
(No need for action from anyone - I was just mumbling aloud).
Allan
At 16:49 -0800 12/14/07, Mark Sapiro wrote:
Gruver, Sandi wrote:
Does the 'no dupes' option mean that members will not receive a
messages sent to more than one list to which they are subscribed?No. It only means that a member will not receive the post from
the list if (s)he in specifically addressed in To: or Cc: of the post.If you have lists with duplicate members which are frequently cross posted, the new sibling lists 'exclude' feature in Mailman 2.1.10
can be used to avoid these duplicate messages.-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B.
Dylan-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/stephen%40xemacs.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/brad%40shub-internet.or...
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Allan Hansen writes:
One message from a subscriber's MUA goes to two lists in Mailman because that person is addressing it using
To: list1@abc.com, list2@abc.com
[subscriptions of poster and recipient to list1 and list2 verified]
Mailman is the actual recipient of this message. However, being a listserver, Mailman becomes the originator (literally) of two new messages,
This may be true "literally", but it is definitely not true from the point of view of Mailman or RFC 2822. In fact Mailman will preserve the Message-ID header, and thus the identity of the two messages. This behavior conforms to RFC 2822.
one for the subscribers of list1 and another for the subscribers of list2. It has to be two messages, because one message has additional headers and a footer added for list1 and the other has headers and a footer added for list2. In fact, Mailman even adds the Sender: header with the list as the sender.
RFC 2822 headers are not part of the message in the sense relevant to duplicate pruning. Messing with those headers (except Message-ID, of course) should never change the identity of the message in the sense of RFC 2822 (AFAIK, I haven't read it with that exact point in mind, though).
I'm subscribed to both list1 and list2, so I'll expect to see two different messages being picked up by my MUA. One message with Sender: list1@abc.com and another with Sender: list2@abc.com.
I don't suppose list1 is an umbrella list, with list2 subscribed to it? Or vice versa? (I don't know for sure that this could lead to the described effect, but I also don't see offhand how to prove it couldn't.)
In Mailman I'm seeing only the message corresponding to list2.
My MTA is Postfix and my MUA is Eudora (both running under Mac OS X 10.4.11).
Eudora is a full-featured MUA; I would imagine it can suppress dupes.
I cannot imagine my MUA comparing the two messages and throwing one out, as the message bodies are, in fact, different. Ditto for the MDA and MTA.
I can't imagine it, either. But no duplicate-pruning agent I've seen attempts to compare bodies. Instead, they use the Message-ID header, and assume that two messages with the same Message-ID are the same message in the relevant sense. Mailman does not touch this header, because it interprets the addition of body headers and footers, and even removal of unwanted content, to *not* change the identity of the message. (IIRC Mailman does add a Resent-Message-ID, however.) So duplicate-pruning agents will suppress one of the messages.
Mailman's internal no-dupes and not-me-too features work differently: if an explicit recipient address (resp, the from address for not-me-too) in the message's headers (a) is an exact match for a subscriber address and (b) its subscription has the no-dupes (resp, not-me-too) flag set, Mailman does not queue a delivery to that subscriber address. This also does not involve an attempt to compare message bodies.
This certainly explains the behaviour, Stephen and Brad. I had looked through all the options in Eudora and didn't find a way to turn off this pruning feature, so I assumed it to be non-existent.
As for RFC 2822, this is what it says about Message-ID. Given the highlighted section, I think that what you have done with Mailman (not touching the Message-ID) is the right thing to do. Besides, keeping Brad sane is certainly a worthy goal. :-)
Thank you all for a great program.
Allan
The "Message-ID:" field provides a unique message identifier that refers to a particular version of a particular message. The uniqueness of the message identifier is guaranteed by the host that generates it (see below). This message identifier is intended to be machine readable and not necessarily meaningful to humans. A message identifier pertains to exactly one instantiation of a particular message; subsequent revisions to the message each receive new message identifiers.
Note: There are many instances when messages are "changed", but those changes do not constitute a new instantiation of that message, and therefore the message would not get a new message identifier. For example, when messages are introduced into the transport system, they are often prepended with additional header fields such as trace fields (described in section 3.6.7) and resent fields (described in section 3.6.6). The addition of such header fields does not change the identity of the message and therefore the original "Message-ID:" field is retained. In all cases, it is the meaning that the sender of the message wishes to convey (i.e., whether this is the same message or a different message) that determines whether or not the "Message-ID:" field changes, not any particular syntactic difference that appears (or does not appear) in the message.
At 19:12 +0900 12/17/07, Stephen J. Turnbull wrote:
Allan Hansen writes:
One message from a subscriber's MUA goes to two lists in Mailman because that person is addressing it using
To: list1@abc.com, list2@abc.com
[subscriptions of poster and recipient to list1 and list2 verified]
Mailman is the actual recipient of this message. However, being a listserver, Mailman becomes the originator (literally) of two new messages,
This may be true "literally", but it is definitely not true from the point of view of Mailman or RFC 2822. In fact Mailman will preserve the Message-ID header, and thus the identity of the two messages. This behavior conforms to RFC 2822.
one for the subscribers of list1 and another for the subscribers of list2. It has to be two messages, because one message has additional headers and a footer added for list1 and the other has headers and a footer added for list2. In fact, Mailman even adds the Sender: header with the list as the sender.
RFC 2822 headers are not part of the message in the sense relevant to duplicate pruning. Messing with those headers (except Message-ID, of course) should never change the identity of the message in the sense of RFC 2822 (AFAIK, I haven't read it with that exact point in mind, though).
I'm subscribed to both list1 and list2, so I'll expect to see two different messages being picked up by my MUA. One message with Sender: list1@abc.com and another with Sender: list2@abc.com.
I don't suppose list1 is an umbrella list, with list2 subscribed to it? Or vice versa? (I don't know for sure that this could lead to the described effect, but I also don't see offhand how to prove it couldn't.)
In Mailman I'm seeing only the message corresponding to list2.
My MTA is Postfix and my MUA is Eudora (both running under Mac OS X 10.4.11).
Eudora is a full-featured MUA; I would imagine it can suppress dupes.
I cannot imagine my MUA comparing the two messages and throwing one out, as the message bodies are, in fact, different. Ditto for the MDA and MTA.
I can't imagine it, either. But no duplicate-pruning agent I've seen attempts to compare bodies. Instead, they use the Message-ID header, and assume that two messages with the same Message-ID are the same message in the relevant sense. Mailman does not touch this header, because it interprets the addition of body headers and footers, and even removal of unwanted content, to *not* change the identity of the message. (IIRC Mailman does add a Resent-Message-ID, however.) So duplicate-pruning agents will suppress one of the messages.
Mailman's internal no-dupes and not-me-too features work differently: if an explicit recipient address (resp, the from address for not-me-too) in the message's headers (a) is an exact match for a subscriber address and (b) its subscription has the no-dupes (resp, not-me-too) flag set, Mailman does not queue a delivery to that subscriber address. This also does not involve an attempt to compare message bodies.
-- Allan Hansen P.O Box 2423 Cypress, CA 90630 U.S.A. hansen@rc.org +1-714-875-8870
participants (9)
-
Allan Hansen -
Brad Knowles -
Gabriel Millerd -
Gruver, Sandi -
Mark Sapiro -
Sarah -
Stephen J. Turnbull -
Tonya Robison -
Vinita Aggarwal