On 05/05/2016 01:00 AM, deoren wrote:
> Goal:
>
> 1) Setup a Google Calendar entry for a biweekly task
> 2) Configure the email notification schedule
> 3) When the email notification from Google arrives have Sieve send a
> notification to an alias I have setup for my cell provider's email to
> text
> ssl_dh_parameters_length = 2048
>
> Probably not related to your problem, but this will cause wildly variable
> dovecot initialization times, as temp key generation of this length
> can result in a lot of candidate primailty testing.
>
The key generation is done once an
On 5/5/2016 10:42 AM, Gedalya wrote:
On 05/05/2016 01:00 AM, deoren wrote:
Goal:
1) Setup a Google Calendar entry for a biweekly task
2) Configure the email notification schedule
3) When the email notification from Google arrives have Sieve send a
notification to an alias I have setup for my ce
On 05/05/2016 01:02 PM, deoren wrote:
> On 5/5/2016 10:42 AM, Gedalya wrote:
>> On 05/05/2016 01:00 AM, deoren wrote:
>>> Goal:
>>>
>>> 1) Setup a Google Calendar entry for a biweekly task
>>> 2) Configure the email notification schedule
>>> 3) When the email notification from Google arrives have S
On 05/05/2016 01:33 PM, Gedalya wrote:
> you just might be able to set that up to test for the right conditions *when*
> to do this, and then proceed to remove the header
Maybe using PCRE negative lookaheads
/^Subject: (?!google-calendar-notification)/DUNNO
/^From: (?!google)/DUNNO
/^Aut
Well, they're empty. So whatever is causing this delay, it's silent.
Yves Goergen
http://unclassified.software
Von: Steffen Kaiser
Gesendet: Mo, 2016-05-02 08:39 +0200
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 1 May 2016, Yves Goergen wrote:
I configured Dovecot on our mail server under Centos 5.3 (I think) some while
ago now (about 2 years) and, to the best of my knowledge,it had been working
correctly all that time.
However, one of the team wanted to use webmail while away from base and found
that, although he could receive email
On 05/05/16 14:40, Chris Smith wrote:
I configured Dovecot on our mail server under Centos 5.3 (I think) some while
ago now (about 2 years) and, to the best of my knowledge,it had been working
correctly all that time.
However, one of the team wanted to use webmail while away from base and fo
Hello all, thank you again for your help.
Thanks to Edgar Pettijohn's inspiration, we changed /etc/dovecot/conf.d
/10-auth.conf to include login (which did not work) and cram-md5 (whichdid
work):
auth_mechanisms = plain login cram-md5
and we no longer get Connection refused.
(Note: I am not subscribed to this ML, so please be sure to CC me in replies.)
Hello,
I see a strange bug when running dovecot under btrfs with a mailbox in mdbox
format. At some point, which can take a few minutes or more than a day,
dovecot starts logging pread() failures, like so:
Apr 02 2
> On 5 May 2016, at 21:03, Edgar Pettijohn wrote:
>
>
>
> On 05/05/16 14:40, Chris Smith wrote:
>> I configured Dovecot on our mail server under Centos 5.3 (I think) some
>> while ago now (about 2 years) and, to the best of my knowledge,it had been
>> working correctly all that time.
>>
>>
On 05 May 2016, at 16:21, Marc Joliet wrote:
>
> (Note: I am not subscribed to this ML, so please be sure to CC me in replies.)
>
> Hello,
>
> I see a strange bug when running dovecot under btrfs with a mailbox in mdbox
> format. At some point, which can take a few minutes or more than a day,
C. Andrews Lavarre writes:
Presumably, as Joseph shows with his nc call, imap calls are to ServerName
mail.privustech.com.
No, nc is just a dumb tool -- it knows nothing about IMAP or SSL. You didn't
even get to the SSL handshake. Your problem has nothing to do with the
interaction of clien
13 matches
Mail list logo