Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Tbird stalling on reading data for IMAP header from ISP

  • 1 antwurd
  • 1 hat dit probleem
  • 6 werjeftes
  • Lêste antwurd fan gw_westdale

gw_westdale
gw_westdale
more options

I have raised this question before - in the context of TBird getting a long delay on running its filters to copy to my local inbox. I had some useful help from 2 people but still unable to get my emails properly from an ISP where TBird has worked fine until 2 weeks ago. Although there *is* a problem with TBIrd getting 'confused' if filters or user move messages to local inbox when the data has not arrived, the main problem with IMAP is not getting data for a message for which the header has been received. I have now run with diagnostics and it seems to show TBird 'giving up' on receiving the data.

As I do not understand the detail of the logging, I wonder if someone could be kind enough to advise what is going on - to see if it is a problem at the ISP or with TBird?

I cleared down all messages at the ISP and then sent two small messages from my gmail account. These received ok. I then sent a large one with attachment and that timed out on getting data after the header was received. I stopped and restarted TB and seemed to get similar behaviour.

The end of the second log is below and I would be very grateful for any advice as to what to try next. And any advice on how to upload a large log if that is useful -- I could load to a neocities site if that helps.


2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=78 needmore=0] 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: Oh5r6ba4qlljy2p2KlyBOlYQ8csnkNXCq7dzc+5WNGdbLmveUNypN8Chmdl8cqaOi+O0ZWvUxxZ4

2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=78 needmore=0] 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: rfxMa1C0szzXuphT9K0uFjV7ZrezC1JW9bbY1e0cy2ZX4rNgUg/21tia8YOxwWnUgP3mJ0IC35zT

2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=78 needmore=0] 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: Wsd7eOX1lDCzEzpDeCk0JDurMTd5QxuJl4iX3RKmMLc21J4K4cq1bUeVfdSJshlCW1htMRBGzkib

2015-12-12 13:49:01.453000 UTC - 0[2f11140]: c0e0000:mail.demon.co.uk:S-INBOX:CONTROL: PSEUDO-Interrupted 2015-12-12 13:49:02.433000 UTC - 0[2f11140]: c0e0000:mail.demon.co.uk:S-INBOX:CONTROL: PSEUDO-Interrupted 2015-12-12 13:49:03.625000 UTC - 0[2f11140]: c0e0000:mail.demon.co.uk:S-INBOX:CONTROL: PSEUDO-Interrupted 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: proposed url = INBOX folder for connection INBOX has To Wait = TRUE can run = FALSE 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: queuing url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: considering playing queued url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: creating protocol instance to play queued url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:03.636000 UTC - 0[2f11140]: proposed url = INBOX folder for connection INBOX has To Wait = TRUE can run = FALSE 2015-12-12 13:49:03.636000 UTC - 0[2f11140]: failed creating protocol instance to play queued url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:49.876000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=0 needmore=1] 2015-12-12 13:49:49.907000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: clearing IMAP_CONNECTION_IS_OPEN - rv = 804b000e 2015-12-12 13:49:49.915000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:TellThreadToDie: close socket connection 2015-12-12 13:49:49.915000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: (null) 2015-12-12 13:49:49.915000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:STREAM:CLOSE: Abort Message Download Stream 2015-12-12 13:49:49.919000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:ProcessCurrentURL: aborting queued urls 2015-12-12 13:49:49.929000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:SendData: clearing IMAP_CONNECTION_IS_OPEN 2015-12-12 13:49:49.929000 UTC - 10124[c01a4f0]: ImapThreadMainLoop leaving [this=c0e0000]

I have raised this question before - in the context of TBird getting a long delay on running its filters to copy to my local inbox. I had some useful help from 2 people but still unable to get my emails properly from an ISP where TBird has worked fine until 2 weeks ago. Although there *is* a problem with TBIrd getting 'confused' if filters or user move messages to local inbox when the data has not arrived, the main problem with IMAP is not getting data for a message for which the header has been received. I have now run with diagnostics and it seems to show TBird 'giving up' on receiving the data. As I do not understand the detail of the logging, I wonder if someone could be kind enough to advise what is going on - to see if it is a problem at the ISP or with TBird? I cleared down all messages at the ISP and then sent two small messages from my gmail account. These received ok. I then sent a large one with attachment and that timed out on getting data after the header was received. I stopped and restarted TB and seemed to get similar behaviour. The end of the second log is below and I would be very grateful for any advice as to what to try next. And any advice on how to upload a large log if that is useful -- I could load to a neocities site if that helps. 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=78 needmore=0] 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: Oh5r6ba4qlljy2p2KlyBOlYQ8csnkNXCq7dzc+5WNGdbLmveUNypN8Chmdl8cqaOi+O0ZWvUxxZ4 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=78 needmore=0] 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: rfxMa1C0szzXuphT9K0uFjV7ZrezC1JW9bbY1e0cy2ZX4rNgUg/21tia8YOxwWnUgP3mJ0IC35zT 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=78 needmore=0] 2015-12-12 13:47:38.017000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: Wsd7eOX1lDCzEzpDeCk0JDurMTd5QxuJl4iX3RKmMLc21J4K4cq1bUeVfdSJshlCW1htMRBGzkib 2015-12-12 13:49:01.453000 UTC - 0[2f11140]: c0e0000:mail.demon.co.uk:S-INBOX:CONTROL: PSEUDO-Interrupted 2015-12-12 13:49:02.433000 UTC - 0[2f11140]: c0e0000:mail.demon.co.uk:S-INBOX:CONTROL: PSEUDO-Interrupted 2015-12-12 13:49:03.625000 UTC - 0[2f11140]: c0e0000:mail.demon.co.uk:S-INBOX:CONTROL: PSEUDO-Interrupted 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: proposed url = INBOX folder for connection INBOX has To Wait = TRUE can run = FALSE 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: queuing url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: considering playing queued url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:03.635000 UTC - 0[2f11140]: creating protocol instance to play queued url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:03.636000 UTC - 0[2f11140]: proposed url = INBOX folder for connection INBOX has To Wait = TRUE can run = FALSE 2015-12-12 13:49:03.636000 UTC - 0[2f11140]: failed creating protocol instance to play queued url:imap://administrator@westdale.demon.co.uk@mail.demon.co.uk:143/fetch>UID>/INBOX>34288 2015-12-12 13:49:49.876000 UTC - 10124[c01a4f0]: ReadNextLine [stream=8a2c740 nb=0 needmore=1] 2015-12-12 13:49:49.907000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: clearing IMAP_CONNECTION_IS_OPEN - rv = 804b000e 2015-12-12 13:49:49.915000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:TellThreadToDie: close socket connection 2015-12-12 13:49:49.915000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:CreateNewLineFromSocket: (null) 2015-12-12 13:49:49.915000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:STREAM:CLOSE: Abort Message Download Stream 2015-12-12 13:49:49.919000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:ProcessCurrentURL: aborting queued urls 2015-12-12 13:49:49.929000 UTC - 10124[c01a4f0]: c0e0000:mail.demon.co.uk:S-INBOX:SendData: clearing IMAP_CONNECTION_IS_OPEN 2015-12-12 13:49:49.929000 UTC - 10124[c01a4f0]: ImapThreadMainLoop leaving [this=c0e0000]

Keazen oplossing

After 2 weeks of struggling to get emails and one more complete reinstall of TBird, today the emails are flowing as they should. I don't know where the blockage was and, to be honest I don't care as long as it stays like this :-)

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (1)

gw_westdale
gw_westdale Fraacheigener
more options

Keazen oplossing

After 2 weeks of struggling to get emails and one more complete reinstall of TBird, today the emails are flowing as they should. I don't know where the blockage was and, to be honest I don't care as long as it stays like this :-)