Re: regarding IETF lists using mailman: nodupes considered harmful

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2005-08-25 at 18:20 -0400, Keith Moore wrote:
<SNIP>

> Specifics:  Mailman has a per-recipient setting called "nodupes".  The
> effect of this setting is that any recipient address that has the
> nodupes flag set, and which appears in a To or CC field of a message
> sent to the list, will not receive a copy of the message from the
> list.

But they _should_ be getting the message directly already, because of
the CC: or To:. Or is there something which causes the person not to get
it?

Indeed when some 'malicious' person would add Cc's/To's and would
instruct his SMTP to not forward to the additional addresses in the
Cc/To the users will effectively not receive the message.

Or when the recipient doesn't accept messages to $list@xxxxxxxx +
himself, and expects everything to come from the list directly.

But how exactly does this cause a problem?

Greets,
 Jeroen


Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________

Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]