Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 34788
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Net-Mail Packages <net-mail@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: John Huttley <john@mib-infotech.co.nz>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
fetchmail-broken-headers.patch Broken headers patch proposal (resides in files directory) patch Philippe Weibel 2004-06-01 08:56 0000 250 bytes Details | Diff
fetchmail-6.2.5-r1.ebuild fetchmail-6.2.5-r1.ebuild text/plain Philippe Weibel 2004-06-01 08:57 0000 2.34 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 34788 depends on: Show dependency tree
Bug 34788 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-11-30 17:57 0000 
version 6.2.3 (shipping version in 1.4) will fail if it sees imperfect headers 
in pop mailboxes. It reports  a protocol error and stops.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
Best would have been to ignore the header and download anyway.

The problem does not seem to occur in 6.2.5.
Suggest releasing it immediately.

Since NO pop mail is retreived, mailboxes overflow quickly.

------- Comment #1 From SpanKY 2003-11-30 19:56:46 0000 ------- 
you never actually said what program is failing

------- Comment #2 From John Huttley 2003-11-30 22:13:48 0000 ------- 
Ahem, sorry,
The program with the problem fetchmail 6.2.3.
This is the stock version as at 2003-12-01.

A bit stressed here.

------- Comment #3 From Philippe Weibel 2004-06-01 08:56:14 0000 ------- 
Created an attachment (id=32465) [details]
Broken headers patch proposal (resides in files directory)

Just accept mail that contains invalid headers (warning still issued) if end of
headers is found. This resolved the problem for me.

------- Comment #4 From Philippe Weibel 2004-06-01 08:57:30 0000 ------- 
Created an attachment (id=32466) [details]
fetchmail-6.2.5-r1.ebuild

New ebuild using my patch (~x86)

------- Comment #5 From Philippe Weibel 2004-06-01 09:03:49 0000 ------- 
I've got tons of messages in logfiles like "incorrect header line found while
scanning headers". Mails where then deleted by default (!!)

I tried some other fetchmail versions, all of them having the same problem
(6.2.0, debian patched 6.2.5-7 and 6.2.5-8)...

The patch + ebuild corrects the problem for me.

Could you add these files to portage?

------- Comment #6 From Andrej Kacian (RETIRED) 2004-09-03 10:42:33 0000 ------- 
robbat2, what do you think? I find this patch useful, as I experienced this
fetchmail behavior several times already and it's annoying. For now, I'll be
using fetchmail with this patch applied, even if it's not in portage yet.

------- Comment #7 From Robin Johnson 2004-09-03 12:48:10 0000 ------- 
Ticho: looks good to me, but I only use fetchmail with IMAP. Could you please
also send the patch to upstream?

------- Comment #8 From Andrej Kacian (RETIRED) 2004-09-03 12:59:36 0000 ------- 
-r1 ebuild, with patch submitted here, committed to CVS. Thank you, John!

------- Comment #9 From Andrej Kacian (RETIRED) 2004-09-04 01:40:29 0000 ------- 
*** Bug 62434 has been marked as a duplicate of this bug. ***

------- Comment #10 From Philippe Weibel 2004-10-20 16:30:20 0000 ------- 
"Thank you, John!" ???

Just saw the patch submitted was attribued to reporter of this bug... :-(. Ok, It's one line - patch...

------- Comment #11 From Andrej Kacian (RETIRED) 2004-10-20 16:39:39 0000 ------- 
I'm terribly sorry, Philippe, I should have checked who submitted the patch.
Fixed the ChangeLog for fetchmail.

Once again, I apologize.

------- Comment #12 From Philippe Weibel 2004-10-21 05:10:51 0000 ------- 
Forget this.
I'm happy to contribute ;-)
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug