postfix does not flush queued mails

4 msg	Forwards vs aliases ?
4 msg	no content-filter for authed users

postfix does not flush queued mails
\ Patrick Schoenfeld (15 Nov 2007)
. \ Listaccount (15 Nov 2007)

1 msg	Re: [dkim-milter-beta] mlfi_negotiate() problem
2 msg	newby Q
14 msg	PAM 'smtp' file question
5 msg	Cyrus SASL2 + Postfix + PAM - part 3
9 msg	transport error?
3 msg	Can't figure out if this rejection is coming fr...
8 msg	Alias with check_recipient_access: /etc/ppostfi...
2 msg	NDR reports
7 msg	Sender-ID and the Hotmail devil...
2 msg	Postifx with IMAP
2 msg	Postfix and procmail
4 msg	destination limits - what is 'destination'
1 msg	Redirect message based on Conditions
1 msg	Cyrus SASL2 + Postfix + PAM - part 2
6 msg	Cyrus SASL2 + Postfix + PAM
5 msg	header_checks and content_filter documentation ...
2 msg	Some problem configuring postfix/procmail with ...

Subject:	postfix does not flush queued mails
Group:	Postfix-users
From:	Patrick Schoenfeld
Date:	15 Nov 2007

Hi,

appearently our external mailhub ran out of memory this night, because
clamav needed to much memory. That caused a lot of mails to be not
delivered to our internal mail server and instead beeing queued on the
mailhub. Now I removed the content scan mechanism (cause I cannot
currently restart the system to add RAM) and tried to flush the queue,
but it results in messages like the follow immediately (so I think it
does not even try to really flush!):

Nov 15 10:04:58 imr-ext postfix/qmgr[28957]: F2BA3C00A13:
to=<info>, relay=none, delay=58974, delays=5
8974/0.03/0/0, dsn=4.4.1, status=deferred (delivery temporarily
suspended: connect to 127.0.0.1[127.0.0.1]: Connection
refused)

I don't know If I am right, but I am aware that a lot of mailservers
implement something thats like a 'hard freeze' when mail submission
results in a lot of errors in a short time. That means that the
mailserver won't try to deliver within a certain time for those mails. I
don't know if postfix has such a logic, but if i would think that is
whats happening here. But how can I force postfix to process these
mails? How can I postfix force to process frozen mails at all? (because
something like sendmail -qf is not supported). I feel quiet confident in
this because new mail processing seems to work.

I tried to fastflush mails for some important domains with -qRdomain but
that does not work either.

What am I missing? How can I debug this, because adding -v to the qmgr
process in master.cf does not produce useful output. How can I be sure
what postfix is trying to connect? (Because it only says it cannot reach
127.0.0.1 but not a port or something).

Thanks in advance
Best Regards

Patrick