Well, I put my new iMS server into production early this morning, and it works! Yes,
of course I expected it to, but it's still cool :-) No more open spam relay with
NTMail! woohoo!
Anyway, pardon my excitement...
What's the point of the BadMes folder? I see delivery failures in POST log with null
returns (from a list, so as it should be), and I expect the bad messages to appear in
the BadMes folder (ala NTMail's BadMes folder). But they just disappear. Can I enable
them to be saved in BadMes somehow?
Also I see MX lookups failing occasionally. I have 3 DNS servers defined in the POST
config. 2 of them are on the same LAN, and another is just a few hops away. All 3 are
fast. I did notice at least 2 permanent MX lookup failures in the logs today-- one to
ptwi.com and one to bolt.com. These domains DO have MX records. However, iMS
apparently gave up looking for a MX, and deleted the outgoing mail file, after
claiming a timeout from all DNS servers. I have the MX resolve timeout set to 60
seconds (at 30 seconds I was getting a lot of timeouts). Now, I didn't get a chance
to check these MX's until a few hours after the failures, so perhaps both DNS servers
for those domains were down at the time... but that doesn't seem likely. Actually I
see several failures of this type, but then there are some successes also, for the
same domains (eg. bolt.com). Anyone else notice this? What could be happening? This
is especially disturbing considering what I said above-- that the bad email just gets
deleted. I should say that I had no MX resolution problems with my previous mail
system, using the same DNS servers.
Thanks!
-Max
������������������������ This list server is Powered by iMS
'The Swiss Army Knife of Mail Servers'
--------------------------------------
To leave this list please complete the form at
http://www.CoolFusion.com/iMS.htm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
�����������������������==
