On Mon, Jan 25, 1999 at 04:52:23AM -0000, Russell Nelson wrote:
> Why does qmail-send merely silently discard virtualdomains lines that
> have no colon? Isn't it likely that such a line is in error, and
> needs to be pointed out?
Due to the design of qmail-send, it's quite hard to report an error
in this case. rewrite() in qmail-send.c cannot even print a warning
to stderr. `not allowed to barf'... A possibility so, would be to
define a special address which could handle local configuration errors.
Example:
recipient address is `[EMAIL PROTECTED]'.
control/virtualdomains:
# the colon is missing, obviously a configuration error.
virtual.org
in qmail-send, rewrite the address to, hmmm, say
`[EMAIL PROTECTED]'.
Now ~alias/.qmail-trouble-virtualdomains could be used to handle the
error.
Anyway, most likely, the mail will bounce with the following error:
Sorry. Although I'm listed as a best-preference MX or A for that host,
it isn't in my control/locals file, so I don't treat it as local. (#5.4.6)
Background:
I tried to implement address rewriting in qmail-send based on an ldap
lookup, but I gave up on this because I was not able to handle errors
(and there are a plenty of possible errors that could occur during an ldap
lookup). The way it is implemented right now, does not allow any other lookup
mechanisms then in-memory based hash tables.
regards, Lars
