>In an email address? You sure about that?
>
>Hmm, that would certainly suck.
>1) It means I'm wrong.
>2) It means I have to change my own email validation code. ;)
>
>I would assume this is in an RFC somewhere. Anyone know where?
I think it's with Lookout where users get the recipient address screwed up
send it out with tick marks. Here's IMgate/postfix complaining:
Out: 220 mgw1.MEIway.com - ESMTP - Postfix Relay Hub - ATTN: UCE trespassers
will be pursued.
In: EHLO smtp.modsys.com
Out: 250-mgw1.MEIway.com
Out: 250-PIPELINING
Out: 250-SIZE 40000000
Out: 250-ETRN
Out: 250 8BITMIME
In: MAIL FROM:<[EMAIL PROTECTED]> SIZE=5222
Out: 250 Ok
In: RCPT TO:<'[EMAIL PROTECTED]'>
Out: 504 <'[EMAIL PROTECTED]'>: Recipient address rejected: need
fully-qualified address
In: RCPT TO:<'[EMAIL PROTECTED]'>
Out: 504 <'[EMAIL PROTECTED]'>: Recipient address rejected: need
fully-qualified address
In: QUIT
Out: 221 Bye
... what postfix is saying is the the envelope recipient is not fully
qualified (broken by the ticks), and we have a policy to reject such mail.
postfix is pretty darn sticky about RFC compliance, so I'm pretty sure that
tick marks, at least in the envelope sender and recipient, aren't kosher.
Len
http://MenAndMice.com/DNS-training
http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K
http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
