Question Outgoing mail control : Manage rejected messages ?

[Pascal_Netenvie]

Hi,
On our servers we use Outgoing mail control from Plesk 17.5.
When a subscription is over quota, for example it try to send 500 mails instead of 50 in one hour, is there a special queue where rejected messages are stored in ?
If this queue exist how to empty it ?

Cheers

 

[UFHH01]

Hi Pascal_Netenvie,

this is actually not a "special" queue, it's just the normal mail - server queue, which you are able to see at => HOME > Tools & Settings > Mail Server Settings > (tab) Mail Queue , or with the command ( logged in as user "root" over SSH ):

mailq

or

postqueue -p

... when you use postfix.

If you desire to delete the mail queue, you could use:

postsuper -d ALL

... or if you desire to delete all "deferred" mails, you could use:

postsuper -d ALL deferred

Over the Plesk Control Panel, you have as well the choice to flush/delete/clear the mail queue.


For additional postfix informations, you might like to visit: => Postfix manual - postqueue(1)

 

[Pascal_Netenvie]

Thanks for answer, i know all that
But even with mailq empty i have new rejected messages that i can't find !
That 's why i ask that.

 

[Bitpalast]

The messages that are rejected by the outgoing mail limit are not queued. They are discarded. Else in case of viruses sending mail your mail queue would fill up with tens of thousands of mails waiting for the next opportunity to pass the mail limit. It does not make sense to queue such messages for further delivery attempts.

 

[Pascal_Netenvie]

Hi Peter,
Ok i understand the point but in this case how can we analyse one or two message to find origin of problem ??
Outgoing control script should keep some messages somewhere in a log to help find out where is the problem.

 

[Hangover2]

@Pascal_Netenvie You can find a log about those rejected message in /var/log/maillog or the specific mail log of your operation system. Search for REJECT message as outgoing mail rate limits are exceeded . The extra information provided by from= and to= can help to identify the root cause for hitting the limit.