Re: user_cgi_http_prefix - what is it for?

In some cases webmail needs to connect to user.cgi. In most
cases the 
correct host name is determined without explicitly needing
to specify the 
host via this.

In some cases, the following two possibilities spring to
mind:
 - functionally split surgemail / webmail configuration
 - if server is in DMZ and the user.cgi host is not locally
resolvable
this can be explicitly specified.

It is indeed specified as url. ie Host / ip with port.
eg:
user_cgi_http_prefix 127.0.0.1:7080

Just take a look in the webmail templates for its use. eg:
in 
config_surge.tpl:
||post_cmd||(||user_cgi_http_prefix||/cgi/user.cgi?cmd=auto_
login&||xcmd||&vhost=||vhost||)||

Marijn



--------------------------------------------------
From: <surgemail-listnetwinsite.com>
Sent: Wednesday, March 26, 2008 7:23 AM
Newsgroups: netwin.surgemail
Subject:  user_cgi_http_prefix - what is it for?

> There is an obscure parameter in scripts/webmail.ini
that manages to 
> interfere with the ability to tune and modify IPs and
ports - namely 
> user_cgi_http_prefix.
>
> What exactly does this do besides undermine new
configurations and give 
> false suggestions as to how to fix them?
>
> For example, it can be set to an IP, or to 127.0.0.1,
and either of these 
> might or might not include a port specification, that
might or might not 
> be a standard port (i.e. :80) or a suggested surgemail
port (i.e. :7080) 
> or something else.
>
> If webmail is running off IP A.B.C.D and port N, it
seems that setting 
> user_cgi_http_prefix to A.B.C.D:N fails. This suggests
it is referring to 
> a separate listener on a separate port. What port?
Where is this 
> documented?
> 

> 1. Is the user.cgi service the same as whatever is
being accessed when a 
> user opens a web session to read their email? If this
is correct then 
> user_http_cgi_prefix should refer to the IP and port
that webmail is 
> using. Also, if this is true it should be the same as
the g_webmail_port 
> parameter set in the surgemail web admin configuration
area.

Yes correct, this is user.cgi on the same ip + port that you
connect on 
using a browser.

> 3. Why would a user_cgi_http_prefix setting that used
127.0.0.1 EVER fail? 
> After all, the server must be able to see itself at a
minimum.

There are several reasons why 127.0.0.1 might fail:
-The server may be functionally split 
(http://netwinsite.com/surgemail/help/clustering.ht
m#functional) so that 
webmail needs to connect to surgemail on different server
- You may have surgemail configured not to listen on port
127.0.0.1
- OS level firewall may be blocking connections on
127.0.0.1

Marijn

--------------------------------------------------
From: <surgemail-listnetwinsite.com>
Sent: Friday, March 28, 2008 9:51 AM
Newsgroups: netwin.surgemail
Subject:  Re: [SurgeMail List] Re:  user_cgi_http_prefix -
what is it for?

> "Surgemail Support (Marijn)"
<surgemail-supportnetwinsite.com> wrote:
>>
>
> I have no idea what is being talked about here.
>
>
> Let me try and re-phrase the issue.
>
> 1. Is the user.cgi service the same as whatever is
being accessed when a 
> user opens a web session to read their email? If this
is correct then 
> user_http_cgi_prefix should refer to the IP and port
that webmail is 
> using. Also, if this is true it should be the same as
the g_webmail_port 
> parameter set in the surgemail web admin configuration
area.
>
> 2, If it is not the same, then where is the port set in
the surgemail 
> admin web pages? What is the appropriate parameter?
>
> 3. Why would a user_cgi_http_prefix setting that used
127.0.0.1 EVER fail? 
> After all, the server must be able to see itself at a
minimum.
>
> 

Hi Folks,

  Having used Surgemail for a number of years, we are
'stuck' on an oldish
version, and I am evaluating a more recent version (ver
3.8k4-4).

  There are some features that I do not wish to offer my
clients. For
example, the Friends system. If I disable it in the web
admin interface in
Surgemail (g_friends_only) then the option still appears in
thw user WebMail
interface. Is this correct?. Is the only way to remove this
option from the
client web mail in=terface by editing the relevant .tpl
file.

  There are some other features that I wish to 'hide' from
my clients (on
the basis of Keep it Simple Stupid). What a really need is a
pretty straight
forward, simple web mail interface. ANy ideas on how to
achieve this? I am
thinking thats whats needed is a Basic/Advanced option for
the user
interface, similar to the admin one.

  Grateful for any advice

rgds
Jim