I believe that you'll find that it is associated with G_CON_PERSUBNET. If you search for that setting withing Surgemail, you should see "Exception IP addresses to g_con_perip" right below it. Adding the desired IP address to the exception list should stop teh messages for the IP excepted, and allow email to pass from that IP.
Eric Vey HIDDEN@@ericvey.com> wrote:
>I looked at my max settings and they all seem reasonable:
>g_bomb_max_from not set, so defaults are used.
>g_bomb_max is set at 2000
>g_max bad_to is 10
>g_con_perip is set at 15
>G-tarpit_max is 50
>g_maxbad_nolookup is 4
>please excuse my typing on these. Couldn't cut and paste, but I'm using
>the web page, so they ate not mistyped on the config page.
>Lyle Giese wrote:
>> On 06/06/11 16:36, Eric Vey wrote:
>>> I asked about this entry in my msg.log a few weeks ago and nobody
>>> replied. Now I am getting more and more of these: "Rejected
>>> 220.127.116.11 none <none> 0 "maxfrom_check" "
>>> I'm just afraid I set something a little too low and I am rejecting
>>> legitimate mail . . . Probably not, but the frequency makes me wonder.
>>> Does anybody know what setting generates these log entries?
>> 1) this ip looks like a dynamic end user IP address.
>> 2) Possibly g_bomb_max_from
>> Once you turn on this setting, after every email sent from a
>> subscriber, you may get this entry. I think, it's how Surgemail keeps
>> track of how many a subscriber/ip address has sent for the max send
>> Lyle Giese
>> LCR Computer Services, Inc.
Last Message | Next Message
Site Map |
Contact Netwin |
POP3 Mail Server |
Linux Webmail |
UnInstall instructions for all products
Copyright © 2017 Netwin Ltd. All rights reserved.