Rather than using POP3, we use IMAP.  Since Exchange usually stores user
accounts as "username" and not the full email address, we also strip the
domain information.  I cannot speak well to opening really large
accounts as our users use OWA rather than SurgeWeb or WebMail.  The few
who do use SurgeWeb or WebMail have not reported any problems.
 
The config line for this in surgemail.ini is:

surgewall_options strip_domain="TRUE" proxy_failover="" auth_local="" \
pop="exchange.domain.name" smtp="exchange.domain.name" \
imap="exchange.domain.name" usercgi="imap"

The parts that matter are:

strip_domain="TRUE"
usercgi="imap"


Hope this helps.

--Eban


IN REPLY TO:

From: Surgemail Support (Marijn)
[mailto:surgemail-support@netwinsite.com] 
Sent: Thursday, October 07, 2010 04:38 AM
To: surgemail-list@netwinsite.com
Subject: [SurgeMail List] Re: Surgewalled Domain slow user.cgi web login

No, surgewall uses proxied POP / IMAP / SMTP connections to the
destination server for authentication rather than locally defined
"accounts". 

Personally I am not aware of issues here, but I'm not generally the
person providing answers to the surgewall mode questions. 

Have other admins seen issues along these lines? and has anyone come
across any exchange side fixes to improve this?

Marijn

On Wednesday 06/10/2010 at 3:20 pm, surgemail-list@netwinsite.com wrote:
Hello-

We are running Surgemail 5.0e3-3 but have seen this with previous
versions..

Domain running in Surgewall mode in front of Exchange 2003 server.

POP proxy is pointing to server:995

Users with large inboxes are taking a long time to login to manage their
spam, users with small mailboxes log in very quickly it looks like the
issue is with the initial POP of the exchange mailbox.

Is there an alternate way to authenticate that will provide fast login?

Thanks!

Jay