RE: "User send limit reached" <-- Found it

Hi,

After working my way through each config-menu, I found a few
things which
*could* have an effect on this:

"g_user_send_max", where each "group"
can be defined. It has always been
empty in my server.

"g_user_send_ip", which has also been empty.

"g_user_send_white", which has wildcarded our
C-net.


After defining "g_user_send_max" with a large
number for each group, and
defining our C-net in the other two paraneters, mails again
could be sent.

I really don't know what actually changed the behaviour, as
the
documentation is not very clear for either of these
settings.

What I would love to see in the SurgeMail documentation, is
some
relationships between error messages in the log files, and
the actual
settings which can affect the creation of the error
messages.

In this case, I'd appreciate if I could search the docs/help
files for the
text "User send limit reached" and list the
parameters / settings involved.

Best regards,
Robert



-----Original Message-----
From: Robert Hercz [mailto:robert.herczteletopia.com] 
Sent: 2. november 2007 10:49
To: surgemail-listnetwinsite.com
Subject: [SurgeMail List] "User send limit
reached"

Hi,

SurgeMail is bouncing mails from a mail sending service we
have, but I have
not found any setting which can be adjusted to allow tons of
mails to be
sent from certain IP addresses or certain senders.

Can someone pls direct me to the setting(s) I need to
change?

Best regards,
Robert Hercz

Any time we come across an error which isn't meaningful we
add the setting in question to the error text so a table 
should not be needed.  This is one of those that is fixed in
the new beta's. There should be very few if any that are 
still unclear, but let me know if you see one.

	ChrisP.


surgemail-listnetwinsite.com wrote:
> "Robert Hercz" <robert.herczteletopia.com> wrote:
>> What I would love to see in the SurgeMail
documentation, is some
>> relationships between error messages in the log
files, and the actual
>> settings which can affect the creation of the error
messages.
>>
> 
> Yes!  This is exactly what we need...  Meaningful error
messages, and a clear table telling us what settings trigger
what error messages.
> 
> 
> George