-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Greg,
Like most people who've been running mailing lists for 20+ years, I have strong opinions about list policy. Please address the mechanism I asked for instead of seeking to discuss the policy issues.
You have a policy problem with your MTA, not your MLM.
Which part of "I don't think we should talk about the policy issues" do you not understand? Please stop wasting your own time.
Hey don't do what you are complaining about others doing. I understand you got some crummy replies, but take a moment to understand what I am saying. It was meant to be constructive.
Do you really have a *policy* to accept messages that you will never deliver, save them to disk, and then generate reject messages for them? Or is that simply the way your MTA+MLM is configured by default? Is that *policy* really any different from your standpoint, from rejecting undeliverable messages during SMTP?
Real users who send from the wrong email account, for example, would still have their messages returned to them either way. The only difference is that the bounce will be generated by their MTA, and not yours. You can still include the reason the message was rejected.
Junk from spammers will never land on your disks, you will not be flooding yahoo users with incomprehensible "reject" notices for stuff they didn't send, or annoying yahoo.com's postmaster with a blizzard of messages to non-existant accounts.
It would not be inconsistent with your current MLM policy. It is simply a better mechanism for implementing it, a better MTA policy, and better netizenship to boot.
- H-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin)
iD4DBQFEB1KgOy/dHTCUq6oRArwjAJ0Y1UNtC7xviyu61C9uVaWvyKQfcgCYpJKL mv7r+x+uQ02tuszPPi1zPw== =j0UH -----END PGP SIGNATURE-----