Hi Johannes, > Mhh. It seems I don't get something I'd like to understant :) If both > the server and the client support a stronger AUTH mechanism, and your > AV tool is hooked into the TCP/IP-Stream, opposed to being a > "server"/listening on it's own port, then why would this clash? MD5 is > only used for the preliminary authentication, enabling a relay.
It is due to a "design feature" in MailScan that has been already addressed by developers and will be fixed soon. It only happens when sending "large" attachments. It looks like (more or less) MailScan thinks it is going to take too long to scan the attachment for viruses, so it "grabs" the message and the attachment to allow the connection between TB and Mercury to close. Then it passes the attachment to the virus scanner and, if safe, it will have to open a new connection with the server (Mercury) to actually send the message and the attachment. Here is where MD% authentication fails and the message is not sent at all. However, if I could "force" TB to use simple authentication, it would not fail. If, for example, I use Outlook Express to send the same attachment it goes through with no problem because OE only uses simple authentication -- Best regards, Miguel A. Urech (El Escorial - Spain) Using The Bat! v1.53d ************************************************************** Scanned by MailScan Content-Security and Anti-Virus Software. Visit http://www.mwti.net for more info on eScan and MailScan. ************************************************************** -- ______________________________________________________ Archives : http://tbtech.thebat.dutaint.com Moderators : mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED]
