Hi Thijs,

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.

Soooo, is there a debug setting for Squirrelmail to see exactly what is
being sent to the IMAP processing? And at the least, if there is a
touchy situation with virtual mailboxes and Squirrelmail, a heads up in
the install process would be good. However, it stills needs to be
determined what is happening.

-jeff

Thijs Kinkhorst wrote:

>Hello Jeff,
>
>  
>
>>The setup is with a Cyrus(IMAP), Postfix, and LDAP. Cyrus works just fine, 
>>clients 
>>can retrieve mail with no problems.. Squirrelmail did work fine
>>at an earlier time. Obviously it is not used much since I'm not able to 
>>pinpoint
>>when it broke. I have a similar setup on another machine (running Etch) 
>>serving another domain, 
>>squirrelmail works fine there.. Perdition is running on the machine that has 
>>the broken squirrelmail 
>>(believe though that I did check it after installing perdition several months 
>>ago though it might have 
>>been the time it broke...can't remember). I tried tracking it down by 
>>increasing the log levels at 
>>various points, but the only info that it seems to report is the cross-realm 
>>denied thing. The 
>>squirrelmail src/configtest.php reports no problems.
>>    
>>
>
>Thanks for your report. However, I strongly doubt this to be a problem
>with SquirrelMail. The message:
>
>  
>
>>Cannot login: reports "cross-realm login [EMAIL PROTECTED] denied"
>>    
>>
>
>is passed straight from your IMAP server; SquirrelMail does not do any
>authentication by itself. Checking out the logs of your IMAP server, or
>of the authentication backend it uses might yield more clues.
>
>I leave it up to you to reassign this report to any other package if you
>discover the problem to be there. Otherwise, I'll close it soon.
>
>
>Thijs
>  
>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to