"Webmail for NUTS" and I really mean it

[subhankar sengupta]

Hi All,
One of my mail server has Postfix,courrier-IMAP,squirrel mail and
TRENDMICRO IMSS(5.5) installed.Since yesteray I am not able to open
my webmail.
My SMTP,POP and even IMAP is running properly. I have restarted apache
it is running properly.
I have even manualy started IMSS daemon(S99IMSS and regserver) but it
is of no use.
When I try to open my webmail using IE it shows error code 400 but
with FireFox it is showing InterScan Error so I doubt the problem is
with IMSS but have no clue how to go about it cause while restarting
IMSS it successfully comes up.
Subho

[Tom Robinson_1]

Have you looked for clues in the log files? What OS are you using? Perhaps you have a full disk?

[Steven E. Protter]

Shalom,

1) Squirrelmail requires an imap server running on port 143. Make sure dovecot is installed then:
chkconfig --level 345 dovecot on
service dovecot start

Try again, checking the /var/log/maillog for errors.

Respond to the errors and report back.

Please post the error you are getting.

Also, for a test, shut down trend micro and see if its interfering with normal mail operations.

SEP

[subhankar sengupta]

Hi,
I am using RHEL ES 3 and my disk is not full.
Rgds,
Subho

[subhankar sengupta]

This is the exact error I getting,


InterScan Error
InterScan HTTP Version 3.81-Build_1022 $Date: 12/19/2003 17:51:0017$

Unknown URL type: /

[Tom Robinson_1]

You say 'since yesterday you can't open webmail'. Did anything on your system change before you were denied access to webmail? Have you installed something or changed a configuration (firewall perhaps)?

[Manuel Wolfshant]

Sub

First of all, THINK and RETHINK what modifications have occured between the last time the system was working (last restart/reload) and the time you have noticed the error for the first time (any software upgrade maybe?)
I would say that most probably you have a broken configuration somewhere in squirrel, which is not serving the login pages as it should. However, this might relate to an error in the results reported by courier. I would definitely start by rechecking the configuration of apache related to squirrel (access rights, directives and so on). Did you happen to upgrade apache or squirrel since you have last started the functional version of the system?
Keep an eye on the logs of apache for squirrel (access.log, so that you know EXACTLY what URL is accessed AND error.log so that you know equally precisely what URL triggers the error). Corelate that with courier logs (usually /var/log/maillog unless you have modified something); you can increase the verbosity of squirrel editing the configuration files (placed in /etc/authlib/ if your courier-authlib is new; otherwise they are somewhere under /usr/share/courier-something if memory serves me well) -- look for the DEBUG_LOGIN option in authdaemonrc). Try to temporarily disable IMSS and see if the errors still occur. If they do, the erorr is not in IMSS; if they do, you have found the culprit.
Since the errors occur when you try to READ the mail, postfix is out of the question; it is only used when you SEND an email. I suggest trying to isolate the problem: if possible, use a regular email client instead of squirrel to access the courier server directly (You might eventually use telnet (telnet imap-server 143) but you would need to know the IMAP commands in order to issue them manually). If it's OK, the problem is somewhere between apache and squirrel; if not, it's between squirrel and courier.