On Mon, Jul 31, 2017 at 09:16:46AM +0200, Tomas Macek wrote:
> Hello, our system is sometimes under attack of spammers using
> "NOTIFY=SUCCESS" param in "rcpt to: " header. And because of a random From
> address, the DSN message obviously goes to an nonexistent server or user.
>
> I've read the "
Matus UHLAR - fantomas:
If filter was able to strip NOTIFY=, we'd have fine control over when to
send notifications...
On 31.07.17 07:14, Wietse Venema wrote:
There is an example that modifies DSN commands in
http://www.postfix.org/postconf.5.html#smtpd_command_filter
That means we could use
On Mon, 31 Jul 2017, Matus UHLAR - fantomas wrote:
On 31.07.17 09:16, Tomas Macek wrote:
Hello, our system is sometimes under attack of spammers using
"NOTIFY=SUCCESS" param in "rcpt to: " header. And because of a random
From address, the DSN message obviously goes to an nonexistent server
Matus UHLAR - fantomas:
> If filter was able to strip NOTIFY=, we'd have fine control over when to
> send notifications...
There is an example that modifies DSN commands in
http://www.postfix.org/postconf.5.html#smtpd_command_filter
Wietse
Tomas Macek:
> Hello, our system is sometimes under attack of spammers using
> "NOTIFY=SUCCESS" param in "rcpt to: " header. And because of a random From
> address, the DSN message obviously goes to an nonexistent server
> or user.
>
> I've read the "Restricting the scope of "success" notificat
On 31.07.17 09:16, Tomas Macek wrote:
Hello, our system is sometimes under attack of spammers using
"NOTIFY=SUCCESS" param in "rcpt to: " header. And because of a random
From address, the DSN message obviously goes to an nonexistent server
or user.
I've read the "Restricting the scope of "suc
