Community Discussions and Support
Sv: Thunderbird and Mercury

Trace the message path. Meaning, if you use MercuryD to pop from the isp, do enable session log to see that you actually get the message down to Mercury. Pause all other modules etc, and examine the queues, so you see what actually happens in each step.

Don't forget to turn off session logging once you're done, as session logs eats performance and disk rapidly...

<P>Trace the message path. Meaning, if you use MercuryD to pop from the isp, do enable session log to see that you actually get the message down to Mercury. Pause all other modules etc, and examine the queues, so you see what actually happens in each step.</P> <P>Don't forget to turn off session logging once you're done, as session logs eats performance and disk rapidly...</P>

I have decided to return to an issue that I tried to solve months ago; a problem using Thunderbird with Mercury.  I have just sent the same (multiple addressee) e-mail message, with a PDF attachment, through my office Exchange system to three accounts.  They are a GMail account, an account with my local Freenet, and and account with my normal ISP.  I used Thunderbird 2.0.0.19 to download the mail from all; accounts.  For the GMail and Freenet accounts, I made a direct IMAP connection and for my normal ISP, I picked up the mail using Mercury's Distributing POP3 client and then pulled it off Mercury using IMAP.  In the GMail and Freenet cases, the mail came through perfectly.  However, the copy using Mercury comes though with blank body content, though it can be seen by using Message/Edit message as new.

Thomas tried to help me when I was trying to solve this issue before, but I was unsuccessful in the end.

The only clue that I have is that after the mail comes in, the Thunderbird Error Console shows

Warning: Error in parsing value for property 'background-color'.  Declaration dropped".  Source File: chrome://messenger/content/preferences/preferences.xul Line: 0

Given the two successful messages, it seems to me that, for the blank message, I either have a problem caused by my normal ISP or there is a problem with Mercury.

There are no problem when using Outlook Express as the e-mail client.

I'm wondering whether this might be a MIME decoding problem, given the reference to "background-color" in the Error Console.  There was no colour used in the message body, but it did exist in the attachment.

If anyone has had any experience of this, since I raised the issue some months ago, I would be pleased to hear frm them. 

Thank you

Gordon

<P>I have decided to return to an issue that I tried to solve months ago; a problem using Thunderbird with Mercury.  I have just sent the same (multiple addressee) e-mail message, with a PDF attachment, through my office Exchange system to three accounts.  They are a GMail account, an account with my local Freenet, and and account with my normal ISP.  I used Thunderbird 2.0.0.19 to download the mail from all; accounts.  For the GMail and Freenet accounts, I made a direct IMAP connection and for my normal ISP, I picked up the mail using Mercury's Distributing POP3 client and then pulled it off Mercury using IMAP.  In the GMail and Freenet cases, the mail came through perfectly.  However, the copy using Mercury comes though with blank body content, though it can be seen by using Message/Edit message as new.</P> <P>Thomas tried to help me when I was trying to solve this issue before, but I was unsuccessful in the end.</P> <P>The only clue that I have is that after the mail comes in, the Thunderbird Error Console shows</P> <BLOCKQUOTE> <P>Warning: Error in parsing value for property 'background-color'.  Declaration dropped".  Source File: chrome://messenger/content/preferences/preferences.xul Line: 0</P></BLOCKQUOTE> <P>Given the two successful messages, it seems to me that, for the blank message, I either have a problem caused by my normal ISP or there is a problem with Mercury.</P> <P>There are no problem when using Outlook Express as the e-mail client.</P> <P>I'm wondering whether this might be a MIME decoding problem, given the reference to "background-color" in the Error Console.  There was no colour used in the message body, but it did exist in the attachment.</P> <P>If anyone has had any experience of this, since I raised the issue some months ago, I would be pleased to hear frm them.  </P> <P>Thank you</P> <P>Gordon</P>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft