ietf-asrg
[Top] [All Lists]

Re: [Asrg] Domain-Authorized SMTP Mail

2003-03-18 14:31:23
On Tue, 18 Mar 2003 16:03:47 EST, David Green said:
If the DNS system is broken, that is a subject for another list.

Handwaving that way won't change the fact that your scheme would *double*
the effort required to accept mail from most of the largest providers - which
is where most of your mail will likely be *from*.

And there's lots of ugly scaling effects - double the load may require more
than double the hardware..

Majordomo masquerades as other people when it relays emails. This is
precisely what we want to prevent. The From: should be changed to the
name of the mailing list.

You really don't understand why lists work the day they do, do you?

There are reasons it is done the way it is.  In particular, if you change
the From: to the name of the list, where do we put the *POSTERS* name?
(Hint - if you're strictly RFC-compliant, it doesn't go in Sender:.  RFC822
overloads Sender: with 2 values, neither of which is correct semantics for
the person posting to the list).

This note would have appeared as:

From: asrg(_at_)ietf(_dot_)edu
To:   asrg(_at_)ietf(_dot_)edu

(You can't put individual recipient names in there, because then each message
body is different. Then you can't piggyback RCPT TO: - there's a *BIG*
performance difference between MajorDomo handing the MTA 1 piece of mail with
400 RCPT TO:, and 400 separate pieces of mail with 1 RCPT TO each.  This is
particularly obvious if you have 20,000 recipients and somebody posts a 500K
attachment (quite reasonable for some lists) - the one way you can do it using
500K of disk plus 1 list of addresses, the other way you just blew 10 gigabytes
of spool.  There's also the performance issues of having 20K messages to track
rather than just 1 (do an 'ls' in a directory with 1 file, and in one with 20K
files, and let me know what happens..)

And any sane citing software would have generated:

On Tue, 18 Mar 2003 16:03:47 EST, asrg(_at_)ietf(_dot_)edu said:

Oh, and that renders 'reply to author' impossible.


Attachment: pgpgC9VXbz7xD.pgp
Description: PGP signature