It could be that the "Secure SMTP (TLS)" setting means trying to use
TLS/SSL on connect, that is, just after the connection is opened. This
will not work. On port 25, exim uses the STARTTLS convention, in which a
normal unencrypted connection is opened and follows the SMTP protocol
normally, until the client issues the STARTTLS command. The server sends
and "OK" message, and only then the TLS handshake starts.
I don't know how (and if) SquirrelMail can be configured to use
STARTTLS. It is possible, however, to configure exim to listen on
another port using the TLS-on-connect convention.
However, if SquirrelMail and exim are on the same host, connecting via
the loopback interface (which seems to be case, since you specified
127.0.0.1 as the SMTP host), you should not need to worry that the
connections are encrypted.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
I don't know how (and if) SquirrelMail can be configured to use STARTTLS. It is possible, however, to configure exim to listen on another port using the TLS-on-connect convention.
However, if SquirrelMail and exim are on the same host, connecting via the loopback interface (which seems to be case, since you specified 127.0.0.1 as the SMTP host), you should not need to worry that the connections are encrypted.
>From there, it seems Squirrelmail supports both TLS-on-connect (which
uses port 465) and STARTTLS, which I think is preferred. It does not
make clear how to specify which method is used, though.
To use TLS-on-connect, you must make sure that Postfix is configured to
listen on this port for that kind of connection.
> Yes,Squirrelmail and Postfix are on the same host.Yes,I know if i
> connect to localhost,I dont need TLS but some clients are using
> Thunderbird so I can not disable TLS support from Postfix main.cf
> <http://main.cf/>
Can't Postfix be configured to allow plain text auth only in encrypted
connections OR if the connection comes from localhost?
Another possibility, if SquirrelMail supports is, would be for it to
call the mailer directly (generally, this is done by invoking
/usr/lib/sendmail) instead of making a SMTP connection.
> In addition to I disabled TLS and I configured on either CRAM-MD5* and
> DIGEST-MD5* authentication and worked without any problem on squirrelmail.
> But this time,only (!) DIGEST-MD5 did not work on Thunderbird.CRAM-MD5
> worked on Thunderbird.
> If i use DIGEST-MD5 mechanism,Thunderbird print error "Your Server
> doesnt support security authentication...."
> Interesting !! I can use DIGEST-MD5 mechanism and login IMAP and SMTP
> server with Evolution without problem.
>
> This is Thunderbird bug ? or DIGEST-MD5 mechanism could not been
> sensed by Thunderbird ? anybody have an idea(s) ?
>
> * I read and benefit from
> http://wiki.dovecot.org/Authentication/PasswordSchemes and
> http://wiki.dovecot.org/Authentication/Mechanisms sources web address.
I'm not sure what Thunderbird supports and what it doesn't. But is not
unlikely that some methods are not supported .
--
Morava tão longe, que o carteiro mandava suas cartas pelo correio.
-- Jô Soares
Eduardo M KALINOWSKI
edu...@kalinowski.com.br
http://move.to/hpkb
I had the same problem a month before and during my search I found pages
mentioning thunderbird doesn't support DIGEST-MD5.
--
Thomas Preud'homme
Why debian : http://www.debian.org/intro/why_debian
I had the same problem a month before and during my search I found pages
mentioning thunderbird doesn't support DIGEST-MD5.