Outgoing Mail Control collect sample of offending emails
When Outgoing Mail Control detects a user abusing the sending limits, it would be helpful for the emails that are sent beyond the limit to be sampled in some way: To: From: Subject: Headers, possibly the first line of the email, origination ip address of the offending email.
This information can help the admin decide if it was the user just sending to many emails or if the email has been compromised and needs to be addressed.
As a similar but different idea, emails beyond the limit could be cached for a short time to allow the administrator to decide to push legitimate emails through even if they are above the limit on a case by case basis.
Randall Hinton
shared this idea
-
Messe & Handel commented
Hi it's important for administrator side, so can check - as per Randall say, ( emails beyond the limit could be cached for a short time less to allow the administrator to decide to push legitimate emails through even if they are above the limit on a case by case basis.) - I agree on this.
-
John Smith commented
hard to find the source if its from php, really needed asap
-
Gianluca DB
commented
+1
it would be much appreciated. -
Anonymous
commented
So needed. The old trick to monitor all php scripts sending email as described on the knowledge base isn't working anymore.
-
Anonymous
commented
Необходим
-
Anonymous
commented
Would be great. I hate analyzing mail logs and it is time consuming.
-
Massimo Infunti commented
Really necessary!
-
Bernd Rabe
commented
Would be very helpful to track down suspicious activities.
-
Anonymous
commented
Plesk obviously doesn't care -- this has been a problem for OVER A <expletive> DECADE.
-
Atakan Köycü
commented
Need to see wich mailbox doing ourbound spam
-
Wayne
commented
+1
This would be helpful -
Bob
commented
This can be vital in tracking down the source of not only an offending subscription but possibly a compromised email address or if the source is from a script, listing the file that generated the email in the first place.
It may be sufficient to log the headers rather than the actual email content... Or possibly just a truncated portion of the offending emails content? As long as the source (email address/script) is logged it should be sufficient to help track down security breaches and injected malware code...