BadRequest

Problem

If you have any problem below. It means you are not able to access the SquirrelMail via web interface. in backend you might have Sendmail, Postfix or Qmail.

This is the basic troubleshooting to know if the IMAP service is running (by telneting it on 143 port). And then this Kerbros related error comes up and you're not able to telnet.

This results you can't run your webmail services. Specially any web mail system required port 143 which is IMAP protocol to be opened.

Solution

Never install imap-pop3d with the Red Hat 9 default mail server IMAP package. Don't select it during installation. this is the cause in many circumstances.

Just remove the imapd package using rpm -e imap-2000d or whatever you have installed. If you are not sure then rpm -qa |grep imap and check your package name and remove it. Then install it again.

Then ntsysv and check all services IPOP3/2/IMAP/IMAPS and then service xinetd restart. Thats all. Reboot will be a good faith to server.

Pushkar Bhatkoti

DC communications Pty Ltd,

Sydey, Australia

[email protected]

-sh-2.05b$ telnet 127.0.0.1 143
| Trying 127.0.0.1...
| Connected to 127.0.0.1.
| Escape character is '^]'.
| imapd: relocation error: imapd: undefined symbol: krb5_kt_start_seq_get
| Connection closed by foreign host.
| -sh-2.05b$ telnet 127.0.0.1 110
| Trying 127.0.0.1...
| Connected to 127.0.0.1.
| Escape character is '^]'.
| ipop3d: relocation error: ipop3d: undefined symbol: krb5_kt_start_seq_get
| Connection closed by foreign host.
| -sh-2.05b$

It doesn't matter if I do it.

imapd: relocation error: imapd: undefined symbol: krb5_kt_start_seq_get

On Mac OS X (10.4.10), if you get a "BadRequest..." error with uw-imapd, try these changes in the top level MakeFile:\n

PASSWDTYPE=pam
SSLTYPE=none

Recompile.

You will get a warning that this violates an RFC, but is okay if you are only accessing IMAP from the localhost.

Remember to move imapd to an appropriate directory.

If you have Linux Red Hat 9 installed and you experience Bad Request issues, it might be because of a bad service user in

/etc/xinetd.d/imap

The user should be root. If you accidentally altered the user edit the setting and be sure to change it into root. It should work.