Hi, In the properties of the smtp virtual server, tab delivery, advanced, you
can fill a fully qualified domain name (fqdn). That is the name that comes in
the outgoing mail headers. If you change that with a fqdn that has also a
working reverse dns entry, it should work.
Or you can use the mail server of your isp to forward your mails. Ask your
isp if they support that and what is the ip address or host name of their
mail server (or just do it and see if it works). In the properties of the
smtp virtual server, tab delivery, advanced, you can fill a smart host for
outbound connections. In this tab If you put there the ip address of your's
isp mail server it must be between square brackets, ex. [188.8.131.52].
The maximum mail size limits of your isp could be a problem when your
company sends large e-mail.
> Hello all,
> Just wanted to get some ideas from you all about a problem we are
> We send all of our mail from one of our IIS SMTP servers running off
> our internal office network on a ADSL connection with a staic ip. When
> mail is sent to AOL it delays the messages, then eventually blocks them
> a few days later.
> I am guessing this is due to their spam policy and a reverse DNS query
> they carry out. In the mail header it says the message is coming from
> ourserver.localdomain and therefore the reverse DNS lookup fails.
> Someone suggested using a smart host to get around this problem. Does
> anyone have any suggestions on how to do this or how I may be able to
> use my ISP's mail servers to get around this blocking issue from AOL?