🚀 go-pugleaf

In article <7FFQ3IC@methan.chemie.fu-berlin.de> admin@methan.chemie.fu-berlin.de writes:
>
>I have problems with this because this might be a valid X.400 address but
>this is NOT a valid RFC822 address. You are not allowed to use the
>character "/" in a RFC822 address (I know there are differences in
>the various RFCs but the newest say that "/" is forbidden).

  There is nothing in RFC822, nor RFC1123 (which updates 822) that bans
the use of '/'.  It is a perfectly valid character in the local part of
an address.

>Our MTA (smail 3.1.20) says that this address has an invalid character
>and refuses such an address. The most MTAs of the European backbones 
>refuses such an address too. 

 Sounds like your MTA is broken.

 To clarify.  The '/' character is permitted in the local part.  Your MTA
does not have to permit it in the local part of mail addressed to your
domain.  But it should permit it in the local part of mail addressed to
other domains.  The difference here is that your MTA interprets the contents
of the local part only when the message is addressed to your own domain.


-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940