"You must be careful what you choose for after the @"
For what purpose? Nothing in OE help files warned me that I must be very
careful about this. I guess you mean because someone else will get the spam
that would have otherwise be targeted at me for inputting my real address
which I am also not warned about.

Well, Good! I have a good mind to change the address to something like
billgates@microsoft .com or someone elses address at microsoft so that they
will get bombarded with spam, and maybe wake up to how the spammers are
harvesting off their own network and put a fix to it.

Maybe we should all make our addresses appear that way to send them the
message. So long as the spam ain't being targeted at me. Thanks for the
great idea Kath. Now let me see if I can find a good email address at
microsoft to copy hahahaha

"Robert Aldwinckle" wrote in message
...
"Kath Adams" wrote in message

...

Robert,
It's always worked ok for me? For example :-

The message could not be sent because one of the recipients was rejected
by
the server. The rejected e-mail address was '.
Subject 'test', Account: 'mail.mvps.org', Server: 'mail.mvps.org',
Protocol:
SMTP, Server Response: '501 5.5.2 Syntax error in address
', Port: 25, Secure(SSL): No, Server Error:
501,
Error Number: 0x800CCC79


I guess that server doesn't implement that part of the RFC then.

OTOH I'm not even clear about how widely implemented RFC2822
is or should be.

It was mostly an ironic comment about its implications for some kinds
of antispamming techniques.



Robert
---