On 17.04.23 13:38, Tyler Montney via Postfix-users wrote:
Before getting started, this has been publicly disclosed by someone else a
while ago. However, I still don't think it's necessary to name the
organization to explain myself. My goal here is not only to give a proper
argument to the provide
Hi
I have question about *_error_limit and postfix
I have separated services like
smtp incomming and smtp outgoing and webmail
I have roudcube which is used by several thousand users
On smtp outgoing in main.cf:
...
smtpd_client_connection_count_limit = 900
smtpd_hard_error_limit = 5
smtpd_soft
Demi Marie Obenour via Postfix-users:
> > While Postfix can to some extent enforce envelope to sender mismatches,
> > the real concern is usually the "From:" header, ... whose content is not
> > the MSAs job to enforce.
>
> A milter must be used for this. Since this, along with DMARC, is a
> core
Hello,
or customer tried to recall send message (outlook/exchange feature) and the
recipient started bombing server and original sender with mails
"message recall failed" (outlook/microsoft failure).
I was able to drop the messages using header_checks but I'm curious if
anyone knows better wa
natan via Postfix-users:
> Hi
> I have question about *_error_limit and postfix
>
> I have separated services like
> smtp incomming and smtp outgoing and webmail
>
> I have roudcube which is used by several thousand users
>
> On smtp outgoing in main.cf:
> ...
> smtpd_client_connection_count_lim
[An on-line version of this announcement will be available at
https://www.postfix.org/announcements/postfix-3.7.5.html]
This will be the last update for Postfix version 3.4.
Fixed with Postfix 3.7.5, 3.6.9, 3.5.19:
* Bugfix (problem introduced in Postfix 3.5): check_ccert_access
did not ha
Hello.
Unlike promised there had to be another release, and i still hope
it is ok to forward the announcement here.
(Bicycle-Day has passed in the meantime, however.)
This fixes some bugs, even non-developers can now see --verbose
logging, for example. Out of interest i implemented sandboxing,
s
Hello.
On 3.8.0 services managed via spawn(8) now produce
Apr 19 01:03:04 postfix/spawn[8485]: warning: /usr/libexec/s-postgray:
process id 8486: command time limit exceeded
Apr 19 14:43:56 postfix/spawn[19651]: warning: /usr/libexec/s-postgray:
process id 19755: command time limit exceeded
ARC-Authentication-Results: i=1; list.sys4.de; dkim=fail;
arc=none (Message is not ARC signed);
dmarc=none
Authentication-Results: list.sys4.de; dkim=fail;
arc=none (Message is not ARC signed); dmarc=none
when originating mails is not dkim signed then i belive dkim=fail here
should be repor
Steffen Nurpmeso via Postfix-users:
> Hello.
>
> On 3.8.0 services managed via spawn(8) now produce
>
> Apr 19 01:03:04 postfix/spawn[8485]: warning: /usr/libexec/s-postgray:
> process id 8486: command time limit exceeded
> Apr 19 14:43:56 postfix/spawn[19651]: warning: /usr/libexec/s-postgr
10 matches
Mail list logo
