I line with the Unix philosofy:
A m2n-gw sends messages form email to usenet. It does not perform any other functions. (so it takes the MessageID and uses that)
A remailer/mixmaster anonymizes mail messages.
Both have their own function and complement each other:)
Alex de Joode wrote:
A m2n-gw sends messages form email to usenet. It does not perform any other >> functions. (so it takes the MessageID and uses that)
To settle the matter once and for all, i hace changed the Message-ID >generation behavior but that *does not address that issue*.
Gab_Virebent <gabriel1@virebent.invalid> wrote:
Alex de Joode wrote:
A m2n-gw sends messages form email to usenet. It does not perform any other >>> functions. (so it takes the MessageID and uses that)
To settle the matter once and for all, i hace changed the Message-ID
generation behavior but that *does not address that issue*.
For remailer users it's easy to settle that matter once and for all by continuing to ignore your deliberately incompatible, thus broken services.
Gab_Virebent <gabriel1@virebent.invalid> wrote:
Alex de Joode wrote:
A m2n-gw sends messages form email to usenet. It does not perform
any other functions. (so it takes the MessageID and uses that)
To settle the matter once and for all, i hace changed the Message-ID >>generation behavior but that *does not address that issue*.
For remailer users it's easy to settle that matter once and for all by continuing to ignore your deliberately incompatible, thus broken
services.
Gab_Virebent <gabriel1@virebent.invalid> wrote:
Alex de Joode wrote:
A m2n-gw sends messages form email to usenet. It does not perform
any other functions. (so it takes the MessageID and uses that)
To settle the matter once and for all, i hace changed the Message-ID >>generation behavior but that *does not address that issue*.
For remailer users it's easy to settle that matter once and for all by continuing to ignore your deliberately incompatible, thus broken
services.
Alex de Joode wrote:
I line with the Unix philosofy:
A m2n-gw sends messages form email to usenet. It does not perform any other >> functions. (so it takes the MessageID and uses that)
A remailer/mixmaster anonymizes mail messages.
Both have their own function and complement each other:)
TCPResetrCOs Message-ID rewriting was intended as a privacy precaution for direct email submissions, which do not necessarily pass through a remailer.
However, I accept that this choice can interfere with
duplicate suppression when the same message is submitted through
multiple gateways...
RFC 5537 explicitly describes multiple injection as an unusual case, although a supported one. I hadnrCOt accounted for that workflow.
How widely is it actually used outside OmniMix?
To settle the matter once and for all, i hace changed the Message-ID generation behavior but that *does not address that issue*.
The relevant question is whether the same original message retains a consistent identity across those paths.
Your point about preserving an existing Message-ID in a remailer-to-news workflow is fair.
Comments: This message did not originate from the Sender address
above. It was posted by the mail-to-news gateway at news.tcpreset.net.
Also, I noticed that your mail2news service inserts this line:
Comments: This message did not originate from the Sender address
above. It was posted by the mail-to-news gateway at news.tcpreset.net.
This is not correct. This line should be inserted by anonymous
remailers, mail2news services themselves do not provide anonymity
(unless you also replace From header). My email address is where my
message originated from. I don't use mail2news service for "anonymity",
I'm just too lazy to register anywhere.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 56:09:49 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,718 |