Re: Postscreen concurrency limits

2018-12-13 Thread Viktor Dukhovni
> On Dec 13, 2018, at 8:25 PM, Alex wrote: > > We had a Mimecast user report today that their mail was being rejected > with a 4.7.0 "too many connections" error. This is a "soft" error, in > that the mail client will later attempt to resend, correct? Should be. > Isn't the default of 50

Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))

2018-12-13 Thread Paul Schmehl
I'm seeing this error in the logs: warn: Unescaped left brace in regex is deprecated here (and will be fata)) It comes right after this: status=sent (delivered via filter service The filter service uses filter.sh (stolen from the docs) and spamassassin. Is it safe to assume this is a code

Re: Problem with filter

2018-12-13 Thread Paul Schmehl
--On December 13, 2018 at 9:00:06 PM +0100 Benny Pedersen wrote: Paul Schmehl skrev den 2018-12-13 20:45: The user does not exist until "ls -l" is able to correctly identify the files as belonging to the user. Hmmm...thank you, Victor. I'll try to sort that out. if its more simple,

Postscreen concurrency limits

2018-12-13 Thread Alex
Hi, We had a Mimecast user report today that their mail was being rejected with a 4.7.0 "too many connections" error. This is a "soft" error, in that the mail client will later attempt to resend, correct? Isn't the default of 50 concurrent connections sufficient for most environments? Is there

Re: Problem with filter

2018-12-13 Thread Benny Pedersen
Paul Schmehl skrev den 2018-12-13 20:45: The user does not exist until "ls -l" is able to correctly identify the files as belonging to the user. Hmmm...thank you, Victor. I'll try to sort that out. if its more simple, change to use spampd so spamassassin is smtp content filter seen from

Re: Problem with filter

2018-12-13 Thread Paul Schmehl
--On December 13, 2018 at 2:36:44 PM -0500 Viktor Dukhovni wrote: On Dec 13, 2018, at 2:33 PM, Paul Schmehl wrote: # ls -lsa /home/filter/.spamassassin/ total 25056 2 drwx-- 2 1004 filter 512 Dec 10 21:45 . why is 1004 when it should be ascii usernamme ? what user is 1004

Re: Problem with filter

2018-12-13 Thread Viktor Dukhovni
> On Dec 13, 2018, at 2:33 PM, Paul Schmehl wrote: > >>> # ls -lsa /home/filter/.spamassassin/ >>> total 25056 >>> 2 drwx-- 2 1004 filter 512 Dec 10 21:45 . >> >> why is 1004 when it should be ascii usernamme ? >> >> what user is 1004 ?, its imho not known in your system >> >>

Re: ignore SASL/Auth to specific server (internal exchange relay)

2018-12-13 Thread Andrey Repin
Greetings, Jan Ceuleers! > On 12/12/2018 20:55, Viktor Dukhovni wrote: >> >>> On Dec 12, 2018, at 2:48 PM, Daniel Miller wrote: >>> >>> Not wanting to get in the way of the experts but this may help: >> Indeed a nice succinct and accessible answer for non-experts. Please >> don't hesitate to

Re: Problem with filter

2018-12-13 Thread Paul Schmehl
--On December 13, 2018 at 6:54:48 PM +0100 Benny Pedersen wrote: Paul Schmehl skrev den 2018-12-13 18:36: # ls -lsa /home/filter/.spamassassin/ total 25056 2 drwx-- 2 1004 filter 512 Dec 10 21:45 . why is 1004 when it should be ascii usernamme ? what user is 1004 ?, its

Problem with filter

2018-12-13 Thread Paul Schmehl
Years ago I setup postfix using the filter script that Wietse wrote to integrate spamassassin into my mail setup. It's worked fine for a long time. smtp inet n - n - - smtpd -o content_filter=filter:dummyr On Monday, I updated the server from

Re: Old mysql patch - is this useful?

2018-12-13 Thread Wietse Venema
Andrey Repin: > Greetings, Scott Kitterman! > > > I am looking at some of the two decades of accumulated cruft in the Debian > > bug > > tracking system for the Postfix package. I came across an old bug with a > > patch that appears never to have been incorporated (no sign ups required): > >

Re: Old mysql patch - is this useful?

2018-12-13 Thread Wietse Venema
Scott Kitterman: > I am looking at some of the two decades of accumulated cruft in the Debian > bug > tracking system for the Postfix package. I came across an old bug with a > patch that appears never to have been incorporated (no sign ups required): > >

Re: Old mysql patch - is this useful?

2018-12-13 Thread Andrey Repin
Greetings, Scott Kitterman! > I am looking at some of the two decades of accumulated cruft in the Debian bug > tracking system for the Postfix package. I came across an old bug with a > patch that appears never to have been incorporated (no sign ups required): >

Re: ignore SASL/Auth to specific server (internal exchange relay)

2018-12-13 Thread Stefan Bauer
thank you for your help folks! Yes that indeed helped to understand the process! Am Mi., 12. Dez. 2018 um 20:48 Uhr schrieb Daniel Miller : > Not wanting to get in the way of the experts but this may help: > > An oversimplified view of the transport map is it tells Postfix what line > in

Old mysql patch - is this useful?

2018-12-13 Thread Scott Kitterman
I am looking at some of the two decades of accumulated cruft in the Debian bug tracking system for the Postfix package. I came across an old bug with a patch that appears never to have been incorporated (no sign ups required): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400395 I've