Re: Debug key sequence for OSX?

>> I can't find what the debug key sequence should be for debugging
>> connections on OSX - the Windows one is 'ALT F F'.
>>
>> Seem to have problems opening my default server inbox and having to
>> resort to an HTTP interface, not good for the blood pressure!
>
> Do you mean the logging options?  To get to them on a Mac hold down the option key while selecting Mulberry->Preferences...

Yes, sorry I couldn't reply with thanks because I couldn't get to my INBOX via my normal route. I did eventually find this at 
<http://trac.mulberrymail.com/mulberry/wiki/logging> and silly of me to forget it from my Classic MacOS days.

Anyway I found the root cause of my issue so here it is for anyone else that might fall into the same pit.

Problem: Mulberry does not open INBOX for a tuffmail.com hosted account but opens INBOXs for other mail accounts and permits 
access to other mailboxes in the Tuffmail account. INBOX can be accessed from IMAP clients running on Android (K9 Mail) and 
Tuffmail's HTTP clients. It can also be accessed via the OSX Mail App (after a very, very long wait for synchronisation...).

Logging shows the IMAP login and facilities of the mail server, then a SEARCH UNSEEN, then nothing.

Answer: Avast Mail Shield gets in the way but only when you restart the Mulberry application. If you didn't close Mulberry and 
restart it, it might be some days/weeks before you notice any issue.

This happens regardless of whether you have SSL on or off to your mail account.
It happens regardless of whether you set Avast Mail Shield to scan secured connections except that if you set SSL/IMAPS access to 
your account and you switch off Avast Mail Shield secured scanning, you can get access.


Solution:
1) Don't run AVAST, but that isn't very palatable
2) Use SSL to access your mail account and switch off Scan Secured Connections, but then your other SSL secured accounts are not 
scanned
3) Use the Ignore Mail Server option to exclude only the failing mail account and then decide whether you want to do SSL or not.

I don't know why it fails, but fail it does.

I had thought there was possibly a INBOX size limit at the provider (though it was nowhere near as big as it has been in the 
past, and other mail clients worked) or that some bad email was causing Mulberry to bomb the account (but protocol logging showed 
nothing). Switching to OSX Mail App with AVAST did show up at least 90+ emails sitting in mailboxes with infected attachments, so 
even though they were Windows specific issues, at least I got something for my pain.

Hope that helps someone in future.

Raza