This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author alfmel
Recipients alfmel, barry, giampaolo.rodola, josiah.carlson, r.david.murray, richard
Date 2010-08-16.19:50:59
SpamBayes Score 1.2104299e-06
Marked as misclassified No
Message-id <201008161339.55488.alberto@byu.edu>
In-reply-to <1281985087.77.0.356956867476.issue8739@psf.upfronthosting.co.za>
Content
On Monday, August 16, 2010 12:58:07 pm Barry A. Warsaw wrote:
> The one thing that looks weird to me is VRFY.  Since it never actually
> does verify the user, should we even claim to support the command?  Why
> not let subclasses claim support if they want to add it?

RFC 5321 section 4.5.1 states VRFY should be implemented in order to be 
considered an RFC 5321-compliant implementation.  But, in section 3.5.3 
paragraph 2 it states that if the actual verification was not performed but 
syntax was checked similar to RCPT, then the response code should be 252.

So my purposes for providing the plumbing for VRFY are:

1. Provide a basic, valid implementation to be as RFC 5321-compliant as 
possible.

2. Let users know the command is there so that it can be reimplemented as 
they build their solutions.
History
Date User Action Args
2010-08-16 19:51:22alfmelsetrecipients: + alfmel, barry, richard, giampaolo.rodola, josiah.carlson, r.david.murray
2010-08-16 19:50:59alfmellinkissue8739 messages
2010-08-16 19:50:59alfmelcreate