Matus UHLAR - fantomas wrote on Thu, 8 Nov 2018 12:12:49 +0100:
> the problem lies in "parent_domain_matches_subdomains" which is (and should
> be) empty in postfix and apparently even is in new postfix version.
As I wrote earlier, it *is* set implicitely by backwards-compatibilty.
> First I
On 08.11.18 01:31, Kai Schaetzl wrote:
Thanks for the answer. But, please look again.
/etc/mail/access:
createsend.com REJECT
cmail20.com REJECT
On 08.11.18 12:06, Matus UHLAR - fantomas wrote:
you should specify .createsend.com, because the connecting domain is
Noel Jones wrote on Wed, 7 Nov 2018 13:30:08 -0600:
With the above list, check_sender_access comes first. Postfix does
not reorder the list you have specified.
On 08.11.18 01:31, Kai Schaetzl wrote:
Thanks for the answer. But, please look again.
/etc/mail/access:
createsend.com REJECT
Noel Jones wrote on Wed, 7 Nov 2018 13:30:08 -0600:
> With the above list, check_sender_access comes first. Postfix does
> not reorder the list you have specified.
Thanks for the answer. But, please look again.
/etc/mail/access:
createsend.com REJECT
cmail20.com REJECT
The order is:
> >
On 11/7/2018 12:40 PM, Kai Schaetzl wrote:
> Wietse Venema wrote on Wed, 7 Nov 2018 12:10:40 -0500 (EST):
>
>> HOWEVER, by default Postfix evaluates all of these at RCPT TO time.
>
> which means smtpd_delay_reject = yes is the default?
Yes, that's the default, and generally should not be
Wietse Venema wrote on Wed, 7 Nov 2018 12:10:40 -0500 (EST):
> HOWEVER, by default Postfix evaluates all of these at RCPT TO time.
which means smtpd_delay_reject = yes is the default?
Am I correct in assuming that with "yes" it doesn't matter if I list the
client restrictions in
Kai Schaetzl:
[ Charset ISO-8859-1 converted... ]
> Addendum.
>
> Currently, I get client rejections with the setup shown in my last mail
> (despite the delay). I don't know if it hits *always*, though. I can't
> check if it didn't hit for some client where the name matches, there are
> too
Addendum.
Currently, I get client rejections with the setup shown in my last mail
(despite the delay). I don't know if it hits *always*, though. I can't
check if it didn't hit for some client where the name matches, there are
too many entries.
I expected it to carry out the helo checks before
Carsten Rosenberg wrote on Wed, 7 Nov 2018 16:23:54 +0100:
> So if you reject somebody with an access_map, you won't see any scan
> result in rspamd.
This would be fine ;-)
> Do you have any problems with this situation?
Yes, it's the other way around here. e.g. there is no rejection happening
Kai,
both are running simultaneously. So at smtpd_recipient_restriction stat
the milter will also get the recipients. As far as I have seen the
postfix restriction react faster.
So if you reject somebody with an access_map, you won't see any scan
result in rspamd. Only the milter connect,
10 matches
Mail list logo
