This is a good point.  I've noticed this and tried to find a way around the 
problem with setting a default domain and creating an alias, but I've not been 
able to get any configuration to work.

Sam, is there anyway/any possibility this can be fixed on a next release?

Thanks,

D


Quoting "Giacomo A. Catenazzi" <[EMAIL PROTECTED]>:

| Hello.
| 
| Courier don't accept "Postmaster" as mailbox, as required
| by RFC 2821:
| 
| Transcript:
| 
| 220 localhost ESMTP
| HELO localhost
| 250 localhost Ok.
| MAIL FROM:<[EMAIL PROTECTED]>
| 250 Ok.
| RCPT TO:<Postmaster>
| 513 Syntax error.
| RCPT TO:<Postmaster@>
| 513 Syntax error.
| RCPT TO:<[EMAIL PROTECTED]>
| 513 Syntax error.
| 
| RFC:
| 
| According to RFC2821:
| 3.6:
|     -  The reserved mailbox name "postmaster" may be used in a RCPT
|        command without domain qualification (see section 4.1.1.3) and
|        MUST be accepted if so used.
| 
| 4.1.1.3:
|     "RCPT TO:" ("<Postmaster@" domain ">" / "<Postmaster>" / Forward-Path)
|                      [SP Rcpt-parameters] CRLF
| 
| 4.5.1:
| >    Any system that includes an SMTP server supporting mail relaying or
| >    delivery MUST support the reserved mailbox "postmaster" as a case-
| >    insensitive local name.  This postmaster address is not strictly
| >    necessary if the server always returns 554 on connection opening (as
| >    described in section 3.1).  The requirement to accept mail for
| >    postmaster implies that RCPT commands which specify a mailbox for
| >    postmaster at any of the domains for which the SMTP server provides
| >    mail service, as well as the special case of "RCPT TO:<Postmaster>"
| >    (with no domain specification), MUST be supported.
| > 
| >    SMTP systems are expected to make every reasonable effort to accept
| >    mail directed to Postmaster from any other system on the Internet.
| >    In extreme cases --such as to contain a denial of service attack or
| >    other breach of security-- an SMTP server may block mail directed to
| >    Postmaster.  However, such arrangements SHOULD be narrowly tailored
| >    so as to avoid blocking messages which are not part of such attacks.
| > 
| 
| ciao
|       cate
| 
| 
| -------------------------------------------------------
| The SF.Net email is sponsored by EclipseCon 2004
| Premiere Conference on Open Tools Development and Integration
| See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
| http://www.eclipsecon.org/osdn
| _______________________________________________
| courier-users mailing list
| [EMAIL PROTECTED]
| Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
| 




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to