We're moving to a configuration that will leverage the check_sasl_access option
to allow only those granted access to authenticate from outside the local
network and relay mail.
This are mostly working (at least amongst the list of users allowed to
send--we'll evaluate the types of things we're
On Thu, Dec 12, 2019 at 12:10:07AM +, Jason R Cowart wrote:
> We're moving to a configuration that will leverage the check_sasl_access
> option to allow only those granted access to authenticate from outside the
> local network and relay mail.
Your submission users should be using port 587, n
Seriously is there ever a case not to use port 587?
I have a spammer who uses all sorts of "from" addresses but the same
"reply" address. Any way to block this spammer in Postfix.
If you have integrated with Apache SpamAssassin, then v3.4.3 introduces
the ability to do RBL lookups on the domain in Reply-to as well as the
ability to do hashed lookups.
Regards,
KAM
On 12/11/2019 9:38 PM, li...@lazygranch.com wrote:
> I have a spammer who uses all sorts of "from" addresses bu
* li...@lazygranch.com:
> I have a spammer who uses all sorts of "from" addresses but the same
> "reply" address. Any way to block this spammer in Postfix.
You can use Postfix header checks. The following example is PCRE based:
/^Reply-To:.+\bexample\.com\b/i REJECT
-Ralph
> On Dec 11, 2019, at 9:38 PM, li...@lazygranch.com wrote:
>
> I have a spammer who uses all sorts of "from" addresses but the same
> "reply" address. Any way to block this spammer in Postfix.
main.cf:
pcre = pcre:${config_directory}/
header_checks = ${pcre}header-checks.pcre
Thanks. Not the smartest spammer. The "from" lasts a while but the "reply" is
static for months. I just got tired of blocking the "from" periodically.
Original Message
From: postfix-us...@dukhovni.org
Sent: December 11, 2019 6:57 PM
To: postfix-users@postfix.org
Reply-to: postfix-users
li...@lazygranch.com skrev den 2019-12-12 03:38:
I have a spammer who uses all sorts of "from" addresses but the same
"reply" address. Any way to block this spammer in Postfix.
milter-regex
or make a clamav-signaturee
Kevin A. McGrail skrev den 2019-12-12 03:45:
If you have integrated with Apache SpamAssassin, then v3.4.3 introduces
the ability to do RBL lookups on the domain in Reply-to as well as the
ability to do hashed lookups.
and spamassassin 3.4.3 is out before xmax :=)
is TxRep working with non defa
Jason R Cowart skrev den 2019-12-12 01:10:
smtpd_recipient_restrictions =
check_client_access
cidr:/etc/postfix/access/restricted-local-only.cidr,
check_recipient_access hash:/etc/postfix/access/recipient,
Any thoughts? Thanks in advance.
make check_resipient_access reused in ch
lists skrev den 2019-12-12 03:08:
Seriously is there ever a case not to use port 587?
depends on content filtering, if all clients is local all can use port
25
lists skrev den 2019-12-12 03:08:
Seriously is there ever a case not to use port 587?
On 12.12.19 08:29, Benny Pedersen wrote:
depends on content filtering, if all clients is local all can use port
25
even in this case separation of submission port can help much.
I prefer postscreen and milt
13 matches
Mail list logo
