You should take into consideration parallel deliveries with attachments.
Due to those cases I'm not in favor of pre-queue filtering. I see it as a
risk.
Instead of notifying the sender in case of non-delivery, the recipient (and
the admin) can receive notifications. Amavis can generate them for
> Wietse:
>> There is no difference for the remote SMTP client whether you use
>> spampd in "pre-accept" mode, or amavisd-new in "pre-accept" mode.
>> Both appraches have the same problem: when it takes too much time
>> to inspect a message, the remote SMTP client will time out.
> listserv.traf.
Wietse:
> There is no difference for the remote SMTP client whether you use
> spampd in "pre-accept" mode, or amavisd-new in "pre-accept" mode.
>
> Both appraches have the same problem: when it takes too much time
> to inspect a message, the remote SMTP client will time out.
listserv.traf...@sloop
Hello Wietse,
Friday, May 8, 2015, 10:26:11 AM, you wrote:
> listserv.traf...@sloop.net:
> [switching from before-queue spampd]
>> I've seen suggestions for using amavis as a pre-accept filter, and
>> turning off the AV scanning. [But this defeats some substantial
>> purpose of running amavis in
listserv.traf...@sloop.net:
[switching from before-queue spampd]
> I've seen suggestions for using amavis as a pre-accept filter, and
> turning off the AV scanning. [But this defeats some substantial
> purpose of running amavis in the first place.]
There is no difference for the remote SMTP client
I've done a few searches and don't really turn up anything - so my apologies if
this is an "old" already answered question. [If you could point me in the right
direction for the discussion somewhere that would be nice...]
So, here's what I want, and I'm not sure how best to go about it.
Platfor
Kristjan Nii skrev den 2015-05-08 15:04:
Can anyone please help with a solution?
https://dnsrpz.info/
then list ru as a rpz tld, problem solved, it works both in incomming
and outgoing, with domain not found in mta responses, if you want only
on outgoing, then remove reject_unknown_domain*
Update: so I kept on digging and found a hind here
http://postfix.1071664.n5.nabble.com/Reject-Discard-outbound-domain-td46854.html
"
I think the easiest way to ban a domain is to add it to the
transport_maps with an entry something like
bad.example.com error:invalid domain
-- Noel Jones
"
I
On 5/8/2015 3:33 AM, Tobi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 07.05.2015 um 18:43 schrieb Rod K:
I'm trying to implement
check_client_restrictions = check_client_access
pgsql:/path/to/local_blacklist-sql.cf, ...
have you had a look at postfix postscreen featue?
http://w
Hi,
I googled this question, but was not able to find a definitive answer or
solution. I am using Postfix 2.9 and I'd like to block or redirect (to our
original sender or at least /dev/null) outbound emails destined to fake
domains (user typos) like gmail.ru or/and potentially stop sending to
*@*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am 07.05.2015 um 18:43 schrieb Rod K:
> I'm trying to implement
>
> check_client_restrictions = check_client_access
> pgsql:/path/to/local_blacklist-sql.cf, ...
>
have you had a look at postfix postscreen featue?
http://www.postfix.org/POSTSCREEN_R
11 matches
Mail list logo
