On Sat, 20 Mar 2021, Dominic Raferd wrote:
You may find my script helpful:
https://www.timedicer.co.uk/programs/help/relay-enforcer.sh.php
Looks very interesting, thanks. I ran 'shellcheck' on it and saw many
scary warnings; highly recommended to revise the code to fix all of them.
Rahul
On Fri, 19 Mar 2021, Wietse Venema wrote:
See examples in:
http://www.postfix.org/postconf.5.html#default_delivery_status_filter
(this was originally designed to turn soft TLS errors into hard ones).
Thanks, that is a vey nice feature I did not know about.
I should mention that my strategy of
A fix that I recently applied for a backscatter problem.
Gmail is the example used below, but the problem and solution are not
Gmail-specific.
The problem: Spam arrives for a user, gets past spam filter, is forwarded
by receiving user to their Gmail address, gets a permanent rejection from
G
Thanks for all the suggestions, esp. Wietse, Viktor, Benny, Matus. I'll
investigate reject_unverified_recipient, and report back soon with what
solution(s) I found. May be a week or two (or more).
Rahul
On Fri, 5 Feb 2021, Wietse Venema wrote:
Postfix is a pipeline of processes; some processes transform addresses
before a message is queued (canonical_maps, virtual_alias_maps),
and some transform addresses in the delivery agent (alias_maps,
$HOME/.forward files). It is not practical for an SMTP
I would like to write an smtpd policy server[1] that will cause incoming
mail to be rejected during smtp if a local recipient (a Linux user in my
case) is exceeding his filesystem storage quota.
Postfix supplies the envelope recipient but not the local recipient to the
smtpd policy server.
I