Hello all,
My scenario:
On the mail server I am using:
Mercury/32 v3.30
http://www.pmail.com/overviews/ovw_mercwin.htm
http://risc.ua.edu/pegasus-previews/m32-330.exe
MaiScan for Mail Servers v3.1a - Build: 181 SP: 2
http://www.mwti.com/
And The Bat! v1.53d on client machines.
I am actually evaluating MailScan and I am having a problem when
sending e-mail with large (> 1MB) attachments. I'll explain.
I have Mercury set up for SMTP Authentication to avoid relaying of
spam. Mercury supports both simple LOGIN and secure (MD5)
authentication and so does The Bat!. But it looks like MailScan only
supports LOGIN and this seems to be a problems when sending large
attachments (would be too long to explain why now).
Although I have The Bat! set up for simple authentication, because
Mercury supports MD5, TB will use MD5. This is what TB's help says:
Once connected to an SMTP server, The Bat! checks which of the
server's RFC-2554-authentication mechanisms is available, and
chooses the most secure. Even when "Require secure (MD5)
authentication" is off, if the server does supports it, secure
authentication will take place.
My question is: is there any way I can force TB to use 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://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Unsubscribe: mailto:[EMAIL PROTECTED]
Latest Vers: 1.53d
FAQ : http://faq.thebat.dutaint.com
