> MD5 is optional in The Bat!, for example... Minor correction to my post: The Bat! will attempt MD5 first if announced.
There is something to be aware of here: CRAM-MD5 is not supported for external databases--but CRAM-MD5 *will* be announced if you're hitting an IP address whose primary domain is in the Registry. In this case, the MUA must try to use MD5, catch the failure, and then try to use LOGIN or another lower-security AUTH protocol instead. If an MUA tries to use MD5 because it's announced, but does *not* pursue an alternative AUTH method if MD5 fails, the session will not authenticate. Again, The Bat! deals well with this situation, provided that it hasn't been told to "never fall back." I presume the other MUAs will behave reasonably well, too, but the failure-retry-success pattern is normal. Anyway, the "non-returning function" symptom is probably not related to the MD5 question, since IMail knows ahead of time not to ask external DBs for unsupported AUTH methods, but it's good to know the bigger picture when looking at packet traces. On the firewall front, why not just set up OE on the server itself and see if it behaves any differently, rather than mucking about in your rulebase just yet? -Sandy --- [This E-mail scanned by Declude Anti-Virus] 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/
