similar to: [PATCH] lib-imap: imap-bodystructure: add test with empty header field

Ok, I have narrowed my IMP/Dovecot attachment problem down to what I think is a bug in Dovecot. The test that follow are performed on 0.99.11. When you download an attachment in IMP it uses the php function imap_fetchbody() which contacts the IMAP server and retrieves just the mime chunk you are looking for. It does this by first fetching some information about the email, and then grabs the

First let me thank you for my initial newby question about poping from a pop3 server and delivering into my Dovecot maildir folders. Now I'm getting an assertion in imap-bodystructure.c and one of my imap folders is now inaccessable. I think the two are related. Whenever I select the folder from my email client (kmail) I get two log entries in the dovecot log of the format:

Hi, I tried to see a mail that have a strange From header in bellow URL: https://www.mailsploit.com/index Then, I got BODYSTRUCTURE response contain next: ((NIL NIL "service" "paypal.com")) Are this problem already founded by anyone? So already fixed? -- TACHIBANA Masashi QUALITIA CO., LTD. mailto:tachibana at qualitia.co.jp

Hello, we are developing a web page, for a ticket system, to show the email messages ordered by the biggest attachments size present in an IMAP folder, with a pagination of 100 messages per page. Each raw represents a message with "DATE, FROM, SUBJECT, the preview (the first 500 chars of the text/html of the messsage) and the list of the attachments (name + size) it contains. The

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird)

Hi! I've found a bug in Content-Type parsing. It's old instance of dovecot 1.1. Maybe fixed in newer versions. I have a mail with header: Content-Type: multipart/signed; boundary="------------080705010808010608030700"; protocol="application/x-pkcs7-signature";micalg="SHA1" and it works, but when the boundary is in different order Content-Type:

Hi there I'm using dovecot-1.1b2/b3 with deliver. All information is stored in an SQL database and no errors related to this issue are written to the logs (actually I get no errors at all). I've run into at problem; FETCH BODYSTRUCTURE is broken after upgrading to dovecot 1.1b2 (same issue with 1.1b3). BODUSTRUCTURE only returns information from the first section (with incorrect

I'm running Dovecot on a Debian system which recently has been failing on an assert(). I have a spam mailbox that if I try and open (from any client), the imap process dies and this is written to the error logs: Dec 21 18:57:11 theronge imap(mronge): file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset -

On 3. Mar 2020, at 20.38, Simon Ser <contact at emersion.fr> wrote: > > This causes the body structure to be incorrect. The RFC says it's fine o > have empty header field values. The problem isn't empty header field. It's that the mail is missing Mime-Version header. If that doesn't exist, then the Content-* headers can be ignored. But because there are so many

Hi, I've changed a program that fetches mail via IMAP from an Exchange Server to use our Dovecot machine. But now I'm experiencing strange problems with seem to be caused by a wrong BODYSTRUCTURE answer that causes wrong charset handling. When fetchting the BODYSTRUCTURE I see this: Dovecot: 88 UID fetch 32 (BODYSTRUCTURE) * 1 FETCH (UID 32 BODYSTRUCTURE ("text"

Hi there, Quoting RFC 3501 sec. 7.4.2 ?FETCH Response? (data item BODYSTRUCTURE): ?A body type of type MESSAGE and subtype RFC822 contains, immediately after the basic fields, the envelope structure, body structure, and size in text lines of the encapsulated message.? According the ABNF (RFC 3501 sec. 9) the envelope structure is that of the ENVELOPE FETCH data item, and the

Hi, I have a problem with the filename of attachments in some clients. # dovecot 1.2.(5|7) * 3 FETCH (BODYSTRUCTURE (("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 13 1 NIL NIL NIL NIL)("text" "plain" ("charset" "UTF-8" "name" "ISO-8859-1''testanh%E4ng.txt") NIL NIL

Hello, I have the following issue: When using command? FETCH 2 (BODY.PEEK[HEADER] UID INTERNALDATE FLAGS BODYSTRUCTURE) on 2 different emails, we get 2 different response structure. First response structure contains the BODYSTRUCTURE in a single line, while in the second response, the BODYSTRUCTURE is divided into multiple lines with "{61}" character at the end of each line.

Hi all, at work we use Roundcube acting as a mail client for the Dovecot Imap server. In Roundube the messages are parsed through the Imap BODYSTRUCTURE command If a message contains forwarded messages and attachments and some of the messages contains a quote (") in the subject, then the resulting BODYSTRUCTURE appears to be malformed. --- After some digging through the code of

Fyi... Sam Varshavik (courier-imap developer) claims (on the courier-imap list, see attached) dovecot is incorrectly parsing messages with missing/invalid "MIME-Version:" header... I have no clue if he is correct... if so, maybe this has already been fixed? -------------- next part -------------- An embedded message was scrubbed... From: Sam Varshavchik <mrsam at courier-mta.com>

On Fri, Dec 08, 2017 at 18:47:37 +0900, TACHIBANA Masashi wrote: > Hi, > > I tried to see a mail that have a strange From header in bellow URL: > > https://www.mailsploit.com/index > > Then, I got BODYSTRUCTURE response contain next: > > ((NIL NIL "service" "paypal.com")) > > Are this problem already founded by anyone? > So already

FYI. Does Dovecot implement BODYSTRUCTURE? An eval copy of Mulberry can be downloaded from <http://www.cyrusoft.com/mulberry/>. ------------ Forwarded Message ------------ Date: Tuesday, February 10, 2004 6:56 PM +0100 From: Lennart Petersson <lennart at informatik.gu.se> To: mulberry-discuss at cyrusoft.com Subject: Dovecot and Mulberry I've recently changed my imap-server

Hello, We upgraded one of our dovecot servers to debian stretch with dovecot 2.2.27 and since then one of our users has been experiencing random IMAP failures. We enabled raw logging at the server side and it shows normal IMAP commands/responses: 1507292522.222427 * 6 FETCH (FLAGS () BODYSTRUCTURE ("text" "plain" ("charset" "us-ascii") NIL NIL

https://bugs.freedesktop.org/show_bug.cgi?id=109330 Bug ID: 109330 Summary: GL_ALPHA_BITS set to non-zero with EGL_PLATFORM_GBM_MESA Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

Again rc, just in case I broke something. Or maybe I should just start creating nightly CVS snapshots. Anyway, fixes the few bugs people have reported lately: - Mails with nested MIME parts might have caused incorrect BODY and BODYSTRUCTURE fetches and sometimes might have crashed dovecot (assert at imap-bodystructure.c). If client had already successfully done the BODY fetching a