From: "Charles Cazabon" <[EMAIL PROTECTED]>
>
> eric <[EMAIL PROTECTED]> wrote:
> >
[ snip ]
> > > > tcpserver (unless patched) requires IP ADDRESSES.
> > >
> > > No longer true. tcpserver accepts hostnames just fine, with
appropriate
> > > syntax. See the documentation for tcpserver for details.
> [...]
> > Thinking this might be what I was looking for, I tried putting both
> > "=.pm0.net:deny" and "=pm0.net:deny" successively into a test.cdb and
> > then ran the following (with results shown (the results were the
> > same in both cases)):
> >
> > $ tcprulescheck test.cdb ofr.pm0.net
> > default:
> > allow connection
>
> The tcprules syntax above is the correct one; the problem here is you're
> not invoking tcprulescheck properly. It takes the remote host
> information in an environment variable, not as an argument.
>
I also tried the following:
$ export TCPHOSTNAME=ofr.pm0.net
$ rcprulescheck test.cdb 216.205.21.68
default:
allow connection
I must still have something slightly off....
[snip]
>
> Life as a mailserver administrator isn't easy :).
>
Agreed. :-)
> > vdelivermail currently has two possible options for dealing with
> > "no mailbox" situations. 1) deliver a copy of the undeliverable
> > message to an actual Mailbox (default to postmaster) or send a
> > bounce message. Looks like I might end up hacking on vdelivermail
> > until it yields a third option... sending undeliverable messages
> > to /dev/null.
>
> Perhaps it already works if you specify the default mbox you want it to
> deliver to is /dev/null?
>
That was the first thing I tried at 10pm last night... Nope. Don't
work. vdelivermail wants either a DIRECTORY it can write messages
to, or 'bounce-no-mailbox' in which case it bounces. If you put
/dev/null in there, it tries to change into the /dev/null directory
(which fails) and leaves the message in the queue assuming that
it is a transient failure.
> > That still doesn't inform the broken list managers of their problem,
> > but at least it will unclog my outbound queue of wasted bounces.
>
> The other way to handle this would be to throw away _outgoing_ mail
> destined to that host (i.e. the bounces you're generating) before they
> go over the wire. You can do this with virtualdomains and an
> appropriate dot-qmail file containing only a comment.
>
Almost, but not quite. When using vpopmail and virtualdomains, the
.qmail-default file MUST contain the vdelivermail executeable or
the mail will not get delivered to the appropriate directory.
However, I have patched my copy of vdelivermail to allow a third
option - discard-no-mailbox. This will "silently" discard the
message if it is bound for an invalid recipient (it does log the
action), and returns 0 for success so the message is removed from
the queue.
Eric Calvert
