Florian Pritz:
> What do you think about adding a simpler pickup_restrictions option and
> extending the SMTP policy protocol a bit by adding a userid field which
> in case of pickup (I believe only maildrop/sendmail/postdrop go into
> pickup) contains the id of the sending user?
>
> pickup_restrictions could work similar to smtpd_*_restrictions, except
> rejecting a mail should probably create a bounce to the sender since we
> can't reject anything at this stage, but what I'd really want is putting
> stuff on hold.
>
> As for the restrictions supported by pickup_restrictions, I think most
> smtp restrictions (maybe no rbl or helo checks) could be adapted.
>
> Does that sound like an idea worth implementing?
>
> PS: I don't see restrictions support for QMQP in the manpage so might
> make sense to add it there too.
Why don't YOU try it, and then report how well the idea works. I
suggest that you also consider the implications of a malicious
application sending mail with forged sender addresses, and Postfix
then bouncing that mail to innocent people.
But is seems to be that the problem is better solved at the source:
fix those damned broken web applications.
Wietse
