Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: mohamad rahimi (rahimi992yahoo.com)
Date: Sun Apr 25 2010 - 14:05:13 CDT
From: Victor Duchovni <Victor.Duchovnimorganstanley.com>
Sent: Sun, April 25, 2010 8:17:11 PM
Subject: Re: Authentication problem with Thunderbird
On Sun, Apr 25, 2010 at 10:18:57AM -0700, mohamad rahimi wrote:
> >> "Unable to authentication to SMTP server mx.mydomain. The server does not
> > >support any compatible secure authentication mechanism but you have chosen
> > >secure authentication. Try switching off secure authentication."
> >"Secure Authentication" means no plaintext passwords, i.e. GSSAPI,
> >CRAM-MD5, ... Are you sure you have support for mechanisms other than
> >"PLAIN"? If not, don't tell Thunderbird to try and use them...
>> I am sure our mail server had the mechanisms for Secure Authentication.
>What do you mean when you say this? Which non-plaintext SASL mechanisms
>does your server support, and how?
>> my question is that how can I understand that now our mail server
>> support this mechanisms and how can I run this.
>The above sentence does not make sense in English I am afraid. :-(
Sorry for inconvenient in my explanation. In my first email I told that this problem happened after restart the firewall and mail server before that I did not have this problem and it means Secure Authentication mechanisms worked.
I don't know Which non-plaintext or plaintext SASL mechanisms my server support.
how can I find out?
- application/octet-stream attachment: output