note: I'm not at the affected machine at present (...have limited time these days for administration...in general, it is a very stable machine and so can typically live without me).
Some key points: - affected machine is running under sarge while unaffected is etch. - the only new thing that I can think of that changed is the addition of perdition, however the only thing that I can think of then that would be a factor is the /etc/saslauthd.conf file for verifying passwords on the LDAP server. It may be that the combo of perdition and saslauthd.conf may work for IMAP mail lookups but not for Squirrelmail. It's a bit unclear to me that perdition does get involved in the squirrelmail/imap interactions; possibly, if perdition grabs *all* traffic on the imap port, which is what I assume Squirrelmail is using. Let's see if perdition can be cut out of the picture as you suggest. (However, I also believe perdition may do some address rewriting, but I'm not sure offhand. Something to check.) - however, to the last point above, I did try entering the account name in various forms but still no luck, i.e. as jeff and [EMAIL PROTECTED] and [EMAIL PROTECTED] - I did a diff for all of the config file pairs that I could think of between the two systems and nothing seemed to show. When there were differences that I thought could possibly cause the problem I made the affected system consistent with the unaffected but the problem still remained. - I do employ TLS in the mail setup. So, the consistency between the two components needs to be checked. Also need to compare the Squirrelmail settings between the two systems though I think the diff mentioned may have hit that already. - Don't believe that I'm using any Squirrelmail plugins, but I'll check. (Memory tells me I did a vanilla install of Squirrelmail, then configured the apache file.) I'll check all of your suggestions when I get to the machine(s), and thank you for helping out. In particular, I'll start cutting out separable components to simplify. -jeff Thijs Kinkhorst wrote: >On Sun, 2006-09-24 at 13:48 -0400, Jeffrey B. Green wrote: > > >>The question is where is the "screw up"? Like I said, IMAP mail >>retrievals work just fine. The only other possibility that I can think >>of is Perdition, however Perdition is mainly just routing, though it >>does do the regular expression matching to identify which server to >>send to. >> >> > >Well, a first thing would be to configure SquirrelMail to access the >IMAP server directly and not through perdition. > >Are you using any SquirrelMail plugins? If so, you might try to disable >them all and see if that helps. Are you perhaps using the vlogin plugin? > >You can check the SquirrelMail authentication settings (like SSL/TLS) >and whether you've set the IMAP Server Type correctly. > >Are you sure that you're using exactly the same login credentials as >your other IMAP client uses? > >If it used to work and now doesn't anymore, something must have changed. >What did you change? > > > >>Soooo, is there a debug setting for Squirrelmail to see exactly what >>is being sent to the IMAP processing? >> >> > >SquirrelMail is designed to be good at its own function and leave for >other programs what they do best. Hence, the logging of IMAP calls is >left to the IMAP server: you'd best check the log of Cyrus for the exact >commands executed. > > > >>However, it stills needs to be determined what is happening. >> >> > >As you can see - without access to your system it's mostly guessing for >me. > > >Thijs > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
