![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
Per Jessen wrote:
Sylvester Lykkehus wrote:
On 2009-09-27 11:11, Per Jessen wrote:
jdd wrote:
However I don't know howto setup postfix do don't anymore accept mails for this account, and mail only, leaving the account open for login.
smtpd_recipient_access + check_recipient_access
/Per
I'm pretty sure Per meant smtpd_recipient_restrictions. See http://www.postfix.org/postconf.5.html#smtpd_recipient_restrictions
Yep, you're absolutely right, that is what I meant.
/Per
You missed the part where he said he wanted to keep the account open for login. Normally access is used to specify rules for mail ACCEPTANCE, but merely having an account on the box is USUALLY sufficient. So the typical use of access.db has to be reversed in this case, to force a rejection of this specific address but (presumably) allow any other address to continue to use normal access rules. In this case, setting up an access rule to cough up a REJECT will teach the spammer to cull his database eventually. (To the extent that they care). Replying with a "421" will cause postfix to immediately disconnect which wastes even less of your bandwidth, but leaves them guessing. Using Access.db as a general way of managing all users is not a road you want to go down, for performance reasons as well as maintenance reasons. Its designed for general rules and a few specific exceptions. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org