Jorge Bastos wrote:
Hum ok,
But i need to know one thing.
I have about 30 messages in queue, and a few dbmail-lmtpd processes eating
my cpu.
The question is:
Im going to save the raw message, and then delete it. And after 1/2 hours
check if the dbmail-lmtpd processes stoped eating the CPU.
Does it need to restart postfix or dbmail? (maybe doesn't matter at all)
You don't have to restart anything unless you want to stop dbmail-lmtpd.
One more tip though which might help you. When you list the mail queue
with postqueue -p, some of the message ID's have an asterisk after them,
like:
88A2EDCBC*
^
|
this one
It means this messages is being delivered right now. When you do
postqueue -f, then all the messages in the queue will have the asterisk.
You might be able to narrow the list of problematic messages down when
keeping the asterisk in mind.
From the manual:
-p Produce a traditional sendmail-style queue listing. This
option implements the traditional mailq command, by contacting the
Postfix showq(8) daemon.
Each queue entry shows the queue file ID, message size,
arrival time, sender, and the recipients that still need to be
delivered. If mail could not be delivered upon the last attempt, the
reason for failure is shown. This mode of operation is implemented
by executing the postqueue(1) command. The queue ID string is followed
by an optional status character:
* The message is in the active queue, i.e. the
message is selected for delivery.
! The message is in the hold queue, i.e. no further
delivery attempt will be made until the mail is taken off hold.
HTH,
--
Aleksander Kamenik
system administrator
+372 6659 649
[EMAIL PROTECTED]
Krediidiinfo AS
http://www.krediidiinfo.ee/
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
