07-19-04 10:56 PM
Actually, Exchange Server IS compliant with the right configuration. You jus
t have to add the "@[xx.xx.xx.xx]" into a Recipient Policy, and add your
addresses as "Custom" with the address of "postmaster@[xx.xx.xx.xx]" or
"abuse@[xx.xx.xx.xx]" and type SMT
P (choosing SMTP and trying to add the address WON'T work).
I like to have ZERO warnings or errors in my testing though, so if ANYONE ca
n give me the answer on how to do this, or if it is simply NOT possible that
would be great. If it is truely NOT possible, I would like it to be a MS re
p that breaks that news to
me, thanks.
Nathan
"Jeff Henkels" wrote:
> "Nathan Kodak" <Nathan Kodak@discussions.microsoft.com> wrote in message
> news:A93511B2-73B5-4A9F-ADA4-BD6A647BA0EC@microsoft.com...
> replied to, so here it is again, in hopes of recieving an answer.
> are unsure, this RFC compliance deals with Domain Literals.
> recieve a warning from our backup MX stating that it does not accept domai
n
> literals.
> literal format (user@[0.0.0.0]). Mailservers are technically required
> RFC1123 5.2.17 to accept mail to domain literals for any of its IP
> addresses. Not accepting domain literals can make it more difficult to tes
t
> your mailserver, and can prevent you from receiving E-mail from people
> reporting problems with your mailserver. However, it is unlikely that any
> problems will occur if the domain literals are not accepted.
>
> As far as I know, the IIS mail server doesn't claim to be compliant with
> that part of RFC1123. For what it's worth, Exchange Server isn't complian
t
> either. In practical terms, this non-compliance isn't an issue -- no one
> really uses domain literals.
>
>
>
[ Post a follow-up to this message ]
|