Why does qpsmtpd accept email addresses that contain characters like 'é'
(eacute), which aren't really defined?
RFC 2821 says:
Systems MUST NOT define mailboxes in such a way as to require the use
in SMTP of non-ASCII characters (octets with the high order bit set
to one) or ASCII "control characters" (decimal value 0-31 and 127).
These characters MUST NOT be used in MAIL or RCPT commands or other
commands that require mailbox names.
and
SMTP servers
that receive a command in which invalid character codes have been
employed, and for which there are no other reasons for rejection,
MUST reject that command with a 501 response.
Yet, qpsmtpd even goes out of its way to quote them:
Connection from [62.150.84.61] [62.150.84.61]
remote host said nothing spontaneous, proceeding
220 example.com ESMTP
dispatching EHLO in1.smtp.messagingengine.com
250-example.com Hi [62.150.84.61] [62.150.84.61]
250-PIPELINING
250-8BITMIME
250 SIZE 3174400
dispatching MAIL FROM:<[EMAIL PROTECTED]>
full from_parameter: FROM:<[EMAIL PROTECTED]>
from email address : [<[EMAIL PROTECTED]>]
using /home/smtpd/data/denysoft_greylist.dbm as greylisting database
key 62.150.84.61:[EMAIL PROTECTED] initial DENYSOFT,
unknown
getting mail from <"heartbrokeprot\.g\.s"@imap-mail.com>
250 <"heartbrokeprot\.g\.s"@imap-mail.com>, sender OK - how exciting
to get mail from you
(the dots in heartbrokeprot.g.s are eacutes, like heartbrokeprotégés)
Is there a plugin to throw these out? Shouldn't qpsmtpd proper do this?
Hans
