Hi Bill,

 Thanks for your reply.  I can do all you those things, but in my
case, the domains and valid addresses are pretty much static, so I
would not mind updating two machines when I add or remove a new
address.. but adding a RO share to ~vpopmail/domains  is also trivial
to solve that problem.

 I guess my question is how do I configure the front end machine to
pass off via SMTP the filtered valid email messages to another SMTP
server?

And as an option, how would I add a X-header line to the header to
record/track the pass-through?

-Hank



On 12/13/05, Bill Shupp <[EMAIL PROTECTED]> wrote:
> Hank wrote:
> > I have a spare server which I'd like to use as a pass-through, first
> > stage filter in order to reject any email addressed to an non-existent
> > email address in several domains. Only valid email would then be
> > forwarded via SMTP to a third party service for spam and virus
> > filtering (also via an SMTP pass-through), and then finally to my
> > production email server for final delivery via the toaster.
> >
> > The second and third steps are already in-place and working well, but
> > the third party spam/virus filter is getting 10s of thousands of email
> > messages to non-existent email address on my domains, which the
> > third-party filter is trapping, but they're not rejecting them, and
> > I'm being charged for thousands of overage messages sent to their
> > quarantine.  So I'd like to front end it with something to reject
> > invalid addresses, and then pass on to them for through spam/virus
> > filtering removal (which they do very well).
> >
> > How or what can I modify/add to the toaster to accomplish this?
>
> I really should add notes about this in the toaster, it comes up so often.
>
> The toaster patch includes chkuser, code that checks for existing users
> if catchall is set to "bounce-no-mailbox".  But to accomplish this, the
> server running chkuser must have access to not only the auth back end
> (files for cdb, mysql db for mysql, etc), but also the file system that
> ~vpopmail/domains is on.  This is to check for file bases aliases,
> mailing lists, mail "robots", or anything that vpopmail doesn't know
> about in its database.
>
> In your case, the most direct solution is to create a read-only file
> share for ~vpopmail/domains that the chkuser machine mounts to check
> these files.  Also, you'll need to either share or sync periodically the
> /var/qmail/users directory, as well as rcpthosts, morercpthosts*, and
> virtualdomains in /var/qmail/control.
>
> See http://shupp.org/maps/ispcluster.html for info on a fairly more
> involved setup as well.
>
> Regards,
>
> Bill
>

Reply via email to