...
66.148.217.251 domain.com
70.60.133.251 domain.com
will this mechanism rotate through both IPs or will it also
just use whichever it hits first when reading from the top of
the list down? Or is it just a bad idea in general to do
this and we will just have to change the IP
@declude.com
Subject: RE: [Declude.JunkMail] OT: Store and Forward Spam Filtering
to
Multiple IPs
...
66.148.217.251 domain.com
70.60.133.251 domain.com
will this mechanism rotate through both IPs or will it also
just use whichever it hits first when reading from the top of
the list
Or is it just a bad idea in general to do this and we will just have
to change the IP manually if one ISP goes down?
Being able to use the DNS MX algorithm for gatewayed domains is not a
bad idea at all -- it's preferable to hard-coding a single MX route in
HOSTS. However, to do this you
Sandy,
Naturally Ipswitch's method is a major root of the issue. I like
IMail's Spool and it's simplicity in finding and understanding
messages. MS SMTP however encodes the equivalent of the Q file and it
is important to be able to see that information. So all other things
being equal, I
BTW, you can trick IMail. You need to be gatewaying through another
server, MS SMTP for instance and set up that address (gateway) in the
allowed addresses under the IMail SMTP service. That takes care of
IMail accepting everything from your gateway(s) regardless of the Hosts
file entries.
