Re: Best Outgoing Mail, Via DNS or ISP SMTP?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Daren wrote:

I use the POP Manager to receive mail as my ISP (BT) scans everything
for viruses, so I get a nice big fat comfort zone.

But which is best... To send mail via the ISP or via DNS and if the
answer is DNS can anybody tell me why?

*In principle* it is better to route directly via DNS, for these
reasons:

- Routing via your ISP using POP3/SMTP has the inherent delays caused
by the 15-minute Exchange send/receive cycle (and reducing this below
15 mins is not advisable). There are no such delays with direct routing.

- If you are using global (i.e., multi-user) POP3 mailboxes at your
ISP, then BCC-addressed mails cannot be routed to your users by
Exchange (this does not apply if you have individual user POP3
mailboxes, though).

- Routing via your ISP can cause your emails to be blocked by other
MTAs, since the headers of your emails will reveal your server rather
than your ISP as the origin, while only your ISP's servers will have MX
records. Some receiving MTAs will consider this spam-like behaviour and
act accordingly.

However, routing direct via DNS does require you to get all your ducks
in a row, incl. MX records, rDNS (PTR) records, and SMTP open inbound.
Unless you can sort *all* of these, stick with POP3/SMTP via your ISP.
For instance, we surveyed a number UK ISPs recently when we changed our
broadband provider, and BT (who you say you use) said they would not
open SMTP for us unless we hosted our web sites with them.

Some other issues which may be of relevance...

- You make a point of saying that your ISP scans all your emails for
viruses. Does this mean that you have no A/V scanning on your SBS?
Assuming you do have, this isn't an issue.

- Exchange's IMF + Connection filtering does a competent job of
filtering UCE (spam) - though in our case, we do find the need to
supplement it with client-based 3rd party spam filtering. That said, a
peek at Exchange 2007 suggests there are important improvements on the
way in this respect...

--
Regards,
Steve.
.



Relevant Pages

  • Re: Exchange - multiple relay?
    ... I want to change the way I send mail from a forward to ISP to DNS. ... Your firewall does not need to be listening for an incoming port 25 connection for outgoing mail. ... keeping your exchange box inaccessible from the ...
    (microsoft.public.windows.server.sbs)
  • Re: "Microsoft Location Finder" - how is it supposed to work ?
    ... Of course my home DSL points to my ISP located 12 ... >That might eventually work for DHCP settings - but not static. ... so they just convinced the RADIUS server to ... Using DNS for that is ridiculous. ...
    (alt.internet.wireless)
  • Re: Exchange Help!!!!
    ... Best not to have your ISP host your DNS, ... up on the Qwest Servers before actually changing the name servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: Bringing DNS In-house
    ... I would handle all of you internal dns resolutions internally and those addresses that you can't resolve forward to your isp. ... It is a good practice to forward all requests to your isp thereby having the ISP do all the lookup work and not expose your internal ip addresses. ... For failover I have 2 seperate internet feeds with 2 seperate ... ISP (as we use their name servers for our domain name). ...
    (microsoft.public.windows.server.dns)
  • Re: Bringing DNS In-house
    ... I would handle all of you internal dns resolutions internally and those addresses that you can't resolve forward to your isp. ... It is a good practice to forward all requests to your isp thereby having the ISP do all the lookup work and not expose your internal ip addresses. ... For failover I have 2 seperate internet feeds with 2 seperate ... ISP (as we use their name servers for our domain name). ...
    (microsoft.public.windows.server.dns)