search for: rfc5322

...50:09 xxx dovecot[401]: lmtp(lee)<55724><XXXXX>: sieve: msgid=? <xxxx at example.com>: stored mail into mailbox ?Notifications' A message-id line broken up is valid per RFC 5322 and header whitespace shouldn?t be significant for logging purposes https://tools.ietf.org/html/rfc5322#section-3.6.4 https://tools.ietf.org/html/rfc5322#section-3.2.2

...01]: lmtp(lee)<55724><XXXXX>: sieve: msgid=? <xxxx at example.com>: stored mail into mailbox ?Notifications' > > A message-id line broken up is valid per RFC 5322 and header whitespace shouldn?t be significant for logging purposes > > https://tools.ietf.org/html/rfc5322#section-3.6.4 > https://tools.ietf.org/html/rfc5322#section-3.2.2 Yes, that is a bug. Regards, Stephan.

Maybe this[1] page, option 3.C. That strikes me as attractive, if only the mailing-list software can easily support it. (Or be hacked to support it; I'm willing to try.) Or, the "From" could be the mailing-list, the "Reply-To" could be the author, then the "CC" could be the mailing-list plus original "CC" addresses. If someone hits the

...ersion :-) Now I've seen the new RFC 6186 specification (https://tools.ietf.org/html/rfc6186) that describe a "DNS way" to achieve the same goal. [..] 4. Guidance for MUAs By using SRV records as above, MUAs need initially only to prompt the user for their email address [RFC5322]. The "local-part" and "domain" portions are then extracted from the email address by the MUA. The MUA uses the "domain" portion as the service domain to perform SRV lookups for the services it wants to configure. If the SRV lookup is successful, the...

...own e-mail address the problem would be solved Please read here: "I operate a mailing list and I want to interoperate with DMARC, what should I do?" http://www.dmarc.org/faq.html#s_3 There are several options; yours would be: "3- Take ownership of the email message by changing the RFC5322.From address to one in the mailing list's domain (user at example.com => address at mailinglistdomain.com), and adding a DKIM signature for that domain." Best, Patrick

...as received from the mailing list with a message-id line formatted thusly: Message-ID: <VI1PR04MB513558BF77192255CBE12102B0110 at VI1PR04MB5135.eurprd04.prod.outlook.com> It would appear that the parsed message-id value that dovecot uses includes white-space (including newline characters). RFC5322 gives the message-id header format as: message-id = "Message-ID:" msg-id CRLF msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS] It goes on to say: The message identifier (msg-id) itself MUST be a globally unique id...

On Sat, Jan 17, 2015 at 01:20:58PM -0500, Gene Cumm wrote: > On Sat, Jan 17, 2015 at 12:56 PM, Patrick Masotta wrote: > > On Sat, 2015-01-17 Geert Stappers wrote: > > > If 1 person with a yahoo.com e-mail adres does reply on this > > > message, then we have test result for the setting that was changed > > > wednesday. > > > > test > > Patrick,

I created a client library to send emails for a webapp. After connecting to the SMTP server with credential setup in CPANEL, and then do NOT add Message-Id header, the DKIM signature 'h' record created by dovecot/WHM is wrong, and a Message-ID (with a capital D) header is added, invalidating the generated DKIM signature value. This causes outlook, yahoo, gmail and other email

...interaction of Sieve include extension with ManageSieve. It is updated to match new requirements in the draft include specification. Missing included scripts are no longer an error at upload time. * Updated RFC2822 header field body verification to exclude non-printing characters (RFC5322). Only Sieve actions that can create unstructured header values (currently enotify/mailto and editheader) are affected by this change. + Completed sieve-filter tool to a useful state. The sieve-filter tool provides a means to (re)filter messages in a mailbox through a Sieve script...

...interaction of Sieve include extension with ManageSieve. It is updated to match new requirements in the draft include specification. Missing included scripts are no longer an error at upload time. * Updated RFC2822 header field body verification to exclude non-printing characters (RFC5322). Only Sieve actions that can create unstructured header values (currently enotify/mailto and editheader) are affected by this change. + Completed sieve-filter tool to a useful state. The sieve-filter tool provides a means to (re)filter messages in a mailbox through a Sieve script...

...doveadm sieve plugin: Fixed incorrect initialization of mail user. This caused a few memory leaks. - sieve-filter command line tool: Fixed handling of failure-related implicit keep when there is an explicit default destination folder. This caused message duplication. - lib-sieve: Fixed bug in RFC5322 header folding. Words longer than the optimal line length caused empty lines in the output, which would break the resulting message header. This surfaced in References: headers with very long message IDs. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/doveco...

...doveadm sieve plugin: Fixed incorrect initialization of mail user. This caused a few memory leaks. - sieve-filter command line tool: Fixed handling of failure-related implicit keep when there is an explicit default destination folder. This caused message duplication. - lib-sieve: Fixed bug in RFC5322 header folding. Words longer than the optimal line length caused empty lines in the output, which would break the resulting message header. This surfaced in References: headers with very long message IDs. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/doveco...

...doveadm sieve plugin: Fixed incorrect initialization of mail user. This caused a few memory leaks. - sieve-filter command line tool: Fixed handling of failure-related implicit keep when there is an explicit default destination folder. This caused message duplication. - lib-sieve: Fixed bug in RFC5322 header folding. Words longer than the optimal line length caused empty lines in the output, which would break the resulting message header. This surfaced in References: headers with very long message IDs. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/doveco...

...doveadm sieve plugin: Fixed incorrect initialization of mail user. This caused a few memory leaks. - sieve-filter command line tool: Fixed handling of failure-related implicit keep when there is an explicit default destination folder. This caused message duplication. - lib-sieve: Fixed bug in RFC5322 header folding. Words longer than the optimal line length caused empty lines in the output, which would break the resulting message header. This surfaced in References: headers with very long message IDs. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/doveco...

On 17.6.2019 14.07, Michal Krzysztofowicz wrote: > >> On 15 Jun 2019, at 21:09, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> >> >>> On 15 June 2019 10:56 Daniel Lange via dovecot <dovecot at dovecot.org> wrote: >>> >>> >>> Am 15.06.19 um 00:36 schrieb Michal Krzysztofowicz via dovecot: >>>> Would you know if

...ot/CPANEL software are > refusing to raise this as a bug and have requested that I do it. > Hi Robert, Dovecot does not add DKIM headers, Dovecot doesn't even send email. Aside from that: - The RFC states that "Message-ID" is the actual spelling: https://tools.ietf.org/html/rfc5322#section-3.6.4 - The DKIM signer implementation in CPANEL/WHM seems to do the right thing: It adds a Message-ID header if it's missing, and creates a DKIM signature. It seems unlikely that the CPANEL/WHM DKIM implementation generates invalid DKIM signatures for all Message-ID headers it gen...

On Sun, 2014-10-05 at 12:51 +0100, Dennis Davis wrote: > On Sat, 4 Oct 2014, lee wrote: > > > Is the Subject: header required by some RFC? If it is, I'll also > > deny messages that don't have one. > Not as far as I'm aware. RFC5322, "Internet Message Format", > contains: > > The only required header fields are the origination date field and > the originator address field(s). All other header fields are > syntactically optional. More information is contained in the table > following t...

...ers of the mail you just sent, delivered with > the rolled-back-into dovecot 2.3.0.1: > > Return-Path: stephan at rename-it.nl > Delivered-To: dovecot at leo.gaspard.io > > Does that clear the facts? The Return-Path appears to not have <>, which > appears to be opposed to RFC5322. So I guess dovecot could as before > accept it, and a bug should be reported upstream (I guess to opensmtpd, > as rspamd should not touch the Return-Path) so that it puts the expected > <> around the address. What do you think about this? Yes, I will make Dovecot more lenient in th...

...5/2018 om 3:14 PM schreef Ralf Hildebrandt: > Got a coredump: > > Mar 5 15:09:42 mail-cbf dovecot: lmtp(backup at backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master: service(lmtp): child 15425 killed with signal 6 (core dumped) Hmm, yes, I think this an unnecessary RFC5322 -> RFC5321 address translation. Will look at making a fix tomorrow. Regards, Stephan. > > > #0 0x00007fea19977428 in __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 > resultvar = 0 > pid = 15425 > selftid = 15425 > #1 0x0...

Now that v2.0.0 is only waiting for people to report bugs (and me to figure out how to fix them), I've finally had time to start doing what I actually came here (Portugal Telecom/SAPO) to do. :) The idea is to have dbox and mdbox support saving attachments (or MIME parts in general) to separate files, which with some magic gives a possibility to do single instance attachment storage. Comments