On 05/17/2017 11:40 AM, Patrick Goetz wrote:
So, running
openssl s_client -connect mail.myserver.org:143 -starttls imap
Same error with -tls1_2 ?
openssl s_client -connect mail.myserver.org:143 -tls1_2 -starttls imap
it appears that it's still trying to use SSLv3 and the newest
Hi Ellie,
thank you! Are there any Ubuntu packages available as I don't think the
Debian/Ubuntu maintainers will patch their packages.
Ciao
Marcus
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
Thanks everyone; this is as I expected.
On 05/17/2017 10:04 AM, Jason Englander wrote:
On Wed, 17 May 2017, Patrick Goetz wrote:
I had to update my mail server for unrelated reasons, after which I
couldn't get cyrus-master to start. It turned out to be related to
ctl_cyrusdb not running
Hi -
No, the private key and certificate should match; I'm using the same
key/cert pair for webmail, and that one works fine. I'm still thinking
cyrus 2.5.10 isn't compatible with the newest version of openssl. Here
is the "enumerate ciphers" nmap output for the mail, and webmail
servers,
On Wed, 17 May 2017, Patrick Goetz wrote:
before I start googling, can someone tell me how to disable SSLv3 in
imapd.conf?
Possibly not relevant because of the other post, but the answer is:
man imapd.conf
->
tls_ciphers
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info:
Follow up question:
The package maintainer for the Arch cyrus-imapd package has fallen
behind and my users need to be able to access their mail, so as a
temporary work around I'm just going to build/compile cyrus 3.0.1 from
source.
I asked about some of this before, but will my 2.5.10
On 05/17/2017 12:04 PM, Jason Englander wrote:
On Wed, 17 May 2017, Patrick Goetz wrote:
I had to update my mail server for unrelated reasons, after which I
couldn't get cyrus-master to start. It turned out to be related to
ctl_cyrusdb not running because the program was compiled against
Hi lists
After update 2.4.17 to 2.5.10 at CentOS 7.3 I've started see messages in
maillog:
...
May 15 10:04:50 server imaps[22927]: mailbox: longlock shared.folder for 1408.2
seconds
May 15 12:52:27server imaps[30558]: mailbox: longlock shared.folder for 1925.0
seconds
...
May 17 13:33:15
On Wed, 17 May 2017, Patrick Goetz wrote:
I had to update my mail server for unrelated reasons, after which I
couldn't get cyrus-master to start. It turned out to be related to
ctl_cyrusdb not running because the program was compiled against
libssl.so.1.0 while this library had been upgraded
On 05/17/2017 10:54 AM, Patrick Goetz wrote:
Follow up question:
The package maintainer for the Arch cyrus-imapd package has fallen
behind and my users need to be able to access their mail, so as a
temporary work around I'm just going to build/compile cyrus 3.0.1 from
source.
I asked about
Try:
elsif header :matches "subject" "[proxy] File-URL (.*) detected"
On 5/16/2017 9:53 AM, Walter H. via Info-cyrus wrote:
> Hello,
>
> I've got the following in the sieve script
>
> elsif header :matches "subject" "[proxy] File-URL (*) detected"
> {
> fileinto "INBOX._Info.ftpFileURLs";
Hello,
with the, there is not any match ...
'.*' would be a regular expression matching anything,
but sieve filter language doesn't support regular expressions, or does it?
I did a workaround on the other side, I did a reverse DNS lookup, and
most times
there is a DNS name instead of an IP
I had to update my mail server for unrelated reasons, after which I
couldn't get cyrus-master to start. It turned out to be related to
ctl_cyrusdb not running because the program was compiled against
libssl.so.1.0 while this library had been upgraded to libssl.so.1.1
So, I recompiled cyrus
> The Cyrus team is proud to announce the immediate availability of a new
> version of Cyrus IMAP: 2.4.19.
I've just updated our cyrus-imapd rpms from 2.4.18 -> 2.4.19. All seems
well with just some small changes to the build.
However, I just can't get it to work: lmtpd segfaults on mail
So, running
openssl s_client -connect mail.myserver.org:143 -starttls imap
it appears that it's still trying to use SSLv3 and the newest version of
openssl won't allow this?
===
[pgoetz@frog ~]$ openssl s_client -connect mail.myserver.org:143
-starttls imap
Patrick Goetz wrote on 17/05/17 16:40:
> SSL alert number 40
This error has nothing to do with SSLv3 or protocol version at all. Maybe your
private key and certificate do not match on server side.
Greetings, Wolfgang
--
Wolfgang Breyha | http://www.blafasel.at/
Vienna
16 matches
Mail list logo