The Fix: Get a SERVER grade 3 Com Network Interface Card for your DNS Server.
This card runs about $100 and after placing this card on our Main DNS Server all the problems went away. We had a 3 Com card on that server but not a SERVER grade card. This made all the difference. The card we used is 3COM 3CR990SVR97.
I'm very skeptical that changing a NIC in a DNS server would stop false unknown user rejects by AOL's MXs.
I have to agree with Len on this.
The *only* affect that changing a NIC card on the DNS server should be able to do is alter the DNS results that IMail gets.
But, if IMail wasn't getting the correct DNS results, the log file entries would show that. So either you didn't notice key information (examining the log file entries for bounced E-mails is the ONLY way to find out what is happening -- you check to see why the E-mail bounced (a 550, 10054 error, etc.), and make sure IMail connected to the correct IP), or IMail was getting the correct information (in which case a new NIC card won't help).
In your case, it was money very well spent (as in you spent the money, and the problem is now gone). But for other people, it's no better than kicking the server (with one very rare exception -- if they look at their log files, and IMail is going to incorrect IPs, and it isn't due to the IMail "Using-the-A-record-instead-of-MX-record" bug).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask about our free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
