On 5/10/22 16:47, Wietse Venema wrote:
With this setting, mail will be ACCEPTED when the recipient
address:
Sorry, that is incorrect.
Postfix features of the form "reject_" cannot promise
that a recipient (or sender, client, helo) will be accepted when
their predicate is false.
They can't
> With this setting, mail will be ACCEPTED when the recipient
> address:
Sorry, that is incorrect.
Postfix features of the form "reject_" cannot promise
that a recipient (or sender, client, helo) will be accepted when
their predicate is false.
They can't promise that, because there may be a
On 5/7/22 13:18, Wietse Venema wrote:
James Feeney:
At http://www.postfix.org/postconf.5.html :
smtpd_reject_unlisted_recipient (default: yes)
Request that the Postfix SMTP server rejects mail for unknown
recipient addresses, even when no explicit reject_unlisted_recipient
access
On Tue, May 10, 2022 at 09:03:59AM +0200, lutz.niede...@gmx.net wrote:
> userA and userB are real local users with a mailbox. What happens in
> case of an aliases line like this:
>
> userA: userA, userB
>
> Does it deliver to local users userA and userB? I assume that it does not
> loop.
Hi,
userA and userB are real local users with a mailbox. What happens in case of an
aliases line like this:
userA: userA, userB
Does it deliver to local users userA and userB? I assume that it does not loop.
Thanks & cheers!
-lutzn
On 09/05/2022 12:48, Matt Kinni wrote:
I have opendkim configured via 'smtpd_milters' to sign all outbound
mail, and my domain publishes a "quarantine" dmarc record to enforce
the consequences of this.
I recently discovered that MAILER-DAEMON messages generated by
postfix itself bypass this
On Mon, May 09, 2022 at 03:03:42PM -0400, Wietse Venema wrote:
> > - I don't quickly have an example of bad things that can happen
> > with Milter inspection of Postfix-generated mail. That doesn't mean
> > that such bad things don't exist.
>
> So, with that caveat you can turn on DKIMM signing
