2 messages in net.sourceforge.lists.courier-users[courier-users] Problem with Client "...
FromSent OnAttachments
Peter HolmAug 1, 2001 12:43 pm 
Peter HolmAug 1, 2001 1:29 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Problem with Client "The BAT"Actions...
From:Peter Holm (PHo@gmx.de)
Date:Aug 1, 2001 12:43:12 pm
List:net.sourceforge.lists.courier-users

Hi,

there is a problem with a client which is called "The Bat" and can be found on www.ritlabs.com. I don´t know exactly, what´s going wrong, but it is not possible to send mail with authentication with this client.

The server has no problems receiving mails from Outlook Express, what seems to use plain authentication (?)

I downloadad that mailclient myself and had no success with any configuration. Because I am a little bit confused about different smtp-auth-mechanisms, I just post some parts of the Helpfile and hope, somebody could give me a hint. Before fiddling around with my courier-configuration I would like to ask, if somebody knows about that client and if it "should go". THANKS!!!

---snip from "The Bat Help" ------------------- Using RFC-2554, SMTP authentication involves a username and a password being transferred from the client to the server. If the username and the password for SMTP authentication are the same as for POP3 authentication, you can check "Use Settings of Mail Retrieval". Otherwise, check "Use Specific Settings" and specify the username and the password.

Regardless of which settings you are using, either specific or those of mail retrieval - you can avoid sending the password as cleartext by checking the "Require secure (MD5) authentication" box. This will activate the CRAM-HMAC Challenge/Response authentication mechanism, which, however, may not be supported by all servers.

Please note that if you check "Require secure (MD5) authentication" and the server does not support this secure authentication mechanism, there will be no authentication at all, and the mail session will continue as unauthenticated. Under no circumstances will The Bat! pass a cleartext password over a network during RFC-2554 authentication when "Require secure (MD5) authentication" is on.

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.

Have a nice thread, Peter