Wietse Venema wrote:
Daniel L. Miller:
[ Charset ISO-8859-1 unsupported, converting... ]
I don't know what the correct terminology is for my question - please
adjust my wording as needed.
When a user mistypes a remote e-mail address (not that THAT ever
happens!), the result is typically either a "user unknown", "invalid
recipient", or "host or domain not found" message. At least for MY
Um, why is "user unknown" mail stuck in your queue? It should be
returned as soon as Postfix finds out.
It's quite possible I have something misconfigured...here's are some
samples from my current "mailq" -
7A44F20CED3 4338053 Mon Dec 28 10:50:59 idiotu...@amfes.com
(Host or domain name not found. Name service error for
name=fireprotectionbymesa.com type=AAAA: Host not found)
jeff...@fireprotectionbymesa.com
5F47320CEC2 4338844 Mon Dec 28 13:12:09 idiotu...@amfes.com
(host mail.fireprobymesa.com[65.40.152.138] said: 550 5.1.1 User unknown
(in reply to RCPT TO command))
jeff...@fireprobymesa.com
First he got the domain wrong - but he also got the username portion
wrong as well.
system, with MY configuration (however flawed it may be), this results
in a couple messages floating in the send queue with these statuses.
Periodically, I'll check for such items, notify my users of a problem,
and delete them from the queue.
I do have a bounce_template_file, and I've TRIED to make it a bit more
informative - but my users still cross their eyes and call me and
complain that OUR mail server is broken!
Is there a more advanced option that can give individual messages
instead of a generic bounce message? Something that might parse the
rejection and give specific advice to the computer illiterate?
This option is called transport(5) (and involves setting up
specific rules for specific RECIPIENT addresses or domains).
But I don't recommend that you do this.
I believe I understand where you're headed with this - but it's NOT what
I was asking! I DON'T want to manually maintain transport tables to
handle user misspellings. Instead I was hoping the server could examine
the error and automagically make a recommendation back to the
authenticated local sender for a user correction. Something
like...(pseudo code logic) if host not found, either remote server's DNS
is wrong or user mistyped - recommend verifying domain name prior to
re-sending.
Also, is there any e-mail interface for canceling messages? So that if
a slightly more competent user actually READS the bounce message,
determines that they spelled it wrong - they can tell the mail server to
cancel the send?
Again, why is "user unknown" mail stuck in your queue anyway? It
should be returned as soon as Postfix finds out.
Wietse
--
Daniel
