Mark Alan:
> This issue is not present without postscreen. Could it be related to it or
>- with the tlsproxy service?
Perhaps surprisingly, both smtpd and tlsproxy specify the same
parameters to OPENSSL (*). If you tweek them, then you may see
differences.
Wietse
(*) I can't imagine why
Mark Alan:
> In any case setting 'smtpd_tls_mandatory_exclude_ciphers = AES128, DES,
> MD5, aNULL' should not interfere with postfix ability to choose from
> the strongest to the weakest of the remaining ciphers (as shown by
> openssl ciphers -v 'ALL:@STRENGTH')
>
> Is it a postfix bug? If so, I
On Sun, 22 May 2011 22:00:49 -0500, Noel Jones
wrote:
> Is postfix also the client? What are the settings on that
> machine?
Client machines use Claws Mail as MUA (configured to use SMTP at 587)
and those machine have Postfix as the MTA, configured like this:
$ sudo postconf -n | grep -v '^smt
On 5/22/2011 4:27 AM, Mark Alan wrote:
Hello list,
While using ubuntu 10.10, postfix 2.8.1, dovecot 2.0.12, openssl
0.9.8o, and trying to connect to the mail server via postfix
'submission' the best cipher that I am able to get is
DHE-RSA-AES128-SHA (128/128 bits)
As it is only the 11th entry
Hello list,
While using ubuntu 10.10, postfix 2.8.1, dovecot 2.0.12, openssl
0.9.8o, and trying to connect to the mail server via postfix
'submission' the best cipher that I am able to get is
DHE-RSA-AES128-SHA (128/128 bits)
As it is only the 11th entry in the list showed by
openssl ciphers -v
