Community Discussions and Support
Limit the number of incoming emails from one source?

Sure, here is a link to the Mercury Daemon developer kit:

http://community.pmail.com/files/folders/mercur/entry10073.aspx

/Rolf

<p>Sure, here is a link to the Mercury Daemon developer kit:</p><p>http://community.pmail.com/files/folders/mercur/entry10073.aspx </p><p>/Rolf </p>

We are running Mercury 32 4.72.  We have recently had a problem wherein an outside web site provided an email form for an individual to send email of a political nature to several dozen local users (this is a political environment).  We were swamped by incoming email from this one site.  So much so that Mercury crashed, unable to process the volume of email (and needless to say, all OTHER email was either rejected or extremely delayed).

Does Mercury have any configuration settings to limit how much incoming email we will accept from a particular IP address over a period of time?  If not, is this possible and has it ever been suggested as a new feature?

Also, if Mercury can not assist us in this, does anyone have any ideas how we can keep one source from overwhelming Mercury to the point of crashing?

Thanks for any information you can provide!

Charlie



<p>We are running Mercury 32 4.72.  We have recently had a problem wherein an outside web site provided an email form for an individual to send email of a political nature to several dozen local users (this is a political environment).  We were swamped by incoming email from this one site.  So much so that Mercury crashed, unable to process the volume of email (and needless to say, all OTHER email was either rejected or extremely delayed).</p><p>Does Mercury have any configuration settings to limit how much incoming email we will accept from a particular IP address over a period of time?  If not, is this possible and has it ever been suggested as a new feature?</p><p>Also, if Mercury can not assist us in this, does anyone have any ideas how we can keep one source from overwhelming Mercury to the point of crashing?</p><p>Thanks for any information you can provide!</p><p>Charlie</p><p> </p><p> </p>

Please update to version 4.73! There was a problem in previous versions with generating filenames for temporary files that could cause errors during periods of heavy load. Other than that the capacity of Mercury is mostly hardware-dependent.

There are several ways to block a particular IP address from accessing Mercury, but no way to set some kind of volume limit. It would be possible to create an event daemon to do it, though. As it isn't likely that there would be many Mercury installations that would benefit from this functionality it's probably be the most reasonable way to do it.

/Rolf

<p>Please update to version 4.73! There was a problem in previous versions with generating filenames for temporary files that could cause errors during periods of heavy load. Other than that the capacity of Mercury is mostly hardware-dependent.</p><p>There are several ways to block a particular IP address from accessing Mercury, but no way to set some kind of volume limit. It would be possible to create an event daemon to do it, though. As it isn't likely that there would be many Mercury installations that would benefit from this functionality it's probably be the most reasonable way to do it.</p><p>/Rolf </p>

Rolf:

Can you direct me to any resources about CREATING the event Daemon?

Thanks again!

Charlie

  ~~~

<p>Rolf:</p><p>Can you direct me to any resources about CREATING the event Daemon?</p><p>Thanks again!</p><p>Charlie</p><p>  ~~~</p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft