SMTP behavior: 553 5.5.2 Bad command format(h)
WTF? can anyone please explain me why must I enclose my address between the "<>"? 220 cassiopeia.remeyewear.com ESMTP service helo me.intercom.com.sv 250 cassiopeia.remeyewear.com talking to ip168-243-227-1 .243.227.171]) mail from:postmaster@intercom.com.sv 553 5.5.2 Bad command format(h) mail from: postmaster@intercom.com.sv 553 5.5.2 Bad command format(h) mail from:<postmaster@intercom.com.sv> 250 OK - mail from <postmaster@intercom.com.sv> quit 221 cassiopeia.remeyewear.com connection Connection to host lost. -- Miguel Mata-Cardona Intercom El Salvador mmata@intercom.com.sv voz: ++(503) 278-5068 fax: ++(503) 265-7024
On Wed, 31 Mar 2004, Miguel Mata-Cardona wrote:
WTF? can anyone please explain me why must I enclose my address between the "<>"?
In message <Pine.LNX.4.33L2.0403311519260.1938-100000@twomix.devolution.com>, S cott Call writes:
On Wed, 31 Mar 2004, Miguel Mata-Cardona wrote:
WTF? can anyone please explain me why must I enclose my address between the "<>"?
Yup -- that's what the spec says. See, in particular, 4.1.1.2, which gives the syntax of the MAIL FROM: command, and 4.1.2, which gives the syntax of a Reverse-path. There are some SMTP servers which don't require the <>, but they're being generous -- they've always been required. --Steve Bellovin, http://www.research.att.com/~smb
On Wed Mar 31, 2004 at 05:16:41PM -0600, Miguel Mata-Cardona wrote:
WTF? can anyone please explain me why must I enclose my address between the "<>"?
Because the RFC says you should. Even back in RFC821 this was the case: MAIL <SP> FROM:<reverse-path> <CRLF> <reverse-path> ::= <path> <path> ::= "<" [ <a-d-l> ":" ] <mailbox> ">" Simon -- Simon Lockhart | Tel: +44 (0)1628 407720 (x(01)37720) | Si fractum Technology Manager | Fax: +44 (0)1628 407701 (x(01)37701) | non sit, noli BBC Internet Ops | Email: Simon.Lockhart@bbc.co.uk | id reficere BBC Technology, Maiden House, Vanwall Road, Maidenhead. SL6 4UB. UK
participants (4)
-
Miguel Mata-Cardona -
Scott Call -
Simon Lockhart -
Steven M. Bellovin