Re: g_pop_nolock

surgemail-listnetwinsite.com wrote:
> Configuration Suggestions recommends enabling
g_pop_nolock
> TRUE  Fixes locking errors caused by blackberry servers
 
> 
> Howerver, the details provide for the setting suggest
otherwise. 
> g_pop_nolock - Allow concurrent POP logins
(experimental)
> Allows concurrent POP logins, very bad, use entirely at
your own risk..  
> Syntax: g_pop_nolock bool
> 
> What is the recommended setting?

Setting true is fine, the documentation needs to be
updated.

regards,
Stuart


-- 
When replying please quote original message to save time and
always let
us know what OS and version of SurgeMail you are using.

************************************************************
****************
If you wish to communicate with other users and talk about
SurgeMail and
also get news about updates etc then join the SurgeMail
List.
Send an email to surgemail-list-requestnetwinsite.com with only 
"subscribe" in the message body

FAQ - http
://www.netwinsite.com/surgemail/help/faq.htm
************************************************************
**************** 

We have g_con_perip (maximum connections per IP) set to 15. 
We have 
one client who has about 80 users who connect exposing the
same IP 
address to the Internet.  We set their IP address into 
g_con_perip_except (IP list of exceptions to g_con_perip).

Lately they have been complaining about messages that don't
get 
sent.  An error comes back with code 550 (usually meaning
the user is 
invalid) but the message will remain in their out box and
eventually gets sent.

Finally one of them sent me the error message from Outlook
which was:

Task xxx Sending' reported error (0x800CCC03) : 'Unknown
Error 0x800CCC03)

Which seems to translate to too many connections from the
same IP or 
account.  I know they are not using the same account
multiple times.

What is the best way to handle this?  Am I missing something

here?  Does the g_con_perip_except actually work?