Hi Aki,
> To verify whether it's caused by antispam plugin, you could copy/move
> mail to Spam folder and see if it crashes?
That's inconclusive: I can copy stuff in and out of my Spam folder just
fine using mutt. I've never seen the crash for my user so far, which
suggests this is specific to one
On 27.09.2017 15:44, Stephan Bosch wrote:
> Op 9/27/2017 om 2:36 PM schreef Matthijs Kooijman:
>> Hey folks,
>>
>> apologies for the useless subject on my original mail, forgot to update
>> it.
>>
>> Two more bits of info. Here's the log output related to this crash:
>>
>> dovecot: imap-login: Lo
On 27.09.2017 20:14, Mark Moseley wrote:
> On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert wrote:
>
>> On 2017-09-27 16:57:44 +, Mark Moseley wrote:
>>> I've been digging into the auth policy stuff with weakforced lately.
>> There
>>> are cases (IP ranges, so could be wrapped up in remote
Just to confirm - building thunderbird 45.8.0 worked, it connects just fine.
On 09/26/2017 01:46 AM, Michael A. Peters wrote:
No, no certificate in thunderbird.
Work fine when running CentOS 7.3, laptop that still runs 7.3 works fine.
I'm going to attempt building the CentOS 7.3 thundirbird sr
On Wed, Sep 27, 2017 at 10:03 AM, Marcus Rueckert wrote:
> On 2017-09-27 16:57:44 +, Mark Moseley wrote:
> > I've been digging into the auth policy stuff with weakforced lately.
> There
> > are cases (IP ranges, so could be wrapped up in remote {} blocks) where
> > it'd be nice to skip the au
On 2017-09-27 16:57:44 +, Mark Moseley wrote:
> I've been digging into the auth policy stuff with weakforced lately. There
> are cases (IP ranges, so could be wrapped up in remote {} blocks) where
> it'd be nice to skip the auth policy (internal hosts that I can trust, but
> that are hitting th
I've been digging into the auth policy stuff with weakforced lately. There
are cases (IP ranges, so could be wrapped up in remote {} blocks) where
it'd be nice to skip the auth policy (internal hosts that I can trust, but
that are hitting the same servers as the outside world).
Is there any way to
Hey Aki,
> Can you please include excerpt of your logs too? There should be "Panic:
> ..something..." there.
I just sent those over in a reply on my original mail. Also note that
dovecot-antispam seems to be involved somehow, as noted in that mail.
> also bt full is more useful than just bt.
Lear
Can you please include excerpt of your logs too? There should be "Panic:
..something..." there.
also bt full is more useful than just bt.
Aki
On 27.09.2017 15:21, Matthijs Kooijman wrote:
> (I'm not subscribed, please keep me CC'd)
>
> Hi,
>
> since a few months I'm experiencing repeated dovecot
Op 9/27/2017 om 2:36 PM schreef Matthijs Kooijman:
> Hey folks,
>
> apologies for the useless subject on my original mail, forgot to update
> it.
>
> Two more bits of info. Here's the log output related to this crash:
>
> dovecot: imap-login: Login: user=<2014>, method=PLAIN, rip=217.122.126.195,
Hey folks,
apologies for the useless subject on my original mail, forgot to update
it.
Two more bits of info. Here's the log output related to this crash:
dovecot: imap-login: Login: user=<2014>, method=PLAIN, rip=217.122.126.195,
lip=10.42.0.13, mpid=10569, TLS, session=
dovecot: imap(2014): P
(I'm not subscribed, please keep me CC'd)
Hi,
since a few months I'm experiencing repeated dovecot crashes. I mostly
see them in the logs, I haven't had any users complain, so I haven't
looked closely until now. I was originally using an older version fro
mDebian and hoped that a newer future ver
On 28/09/17 00:11, Aki Tuomi wrote:
>> ssl=yes is not documented to work for the auth service and it's highly
>> likely that it is simply ignored.
>
> It is documented for inet_listener's in general and is not ignored. Any
> dovecot inet_listener can be given this flag.
>
> You could use stunnel
On 27.09.2017 13:21, Peter wrote:
> On 27/09/17 20:35, Thomas Bauer wrote:
>> service auth {
>> inet_listener{
>> address=192.0.0.1
>> port=10001
>> ssl=yes
>> }
>> }
> ssl=yes is not documented to work for the auth service and it's highly
> likely that it is simply ignored.
It is
Hi, this particular crash is being tracked internally. We have not been
able to fix it yet.
Aki
On 27.09.2017 13:47, David Gardner wrote:
> Hi,
> replying to my own issue:
> The dsync crash seems to be triggered when there are emails to copy in
> both directions, and it's fairly clear from comm
Hi,
replying to my own issue:
The dsync crash seems to be triggered when there are emails to copy in
both directions, and it's fairly clear from comments in the code that
it should be releasing a read lock before trying to grab a write lock.
A work-around for the crash was doing a one-way sync m
On 27/09/17 20:35, Thomas Bauer wrote:
> service auth {
> inet_listener{
> address=192.0.0.1
> port=10001
> ssl=yes
> }
> }
ssl=yes is not documented to work for the auth service and it's highly
likely that it is simply ignored.
> -o smtpd_tls_security_level=encrypt
This defin
It is possible it will be supported in future, but for now it's not
supported.
Aki
On 27.09.2017 11:33, Dimos Alevizos wrote:
> Hi,
>
> is quota-status still not supported in proxy configuration ?
> Any chance it will be in the future ?
>
> Dimos
>
> On 10/10/2016 09:06 πμ, Aki Tuomi wrote:
>> H
Hi,
is quota-status still not supported in proxy configuration ?
Any chance it will be in the future ?
Dimos
On 10/10/2016 09:06 πμ, Aki Tuomi wrote:
> Hi!
>
> quota-status is not supported in proxy configuration. You should use
> quota_warning and quota_over_flag scripts instead.
>
> Aki
>
> On
Am 27.09.2017 um 09:35 schrieb Thomas Bauer:
> On the postfix server in master.cf:
>
> submission inet n - - - - smtpd
>...
>-o smtpd_sasl_path=inet:192.0.0.1:10001
>...
You might use
-o smtpd_tls_security_level=encrypt
as well, to ensure postfix
Hi,
Am 27.09.2017 um 01:07 schrieb Raymond Sellars:
> Is it possible to secure the Dovecot SASL auth provider for postfix?
>
I'm using this configuration, which you've suggested.
> Has anyone managed to implement a secure internal approach they can share?
> I'm wondering if Postfix with Cyrus
21 matches
Mail list logo
