The simplest way to deal with this is to change your catchall
configuration. In qmailadmin (web app), user accounts, click either the
"set catchall deleted" or "set catchall bounce" link. That controls what
happens to email for which there's no user account.
Deleting misaddressed email is not friendly to the sender (and I think
goes against standards), but it eliminates backscatter (along with
legitimate bounces). It also gives spammers no information they can use
to clean up their lists. I think this is not a good thing, but some
people disagree.
Bouncing misaddressed email contributes to backscatter, but gives
spammers feedback on bogus addresses (provided the return address is
legitimate).
Personally, I use the postmaster account for catchall (the default). I
get practically no spam there (thanks to spamdyke), and I can forward
misaddressed email to their intended account, while adding an forward
for the misaddressed message (for the next time). This is only practical
for SMB and personal servers, not so much for ISPs.
In addition to spamdyke, you can use the badmailto filter to reject some
invalid accounts, while still using the catchall account. See
http://wiki.qmailtoaster.com/index.php/Account_verification_using_badmailto
HTH.
--
-Eric 'shubes'
On 11/19/2010 04:48 PM, Tony White wrote:
Hi Eric,
What is happening is the mail server is seeing addresses for
one or more of my domains that are not real and accepting
delivery of them.
My thought was to deny all then only accept valid addresses.
Also seeing From Address ie @rolex.com and this is in the
blacklist but not being stopped! CHKUSER is accepting delivery
On 20/11/2010 4:06 AM, Eric Shubert wrote:
On 11/19/2010 08:51 AM, Tony White wrote:
Hi folks,
Thank you for making me use spamdyke it certainly does
make a huge difference.
I have tried to use the blacklists but they do not appear to
work.
I have blocked an entire domain in blacklist_recipients
and whitelisted those to accept in that domain in whitelist_recipients.
I have restarted qmail but still they get through!
Does chkuser cause this?
I don't believe chkuser has any impact with this.
You don't need to restart qmail when modifying spamdyke configuration
files. They're picked up on the fly. Nice. (Overhead is negligible, as
they're probably all cached by the kernel)
As to your problem, what are you trying to accomplish? If you're
trying to block spam with forged from addresses, you want to simply
add your domain to the blacklist_senders file:
@mydomain.com
That is all you need to do. No whitelisting is necessary because
authenticated sessions bypass all filters, and your users all
authenticate when sending.
I'm not sure what you're trying to accomplish with the recipients
filters. Please explain what you're trying to accomplish with this.
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
