But any of the solutions mentioned (as I understand) them do require extra effort to mitigate these problems.
One of the reasons we became IMail customers was because of the ease of setting up and using the product.
I talked to Covad and they won't setup our IP for reverse DNS.
Our domain name does have an A record and MX record associated with our IP and works on the whois.
But this doesn't help with Reverse DNS.
I did try pointing our IMail SMTP gateway option to point to the Covad SMTP server, but this failed.
Covad is going to turn on Authentication starting Oct 7th, so even if this worked, it would probably be short term.
For our inter office solution we will just use the Covad SMTP server from our email clients.
However this leaves our Web Messaging partially working which our remote people are using.
As a side note I noticed that as an Earthlink customer at home stopped letting me access our business SMTP server remotely.
They must be blocking remote port 25 access now?
At 02:03 PM 9/9/2003 -0500, you wrote:
Thanks for the info.
What I described about the increasing disadvantages of trying to run mail server subscriber networks has nothing to do with Imail, or any brand of mail server.
I suspect this is going to hurt business for IMail in the long term.
no! has nothing to do with Imail. It has everything to do with where your Imail/other machine is located.
Len
_____________________________________________________________________ http://MenAndMice.com/DNS-training: San Jose; Wash DC; Dallas; Atlanta IMGate.MEIway.com: anti-spam gateway, effective on 1000's of sites, free
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/
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/
