[EMAIL PROTECTED] wrote:
What, exactly, is being done to validate sender/recipient email addresses
during a connection?
I am finding that there are many, otherwise legit, addresses with local
portions that are too long. RFC 2821 4.5.3.1 says 64 characters maximum,
yet I regularly see much longer (last one I checked was 102 characters)
from ezmlm-ndx, Yahoo, and Google mailing lists.
Should this be enforced, ignored, reported?
The paragraph before the limits are defined in rfc2821 says:
There are several objects that have required minimum/maximum sizes.
Every implementation MUST be able to receive objects of at least
these sizes. Objects larger than these sizes SHOULD be avoided when
possible. However, some Internet mail constructs such as encoded
X.400 addresses [16] will often require larger objects: clients MAY
attempt to transmit these, but MUST be prepared for a server to
reject them if they cannot be handled by it. To the maximum extent
possible, implementation techniques which impose no limits on the
length of these objects should be used.
So in a way, the 'maximum' is a minimum that software needs to accept. The last
sentence of the paragraph addresses your question nicely, I think.
Elliot
