Stefan Palme wrote:
Hello,
a little bit off topic - but maybe someone can comment this...
We are running a website where users can register themself, use
features like "send this page to a friend" etc. Those features
make the web application send an email to a user. The from
addresses (envelope FROM and header From:) are set to an
existing email address (like [EMAIL PROTECTED]).
which is the Right Thing (TM). If I get a mail, I want to be able to
reach the From or Reply-To.
It happens very very often that users enter an invalid email
address or just senseless texts. So the webmaster-address
receives all the backscatter from undeliverable mail.
This is not backscatter. this is a legitimate bounce.
Now I want to change the envelope FROM (and the header From)
address to a non-existing address (like [EMAIL PROTECTED]),
and set the Reply-To-Header to [EMAIL PROTECTED]
Instead of playing bad games, set the envelope sender to a specific
address.
The idea behind this: the backscatter caused by undeliverable
mail will go to /dev/null, while all regular replies to one
of those auto-generated emails will reach the webmaster.
and what if I want to complain by replying to the From or Reply-to? what
if as a new admin, I want you to cease sending to an old address? ... etc.
Is this the "state-of-the-art" way to solve this? Or are there
any other, better solutions?
take a look at how mailing list managers do.
[Using captchas or similar does not really solve the problem,
because even really existing human beings often enter senseless
stuff like "[EMAIL PROTECTED]" ;-)]
don't think this will be a simple projet: it is not. make sure to get it
right. every time you send a message, you will be judged. and if you are
judged wrong, you won't have any chance to fix thing (once you are in
our private ACLs, you will never be able to get out. and once
hotmail/yahoo/.... have computed your "reputation", you'll have ahard
time changing it).
