This is a weird one: (SuSE 9.0 Pro)
My server just started having this problem after a reboot.
Only DHCP and Named were added, and DNS was not enabled.
On boot, Postfix, Amavis and Cyrus start without errors, but
the mail is all queued and not delivered. The following is
reported:
Aug 25 16:01:24 yoda postfix/lmtp[2249]: 33CAD657DE:
to=
Quoting Jim Sabatke
This is a weird one: (SuSE 9.0 Pro)
My server just started having this problem after a reboot. Only DHCP and Named were added, and DNS was not enabled.
On boot, Postfix, Amavis and Cyrus start without errors, but the mail is all queued and not delivered. The following is reported:
Aug 25 16:01:24 yoda postfix/lmtp[2249]: 33CAD657DE: to=
, orig_to= , relay=none, delay=-17805, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused) I searched the net and found other references to this problem, but not a single solution, except to restart Amavis, Postfix and Cyrus IMAP.
The restarts do make the problem go away, and a "postqueue -f" flushes the queue (which had built up to 500 some messages by the time I did this).
I'd like to know if there is a more robust solution.
Sounds like Amavis didn't start properly. Make sure it starts before Postfix. HTH, Jeffrey
Jeffrey L. Taylor wrote:
Quoting Jim Sabatke
: This is a weird one: (SuSE 9.0 Pro)
My server just started having this problem after a reboot. Only DHCP and Named were added, and DNS was not enabled.
On boot, Postfix, Amavis and Cyrus start without errors, but the mail is all queued and not delivered. The following is reported:
Aug 25 16:01:24 yoda postfix/lmtp[2249]: 33CAD657DE: to=
, orig_to= , relay=none, delay=-17805, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused) I searched the net and found other references to this problem, but not a single solution, except to restart Amavis, Postfix and Cyrus IMAP.
The restarts do make the problem go away, and a "postqueue -f" flushes the queue (which had built up to 500 some messages by the time I did this).
I'd like to know if there is a more robust solution.
Sounds like Amavis didn't start properly. Make sure it starts before Postfix.
HTH, Jeffrey
You nailed it. For some reason, YaST set amavis to NOT start at boot, so it wasn't running at all. I sure didn't set it that way, and it never occurred that it might not be. On the "restart" it never gave a warning that it wasn't running like some services do. Of course the 127.0.0.1 error didn't exactly scream "amavis isn't running you idiot" to me. Thanks! No wonder I never saw responses to this problem on the net, they were too embarrassed to post them. -- Jim Sabatke Hire Me!! - See my resume at http://my.execpc.com/~jsabatke Do not meddle in the affairs of Dragons, for you are crunchy and good with ketchup. NOTE: Please do not email me any attachments with Microsoft extensions. They are deleted on my ISP's server before I ever see them, and no bounce message is sent.
participants (2)
-
Jeffrey L. Taylor
-
Jim Sabatke