[Savannah-hackers] [support #103380] Savannah MTA seems to request VRFY info before accepting mail

[Jesus M. Gonzalez-Barahona]

This mail is an automated notification from the support tracker
 of the project: Savannah Administration.

/**************************************************************************/
[support #103380] Latest Modifications:

Changes by: 
                Jesus M. Gonzalez-Barahona <address@hidden>
'Date: 
                Wed 09/22/04 at 15:56 (GMT)

------------------ Additional Follow-up Comments ----------------------------
I know it is RFC compliant, but as far as I know it is not mandatory (excuse me 
if I'm wrong). In any case, we have a collaborator who cannot contribute, and 
is not able of changing the policy of  his site. I know the reasons for them  
not accepting VRFY are at the very least arguable, but it is not likely they 
are going to change that (I know he has already tried that way). Maybe we can 
be a bit flexible here,  I don't know...






/**************************************************************************/
[support #103380] Full Item Snapshot:

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=103380>
Project: Savannah Administration
Submitted by: Jesus M. Gonzalez-Barahona
On: Mon 09/20/04 at 22:21

Category:  Mail server
Priority:  5 - Normal
Severity:  9 - Blocker
Resolution:  None
Privacy:  Public
Assigned to:  Beuc
Originator Email:  address@hidden
Status:  Open


Summary:  Savannah MTA seems to request VRFY info before accepting mail

Original Submission:  We are having a user of our mailing lists who is trying 
to send mail to it, but the Savannah mail server seems to reject accepting it, 
apparently because it is asking for VRFY info to the user's MTA. The user's MTA 
dod not support VRFY for security reasons. We wonder whether this VRFY check 
can be avoided. This is blocking for us because the messages by that user are 
important for the project. The user is address@hidden

Follow-up Comments
------------------


-------------------------------------------------------
Date: Wed 09/22/04 at 15:56         By: Jesus M. Gonzalez-Barahona <jgb>
I know it is RFC compliant, but as far as I know it is not mandatory (excuse me 
if I'm wrong). In any case, we have a collaborator who cannot contribute, and 
is not able of changing the policy of  his site. I know the reasons for them  
not accepting VRFY are at the very least arguable, but it is not likely they 
are going to change that (I know he has already tried that way). Maybe we can 
be a bit flexible here,  I don't know...

-------------------------------------------------------
Date: Wed 09/22/04 at 14:28         By: Elfyn McBratney <beu>
quick comment from the sidelines: this is RFC-compliant behaviour.  It's the 
MTA/MUA that's broken, if they don't respond to VRFY/VERP's properly.  Not 
supporting VRFY (for whatever reasons) should be avoided, IMO, and not 
white-listed.

-------------------------------------------------------
Date: Tue 09/21/04 at 21:05         By: Sylvain Beucler <Beuc>
I forwarded the request to the system administrators, who are in charge of the 
mail system (we don't have access there).




CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
dmegias --AT-- uoc --DOT-- edu      | 









For detailed info, follow this link:
<http://savannah.gnu.org/support/?func=detailitem&item_id=103380>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/