nodupes unchecked but still applies

Bug #498235 reported by Jerome
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNU Mailman
Invalid
Undecided
Unassigned

Bug Description

When a message is sent to <email address hidden> and to <email address hidden> (where subscriber is a member of the list), <email address hidden> gets the message directly but not through the list.

As far as I understand, unchecking the nodupes option should let him receive both copies.

It does not.

No dupes option help :
http://support.tigertech.net/mailman-nodupes

Version of mailman used used :
http://packages.debian.org/lenny/mailman
(I am both admin of the server, the list, and subscriber to the list.)

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

You are correct that unchecking nodups should allow the list copy to be sent (the list, of course, has no control over the To: or Cc: copy).

Bug #297795, fixed in 2.1.12, is related, but is the opposite problem - i.e., duplicate received when nodups is checked. I am unable to duplicate your problem. Are you sure this isn't the receiving MUA hiding one of the "duplicate" messages.

tags: added: nodups
Revision history for this message
Jerome (jerome-jolimont) wrote : Re: [Bug 498235] Re: nodupes unchecked but still applies

Fri, 18 Dec 2009 16:59:26 -0000
Mark Sapiro a écrit:

> You are correct that unchecking nodups should allow the list copy to be
> sent (the list, of course, has no control over the To: or Cc: copy).

Thanks for clarifying this.

> Bug #297795, fixed in 2.1.12, is related, but is the opposite problem -
> i.e., duplicate received when nodups is checked. I am unable to
> duplicate your problem. Are you sure this isn't the receiving MUA hiding
> one of the "duplicate" messages.

Good point. I shall dig into this.

I don't remember having configured anything like that in Dovecot.

I'll keep you informed if i find something there.

--
Jérôme

Revision history for this message
Jerome (jerome-jolimont) wrote :

Mailman has nothing to do with this.

(The email-address I am using is an alias on a server I don't manage myself. They must have some setting to avoid duplicates.)

Thanks for answering.

Changed in mailman:
status: New → Invalid
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.