At 16.36 14/09/2005, you wrote:
On Wed, 2005-09-14 at 08:25 -0700, Tom Collins wrote:
> On Sep 14, 2005, at 8:04 AM, Jeff Koch wrote:
> > I think what I am really asking is what is the mechanism for the way
> > 'catch-all delete' works versus 'catch-all bounce' so I can determine
> > which will have a lower load on the server.
>
> Since you're using chkusr, I don't think there's a difference. The
> chkusr patch will reject messages to unknown recipients at the SMTP
> level whenever the catchall is set to delete or bounce. Since messages
> for non-existent users won't be getting through, the delete/bounce
> option will never be used.
Which is related to my original reply. Only thing im not sure about is
how the latest version of chkuser interacts with vpopmail with all the
new features Tonix has added in.
Deleting messages for wrong recipients is up to you, depending on
your business needs and preferences.
Obviously, stopping messages at smtp level help saving bandwidth and
CPU (as those messages will no be processed bu additional SA, clamav,
etc.), at the potential (maniacal) risk that someone could know which
are your real users.
I only ask what happens to honest senders, if none is going to notify
them about wrong deliveries.
About chkuser, it has some small solutions inside, that not solve the
problem, just help to limit some attacks.
I've set up my system to refuse messages with more than 50 total
recipients and more that 3 wrong recipients, with tarpitting delays
(1 second growing for each error) on each error. That help me, though
I see much more could be done. Logs say stupid massive senders are
stopped, while smart are delayed a lot.
Tonino
Shane
