Richard Damon writes:
> The internet protocols disagree on that minor modification create a new
> email.
No, they don't. There's only one RFC that matters, and that's RFC
5322 (or whichever version of that standard that you prefer, but on
this they're basically in agreement). RFC 5322 says:
The internet protocols disagree on that minor modification create a new
email. For instance, EVERY step of mail deliver is REQUIRED to change
the headers of the message, so that would say every step should change
the Message-ID, which distorts some of its use.
The RFC's also say that if a mess
Dear William and Mark and all,
many thanks for your answer. I understand, that never you want to make
any special action for a specific task for Gmail.
But now, for me it is not a question of the specific "duplicate
suppression" from google-mail. it is a more general debate about the
princi
On Monday 23 June 2014, Mark Sapiro wrote:
> Your choice is clear to me. If you don't like the way Gmail handles your
> list posts, subscribe and post from a non-gmail address.
Mark, off topic for *this* list though you might want to add this to the FAQ?
willi, some web hosting servers will allow
On 06/23/2014 08:59 AM, willi uebelherr wrote:
>
>
> The easest way would be a configuratin point for the user to decide,
> that his sended mail get a new message-id, if the listserver changed it
> when he send the mail. And this he always do it.
We have no plans or interest to change Mailman i
Dear friends,
following the RFC 5322 all identification fields are optional. But they
SHOULD have it. Of course, sometimes we need it.
RFC 5322: Internet Message Format
http://tools.ietf.org/html/rfc5322
We have min 3 fields:
message-id
in-reply-to
references
With that, we can create all or
