Can't quite seem to find where it's doing it, but I assume I'll find out for
sure when I implement it in test. Nonetheless, thought I found something,
but like always- you folks have it covered.
Thanks for everyone's support.
-Mike
From: Bill Shupp <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [toaster] smtproutes and chkuser
Date: Thu, 24 Jun 2004 09:04:50 -0700
Mike Miller wrote:
I think the chkuser patch is fantastic! Seeing how many of our servers
receive constant pummelling with 'try-everyone' SPAM, this fills the qmail
queue of bounces and the like.
A few of our clients run exchange servers on their own site, yet don't
have a connection nearly as reliable as ours. For this reason, mail is
sent to us (the MX) and our smtproutes file then forwards the mail to
their static IP.
I am looking to deploy chkuser patch on our mail systems, however need to
ensure that I don't block out the smtproutes clients. The code appears to
check rcpthosts (which these clients have their domain listed in so the
system accepts the mail), then it checks vpopmail, yet it doesn't check
smtproutes. I'm going to take a look at it this weekend to see if I can
find an easy way to add it, but maybe a more official patch is in order.
That's the only potential situation which I dont' think this script
accounts for... if a domain is in smtproutes, we just have to pass accept
all mail.
Thoughts? Am I off track here?
I run backup MX for some clients, and mail goes through just fine. I have
not examined the patch closely in a while, but it appears that if vpopmail
does not have a listing for the domain, chkuser does not fail.
Regards,
Bill
_________________________________________________________________
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines
