Bug 121084
| Summary: | message delimiter found while scanning headers | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ralf Corsepius <corsepiu> |
| Component: | fetchmail | Assignee: | Miloslav Trmač <mitr> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | bugs.michael |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-06-03 23:07:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Reporter says the "leading-edge" 6.2.5 version of fetchmail, which is included in Fedora Core 2 and which is recommended by ESR, http://www.redhat.com/archives/fedora-devel-list/2004-March/msg00424.html fixes this problem. The changelog mentions a few mail header parsing improvements. How about a Test Update for FC1? I'm sorry about the late response. FC2 and FC3 already contain fetchmail 6.2.5, FC1 is now supported by Fedora Legacy, focusing mainly on security bugs. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Description of problem: On certain types of mails, retrieving mail from a remove mail server aborts with .fetchmail: message delimiter found while scanning headers Version-Release number of selected component (if applicable): fetchmail-6.2.0-8 How reproducible: Didn't try Steps to Reproduce: Use fetchmail and wait for such a mail to come ;) Sorry, I don't know how to produce such mails which cause fetchmail to produce the error. There are some indications that certain versions of old netscape 4.x produce such kind of mails. Actual Results: Such mails can't be "fetched" with fetchmail and stay permanently on the remote server. Expected Results: Function. Fetchmail should retrieve the mail. Additional info: I consider this problem to be serious, because some spammers seem to have started to send mails which trigger the error in fetchmail. (I normally receive such kind of mails once a day, but today a wave of spam had caused 10-20 such fetchmail breakdown)