All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Mortimer <richm@oldelvet.org.uk>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Duplicate mail
Date: Thu, 28 Nov 2013 18:19:34 +0000	[thread overview]
Message-ID: <52978936.70802@oldelvet.org.uk> (raw)
In-Reply-To: <20131128135142.GI1408@chimay.paulfariello.fr>

Hi,

On 28/11/2013 13:51, Paul Fariello wrote:
> Hi all,
>
> 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.
This isn't a problem that can be solved in general. The visible "cc" and 
"to" headers are not necessarily what was used as the envelope addresses 
to deliver to. There may also be "bcc" or (non-mlmmj) aliases used in 
the visible headers.

By the time that the mail gets to mlmmj any original destinations will 
already have been lost in intermediate mailservers so at best you are 
going to be able to paper over the cracks with a solution that will work 
in some (most maybe) cases but will fail in others and either the mail 
will get lost or delivered twice.

>
> 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!

Regards

Richard


>
> Regards,
>


  reply	other threads:[~2013-11-28 18:19 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 [this message]
2013-11-28 21:03 ` Ben Schmidt
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=52978936.70802@oldelvet.org.uk \
    --to=richm@oldelvet.org.uk \
    --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.