On 4/27/2010 8:59 AM, Carlos Mennens wrote:
I have the Postfix parameter 'bounce_queue_lifetime' configured in
'main.cf' to 1 day. This I assume tells Postfix to only attempt to
deliver a message stuck in the queue for whatever reason for 24 hours
(1 day) before it is considered "undeliverable" and returned to
sender, right? I want to make sure I have a correct understanding of
this parameter...
In my Postconf -n listed below, you will see it is configured for 1d
however I have been showing the same message stuck in my queue for
almost 5 days. I am 100% sure the user is not re-submitting mail to
the invalid domain after they get undeliverable notifications. Am I
doing something wrong? You can see below that Postfix tagged this
message date on 4/22/2010& today is 4/27/2010.
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
9AC0B778468 239191 Thu Apr 22 11:16:54 car...@iamghost.com
(Host or domain name not found. Name service error for
name=tehnews.com type=MX: Host not found, try again)
d...@tehnews.com
When in doubt about what a parameter does, check the docs.
http://www.postfix.org/postconf.5.html#bounce_queue_lifetime
Hmm, looks as if bounce_queue_lifetime only affects bounce
(MAILER-DAEMON) messages.
If you don't want anything in your queue longer than 1d, you
can set maximal_queue_lifetime=1d, but that's not recommended.
http://www.postfix.org/postconf.5.html#maximal_queue_lifetime
If you want to help out folks who type in vaild-but-dead
domain names, such as tehnews.com, you can add transport_maps
entries to immeadeatly bounce the mail.
# transport_maps
tehnews.com error:5.1.2 not a working domain
Or if this is your own personal mail, you can just delete it
from the queue with
postsuper -d 9AC0B778468
**Postconf Begin**
smtpd_tls_loglevel = 2
tls loglevel 2 is likely to log confusing and unnecessary
messages. Best to leave it at 0 or 1.
The rest of postconf looks reasonable.
**End Postconf**
-- Noel Jones
