From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Duplicate mail
Date: Thu, 28 Nov 2013 21:03:43 +0000 [thread overview]
Message-ID: <5297AFAF.40509@yahoo.com.au> (raw)
In-Reply-To: <20131128135142.GI1408@chimay.paulfariello.fr>
On 29/11/13 5:19 AM, Richard Mortimer wrote:
> On 28/11/2013 13:51, Paul Fariello wrote:
>> I may be wrong but mlmmj don't seems to ignore subscribers that
>> already are in "cc" or "to" headers. This end up with user
>> complaining about duplicate mail.
...
>> Is there a way to avoid this behavior ? Either by tweaking
>> customheaders, by using a configuration I may have missed, by
>> patching ?
>>
> Sorry. I don't have a ready answer for that.
>
> The only way that I know is to filter on MessageID on the receiving
> server. The cyrus mail suite will do that but obviously that relies on
> the receiver's ISP which you will not be able to fix. Oh and it does
> in theory filter out any messages that errorneously have duplicate
> MessageID fields but that tends to be spam in my experience so no big
> loss!
I agree it is best to deal with this at the receiving end if possible.
That said, I suppose this is similar to the "notmetoo" functionality,
and perhaps "notmetoo" could be extended to cover these cases, too, i.e.
ignore "to" and "cc" addresses as well as the "from" one when
distributing posts. It shouldn't be too hard (I wrote the notmetoo
functionality, so am fairly familiar with it.)
Open an enhancement request on the bug tracker and/or write a patch for
it if you like.
Smiles,
Ben.
next prev parent reply other threads:[~2013-11-28 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 13:51 [mlmmj] Duplicate mail Paul Fariello
2013-11-28 18:19 ` Richard Mortimer
2013-11-28 21:03 ` Ben Schmidt [this message]
2013-12-02 6:52 ` G Stansfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5297AFAF.40509@yahoo.com.au \
--to=mail_ben_schmidt@yahoo.com.au \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.