On 2021-01-17 18:08, Tom Sommer wrote:
On 2021-01-17 17:29, Wietse Venema wrote:
On 2021-01-17 14:22, Wietse Venema wrote:
>> I just observed Postfix not picking up changes in the SASL auth
>> backend,
>> is there some kind of cache involved here?
>
> There is no suc
On 2021-01-17 17:29, Wietse Venema wrote:
On 2021-01-17 14:22, Wietse Venema wrote:
>> I just observed Postfix not picking up changes in the SASL auth
>> backend,
>> is there some kind of cache involved here?
>
> There is no such thing in Postfix. Also not in the Postfix Dovcecot
> client.
Curi
On 2021-01-17 14:22, Wietse Venema wrote:
Tom Sommer:
Hi all
I just observed Postfix not picking up changes in the SASL auth
backend,
is there some kind of cache involved here?
There is no such thing in Postfix. Also not in the Postfix Dovcecot
client.
Curious, and it couldn'
Hi all
I just observed Postfix not picking up changes in the SASL auth backend,
is there some kind of cache involved here? I had to restart postfix in
order for it to see that a (spamming) SASL account no-longer existed,
even though the Dovecot auth-backend was aware of this.
Thanks.
--
Tom
On 2020-08-22 22:35, Wietse Venema wrote:
Wietse Venema:
Greg Sims:
> sender_dependent_default_transport_maps = randmap:{r235,r236,r237,r238}
>
> selects transports at random for delivering email. Is it possible to
> schedule a set of transports using a round-robin discipline? This
man 5 tc
On 2020-09-01 00:28, @lbutlr wrote:
On 31 Aug 2020, at 10:08, Greg Sims wrote:
(1) continue to ignore the MaxConnection Messages/Deferrals
(2) reduce the number of processes per transport to 1
(3) reduce the number of outlook transports to 2
4) add a footer to mails going to outlook a
On 2020-10-07 16:28, Dominic Raferd wrote:
On Wed, 7 Oct 2020 at 14:04, Vieri Di Paola
wrote:
On Wed, Oct 7, 2020 at 2:34 PM Tom Sommer wrote:
>
> So SASL user "t...@example.com" would be able to send only from
> "@example.com".
This would force sasl-authe
On 2020-10-07 15:03, Vieri Di Paola wrote:
On Wed, Oct 7, 2020 at 2:34 PM Tom Sommer wrote:
So SASL user "t...@example.com" would be able to send only from
"@example.com".
smtpd_sender_login_maps = pcre:/etc/postfix/login_maps.pcre
content of /etc/postfix/login_ma
I'm trying to get smtpd_sender_login_maps to allow any sasl-auth'd user
to only send from the domain they are logged in as.
So SASL user "t...@example.com" would be able to send only from
"@example.com".
So far I have no luck turning the lookup table into this, is it even
possible?
Thanks
Hi
I'm running into problems with OpenDKIM and a 1024 libmilter connection
limit (or port-reservation limit) during peak hours.
Is there any way to limit/throttle the number of connections made to a
milter?
--
Tom
On 2019-02-26 15:51, Wietse Venema wrote:
Tom Sommer:
I have a feature request for a lookup table like randmap(), but with
the
option to control a percentage or a count of mails sent to the
transport.
Even if the percentage was just a "chance" of selection, it would be
nice.
So yo
I have a feature request for a lookup table like randmap(), but with the
option to control a percentage or a count of mails sent to the
transport.
Even if the percentage was just a "chance" of selection, it would be
nice.
So you could do :
sender_dependent_default_transport_maps = randmap:{
On 2018-09-08 01:21, Wietse Venema wrote:
Either way, the smtpd_reject_footer feature may be of some help.
http://www.postfix.org/postconf.5.html#smtpd_reject_footer
The text is wrong in the docs:
"Lookup tables, indexed by the complete Postfix SMTP server 4xx or 5xx
response, with reject fo
> On 14 Aug 2018, at 16.57, Viktor Dukhovni wrote:
>
>
>
>> On Aug 14, 2018, at 10:50 AM, Tom Sommer wrote:
>>
>> The message-id is not contained within <> in the log message but maybe that
>> is correct, it just breaks logstash parsing but pe
The message-id is not contained within <> in the log message but maybe that is
correct, it just breaks logstash parsing but perhaps the parser is to blame.
--
Tom Sommer
> On 14 Aug 2018, at 16.34, Dominic Raferd wrote:
>
>
>
>> On Tue, 14 Aug 2018 at 15:22, Tom Som
I noticed a mail that broke logging syntax:
Aug 14 15:29:57 X postfix/cleanup[11962]: 41qYP05TZCz5xY9:
message-id==?utf-8?Q?=3CE1F7DC2C-82B5-4927-B0DB-0179227E665C=40aalborgf?=?
=?utf-8?Q?=C3=B8rstehj=C3=A6lp=2Edk=3E?=
I guess the message-id contains non-ascii chars that break logging, or
so
On 2018-08-09 19:52, Wietse Venema wrote:
Tom Sommer:
On 2018-08-09 19:31, Wietse Venema wrote:
> I suggested using a lookup table (smtpd_reply_footer_maps) which
> is queried with the original Postfix response, and which can
> dynamically return a filled-in template based on the conte
On 2018-08-09 19:31, Wietse Venema wrote:
Viktor Dukhovni:
On Thu, Aug 09, 2018 at 06:52:48PM +0200, Tom Sommer wrote:
> So I can do a "Please look at
> http://example.com/smtp.php?code=$smtp_code"; and do some magic on that
> page with the error code and/or error desc
On 2018-08-09 19:07, Viktor Dukhovni wrote:
On Thu, Aug 09, 2018 at 06:52:48PM +0200, Tom Sommer wrote:
So I can do a "Please look at
http://example.com/smtp.php?code=$smtp_code"; and do some magic on that
page with the error code and/or error description to help the
customer.
On 2018-08-09 18:17, Wietse Venema wrote:
Tom Sommer:
On 2018-08-09 14:57, Wietse Venema wrote:
> Tom Sommer:
>> I still fail to see how to inject the $smtp_code for the stream into
>> the
>> string at a precise position, but I gather it's possible somehow so I
>
On 2018-08-09 18:24, Viktor Dukhovni wrote:
On Thu, Aug 09, 2018 at 11:07:33AM +0200, Tom Sommer wrote:
It would be nice if smtpd_reject_footer could include variables such
as
the 4.x.x/5.x.x response code or even the full postfix error message,
this way one could make more helpful errors
On 2018-08-09 14:57, Wietse Venema wrote:
Tom Sommer:
I still fail to see how to inject the $smtp_code for the stream into
the
string at a precise position, but I gather it's possible somehow so I
will keep digging.
One more time:
YOU don't insert status codes into the foote
On 2018-08-09 14:10, Wietse Venema wrote:
Tom Sommer:
On 2018-08-09 14:01, Wietse Venema wrote:
> Tom Sommer:
>> It would be nice if smtpd_reject_footer could include variables such
>> as
>> the 4.x.x/5.x.x response code or even the full postfix error message,
>> t
On 2018-08-09 14:01, Wietse Venema wrote:
Tom Sommer:
It would be nice if smtpd_reject_footer could include variables such
as
the 4.x.x/5.x.x response code or even the full postfix error message,
this way one could make more helpful errors messages with more helpful
links.
Better
It would be nice if smtpd_reject_footer could include variables such as
the 4.x.x/5.x.x response code or even the full postfix error message,
this way one could make more helpful errors messages with more helpful
links.
Thanks
--
Tom
25 matches
Mail list logo
