Hello
On Thu, Feb 23, 2012, at 04:36 PM, Noel Jones wrote:
> > cat /etc/postfix/spamtrap_userparts
> > test1
> > test2
> > test3
> > postmap /etc/postfix/spamtrap_userparts
> Wrong format; table entries must have a result. In this specific
> case, postfix doesn't actually use the result, but *something* must
> be there.
Gotcha.
> And I'm pretty sure you need full addresses, not just usernames.
>
> # these are all considered valid users
> te...@example.tld valid_user
> te...@example.tld Anything
> te...@example.tld melt_CPU
Noted.
In this check I've only been using SQL stored function calls in the
queries (query = SELECT func('arg');), where the query results are just
"1" or "null",
postmap -q valid_domain_part
proxy:mysql:/etc/postfix/sql/vdomains.cf
1
postmap -q invalid_domain_part
proxy:mysql:/etc/postfix/sql/vdomains.cf
null
postmap -q valid_user_part
proxy:mysql:/etc/postfix/sql/vmailboxes.cf
1
postmap -q invalid_user_part
proxy:mysql:/etc/postfix/sql/vmailboxes.cf
null
and it's been working great. Didn't realize that there was a
full_address requirement for the hash: table check. Thanks for pointing
out the possibility -- I'll keep an eye on it.
> > + virtual_mailbox_maps = hash:/etc/postfix/spamtrap_userparts
> > + proxy:mysql:/etc/postfix/sql/vmailboxes.cf
> Yes, that should work fine without any ill effects.
> > should now actually receive, and hopefully trigger upon, the
> > spamtrap-containing message?
> Yes.
Then, I've homework to do. Thanks again.
Cheers,
Roger
