search for: cfws

Displaying 8 results from an estimated 8 matches for "cfws".

Did you mean: cfgs
2020 Feb 18
1
Message-id parsing by sieve
...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 identifier for a message. and: Semantically, the angle bracket characters are not part of the msg-id; the msg-id is what i...
2018 Nov 30
2
Request: Pigeonhole - strip CWFS from message-id logs
Normally for a log line containing the contents of a Message-Id, it is logged like the following Nov 29 11:41:27 xxx dovecot[211]: lmtp(lee)<30167><XXXXX>: sieve: msgid=<xxxx at example.net>: stored mail into mailbox 'Notifications' However, if there is CFWS other than a space, it changes the format of the log line (potentially making the logs harder to process - eg via ?logcheck" rules) Nov 29 11:50:09 xxx dovecot[401]: lmtp(lee)<55724><XXXXX>: sieve: msgid=? <xxxx at example.com>: stored mail into mailbox ?Notifications'...
2018 Jan 31
2
lda: Warning: Failed to parse return-path header: Invalid character in localpart
...r/lib/dovecot/dovecot-lda -e -d '<username>' with a username recognized by your running dovecot installation. The header is 'Return-Path:', \r\n, two spaces, '<...>', \r\n According to rfc2822 folding rules, that should be valid - the Return-Path header allows CFWS at that location. The error message originates in lib-lda/mail-deliver.c in mail_deliver_get_return_address(), while the invalid character message seems to originate from one of several places in lib-lda/mail-deliver.c Ciao, Christian Authmann
2018 Jan 31
2
lda: Warning: Failed to parse return-path header: Invalid character in localpart
...t;' >> with a username recognized by your running dovecot installation. >> >> The header is 'Return-Path:', \r\n, two spaces, '<...>', \r\n >> >> According to rfc2822 folding rules, that should be valid - the >> Return-Path header allows CFWS at that location. >> >> >> The error message originates in lib-lda/mail-deliver.c in >> mail_deliver_get_return_address(), while the invalid character message >> seems to originate from one of several places in lib-lda/mail-deliver.c > > This is Dovecot v2.3.0 r...
2005 Sep 21
1
Another address-spec problem
...but A. N. Other <a.n.other at somewhere.org> is "obsolete", but should be supported by the server (no clients should do it). I think the relevant syntax is phrase = 1*word / obs-phrase word = atom / quoted-string obs-phrase = word *(word / "." / CFWS) and rfc822_parse_phrase() should be modified to cope with "obs-phrase". I'll have a go, but if Timo or anybody knows how to do it properly, that would be better! Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin,...
2018 Jan 31
0
lda: Warning: Failed to parse return-path header: Invalid character in localpart
...e -d '<username>' > with a username recognized by your running dovecot installation. > > The header is 'Return-Path:', \r\n, two spaces, '<...>', \r\n > > According to rfc2822 folding rules, that should be valid - the > Return-Path header allows CFWS at that location. > > > The error message originates in lib-lda/mail-deliver.c in > mail_deliver_get_return_address(), while the invalid character message > seems to originate from one of several places in lib-lda/mail-deliver.c This is Dovecot v2.3.0 right? Regards, Stephan.
2018 Jan 31
0
lda: Warning: Failed to parse return-path header: Invalid character in localpart
...h a username recognized by your running dovecot installation. >>> >>> The header is 'Return-Path:', \r\n, two spaces, '<...>', \r\n >>> >>> According to rfc2822 folding rules, that should be valid - the >>> Return-Path header allows CFWS at that location. >>> >>> >>> The error message originates in lib-lda/mail-deliver.c in >>> mail_deliver_get_return_address(), while the invalid character message >>> seems to originate from one of several places in lib-lda/mail-deliver.c >> >&g...
2019 Jan 03
0
Request: Pigeonhole - strip CWFS from message-id logs
...mally for a log line containing the contents of a Message-Id, it is logged like the following > > Nov 29 11:41:27 xxx dovecot[211]: lmtp(lee)<30167><XXXXX>: sieve: msgid=<xxxx at example.net>: stored mail into mailbox 'Notifications' > > However, if there is CFWS other than a space, it changes the format of the log line (potentially making the logs harder to process - eg via ?logcheck" rules) > > Nov 29 11:50:09 xxx dovecot[401]: lmtp(lee)<55724><XXXXX>: sieve: msgid=? <xxxx at example.com>: stored mail into mailbox ?Notifica...