> Am 04.04.2017 um 12:58 schrieb Wietse Venema :
>
> I posted two-line patch that should work with 3.1 and 3.2 (developed for 3.3).
Applied, tested, works. Problem solved
Thanks
Christian
>
> Wietse
>
> Christian Ro??ner:
>> Hi Victor,
>>
>> do you have a patch that works for Postfix
I posted two-line patch that should work with 3.1 and 3.2 (developed for 3.3).
Wietse
Christian Ro??ner:
> Hi Victor,
>
> do you have a patch that works for Postfix-3.2.0? I tried to apply the patch
> below, but it does not succeed.
>
> Thanks
>
> Christian
>
> --
Hi Victor,
do you have a patch that works for Postfix-3.2.0? I tried to apply the patch
below, but it does not succeed.
Thanks
Christian
-
On Mon, Apr 03, 2017 at 02:03:41PM -0400, Viktor Dukhovni wrote:
> > Any idea is welcome.
>
> For Postfix 3.2.0 see: https://g
On Mon, Apr 03, 2017 at 02:03:41PM -0400, Viktor Dukhovni wrote:
> > Any idea is welcome.
>
> For Postfix 3.2.0 see: https://github.com/vdukhovni/postfix/pull/8
> For 3.3-20170218, see: https://github.com/vdukhovni/postfix/pull/7
>
> The underlying patch is identical. There could be other ways
> On Apr 3, 2017, at 1:24 PM, Christian Rößner
> wrote:
>
> Any idea is welcome.
For Postfix 3.2.0 see: https://github.com/vdukhovni/postfix/pull/8
For 3.3-20170218, see: https://github.com/vdukhovni/postfix/pull/7
The underlying patch is identical. There could be other ways
to address the
> Am 03.04.2017 um 17:53 schrieb Wietse Venema :
>
> Christian Ro??ner:
>> I did the opposite test now and disabled the smtpd_milter_maps
>> parameter. After that I did the same tests again and milters work
>> always. So enabling this map starts producing the described issue.
>
> And the problem
Christian Ro??ner:
> I did the opposite test now and disabled the smtpd_milter_maps
> parameter. After that I did the same tests again and milters work
> always. So enabling this map starts producing the described issue.
And the problem persists across stopping and starting Postfix,
therefore the
> Am 03.04.2017 um 16:47 schrieb Christian Rößner
> :
>
>>
>> Am 03.04.2017 um 16:07 schrieb Christian Rößner
>> :
>>
>>>
>>> Am 03.04.2017 um 15:43 schrieb Wietse Venema :
>>>
>>> Wietse Venema:
> After I ran this (in fact I was too slow ;-) ), I sent a mail from
> external MTA m
> Am 03.04.2017 um 16:07 schrieb Christian Rößner
> :
>
>>
>> Am 03.04.2017 um 15:43 schrieb Wietse Venema :
>>
>> Wietse Venema:
After I ran this (in fact I was too slow ;-) ), I sent a mail from
external MTA mail.sys4.de and this mail did not run through any
of the milters. I
> Am 03.04.2017 um 15:43 schrieb Wietse Venema :
>
> Wietse Venema:
>>> After I ran this (in fact I was too slow ;-) ), I sent a mail from
>>> external MTA mail.sys4.de and this mail did not run through any
>>> of the milters. It is much more worse than I thought, because each
>>> mail after that
Wietse Venema:
> > After I ran this (in fact I was too slow ;-) ), I sent a mail from
> > external MTA mail.sys4.de and this mail did not run through any
> > of the milters. It is much more worse than I thought, because each
> > mail after that "mail loop" above was not scanned by any milters
> > a
> After I ran this (in fact I was too slow ;-) ), I sent a mail from
> external MTA mail.sys4.de and this mail did not run through any
> of the milters. It is much more worse than I thought, because each
> mail after that "mail loop" above was not scanned by any milters
> anymore! I also stopped po
Hi,
> Am 31.03.2017 um 10:48 schrieb Christian Rößner
> :
>
> Hi,
>
>> Am 30.03.2017 um 17:25 schrieb Viktor Dukhovni :
>>
>>
>>> On Mar 30, 2017, at 11:15 AM, Christian Rößner
>>> wrote:
>>>
>>> It is a VM, but the host uses ECC-RAM. No errors were reported to the
>>> kernel message bu
Hi,
> Am 30.03.2017 um 17:25 schrieb Viktor Dukhovni :
>
>
>> On Mar 30, 2017, at 11:15 AM, Christian Rößner
>> wrote:
>>
>> It is a VM, but the host uses ECC-RAM. No errors were reported to the kernel
>> message buffer.
>
> Is it possible that some log messages were lost when the log
> so
> On Mar 30, 2017, at 11:15 AM, Christian Rößner
> wrote:
>
> It is a VM, but the host uses ECC-RAM. No errors were reported to the kernel
> message buffer.
Is it possible that some log messages were lost when the log
socket got re-created as part of log-rotation?
Do your milters always add
> Am 30.03.2017 um 16:00 schrieb Wietse Venema :
>
> Nothing was changed, but something stopped working. Do you have ECC
> memory enabled?
It is a VM, but the host uses ECC-RAM. No errors were reported to the kernel
message buffer.
Christian
--
Erlenwiese 14, 36304 Alsfeld
T: +49 6631 7882340
Nothing was changed, but something stopped working. Do you have ECC
memory enabled?
Wietse
Hi,
this morning I found a spam mail in my inbox, which normally should have been
triggered by my spam milter. As I checked the headers, I found out that the
milter service did not add any headers.
I checked the logs for the QID and found out that the milter was not even
requested. Further I s
18 matches
Mail list logo