similar to: Empty To: Header and message_address_parse

Hello, we are working in the migration from courier-imap to dovecot 2.2.10-4.el7_0.1.x86_64. Some emails that send a internal application show as sender "MISSING_MAILBOX at missing_domain", i use like email client Horde using dovecot like server. But if i open that email with Horde and courier-imap i can see the correct email sender. I think that the email of the sender is no correct

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 14 Oct 2015, grupo correo wrote: > we are working in the migration from courier-imap to dovecot > 2.2.10-4.el7_0.1.x86_64. > > Some emails that send a internal application show as sender > "MISSING_MAILBOX at missing_domain", i use like email client Horde using > dovecot like server. But if i open that email with

It seems that Dovecot gets confused when presented with a header like: From: someone at somewhere.org i.e. with leading whitespace and no "friendly name" This shows up as ""@MISSING_DOMAIN in clients, such as Pine, that believe what Dovecot tells them rather than parsing the headers themselves (e.g. Thunderbird). Here's a sample IMAP session: xyz FETCH 728 ENVELOPE

Hi all, I'm seeing Dovecot include the string "MISSING_DOMAIN" in fetch envelope requests when an mailbox's `addr-spec` part does not have a `domain` part. For example: > C: a022 uid fetch 40 (envelope rfc822.header) > S: * 5 FETCH (UID 40 ENVELOPE ("Sat, 15 Aug 2020 12:53:05 +1000" > "test {{name}}" (("Michael Gratton" NIL

Hi, This To field was not correct indexed by FTS. To: Yamada Taro <yamada at example.com>,=?UTF-8?B?dXNlcjJAZXhhbXBsZS5jb20=?= <user2 at example.com>, =?UTF-8?B?dXNlcjNAZXhhbXBsZS5jb20=?= <user3 at example.com>, user4 desu <user4 at example.com> --> Yamada Taro <yamada at example.com> , user2 at example.com And follow was correct indexed by FTS To: Yamada

I've had complaints from users about "MISSING_DOMAIN" in header fields and I've tracked it down to having "." in an unquoted display name. By my reading of RFC2822 (especially section 4.1) A N Other <a.n.other at somewhere.org> "A. N. Other" <a.n.other at somewhere.org> are legal, but A. N. Other <a.n.other at somewhere.org> is

Hi, I've been having an issue with the indexer giving me errors on mailbox in dovecot. I managed to narrow it down to a specific email in that mailbox. Various dovecot functions have issues with this email. The email itself is just spam. I can email it to you if you want to analyse it. I did run it through mbox-anonymize but its not clear to me that that would be of any use. Happy to email

Dovecot dies with signal 11 (segfault) when doing some commands with a specific message you'll find relevant information stored here: http://www.luria.ch/9e93676668e453b739ee3e085434e086/ the email: msg.anon.txt input rawlog: 20081001-120137-24371.in dovecot -n: dovecot-n.txt the gdb backtrace: bt.txt test system is running debian sarge, but same thing happens with debian etch (both x86)

You can also write to mailing list without subscribing. Anyway, I haven't written managesieve-login code, Ccing Stephan. On Thu, 2009-01-15 at 17:00 +0100, Wolfgang.Friebel at desy.de wrote: > Hi, > > sorry that do not write to the list, I am not subscribed yet. I have read > the november 2008 thread where managesieve-login does a segfault. As it > happened to me as well and

tonight dovecot 1.2beta4 crashed for the first time with an assertion failed. See attached log file. Around that time nobody was logged in into dovecot and there were no other mail deliveries going on. The mail in question should have been delivered to three recipients, one got the mail, the two others not. There is unfortunately no core dump file. I have attached the dovecot -n output as

I am building dovecot-2.0-pigeonhole-0.2.1 (dovecot-2.0.5, but that does not matter) with dovecot-config in place (in /usr/lib64/dovecot) on a 64bit Linux (RHEL5): ./configure --with-dovecot=/usr/lib64/dovecot The libs needed for several executables in libexec such as /usr/libexec/dovecot/managesieve-login are not installed in /usr/lib64 but in /usr/lib64/dovecot. Therefore the executable

In order to let users construct a sieve filter using a GUI I have taken websieve.pl from Alain Turbide (for use with Cyrus) and modified it to work with dovecot. In order to get it working quickly I have removed all the code I did not need (e.g. ldap support, password authentication) and coded Kerberos5 auth (via GSSAPI or SASL) in. I understand that this makes the work mostly useless to

Hi Timo, we are currently running dovecot 2.1.10 using mdbox storage. Sometimes we get requests from users to restore accidentally deleted mails. If the mails got deleted before a backup was made, such mails could of course not be restored from backup. One option to help users in this respect would be to use the lazy expunge plugin. On the other hand I have seen, that the deleted mails stay

I do have two questions related to the managesieve setup in dovecot 1) I did setup a global sieve filter, that is invoked if a user has no other sieve filter. If a user installs a sieve filter and activates it (PUTSCRIPT, SETACTIVE) then the sieve filter gets compiled (.sievec) and deliver does use it. If I want to deactivate the filter (SETACTIVE "") only the symlink (to the .sieve

Any word about this issue? Should I file a bug in an actual bug tracker or something? //Mike On Sat, 15 Aug, 2020 at 13:26, Michael Gratton <mike at vee.net> wrote: > Hi all, > > I'm seeing Dovecot include the string "MISSING_DOMAIN" in fetch > envelope requests when an mailbox's `addr-spec` part does not have a > `domain` part. > > For example:

On 31 Aug 2020, at 06:23, Michael Gratton <mike at vee.net> wrote: > Any word about this issue? Should I file a bug in an actual bug tracker or something? I don't think it's a bug? -- Eliot: We'll figure it out. We always do. Margo: When it's a test to cheat on. Not when we're stuck in some epic fantasy that likes to behead heroes halfway through season

After some investigation, it turns out it is non trivial to install dovecot-dbg on debian jessie. Sorry I can't investigate further. Jason Aki Tuomi wrote on 25/3/19 6:12 pm: > Can you install dovecot-dbg and try gdb again? > > Aki > > On 25.3.2019 3.20, Jason Lewis via dovecot wrote: >> Hi, >> >> I've been having an issue with the indexer giving me

Hi, I'm Tachibana. Additionally, I found below: dovecot/src/plugins/fts/fts-build-mail.c: 187 i_debug("@@@@@ befor address parse:%s",hdr->full_value); 188 189 addr = message_address_parse(pool_datastack_create(), 190 hdr->full_value, 191

On Mon, Jul 20, 2020 at 20:24:13 +0900, TACHIBANA Masashi wrote: > Hi, > > I'm Tachibana. > Additionally, I found below: > > dovecot/src/plugins/fts/fts-build-mail.c: > > 187 i_debug("@@@@@ befor address parse:%s",hdr->full_value); > 188 > 189 addr = message_address_parse(pool_datastack_create(), >

Hello we are doing regular backups of the mdbox mail folders using dsync -u username backup mdbox:/somedir/BACKUPS/username (still with version 2.1.10, but 2.2.5 is in testing phase) We do observe that the directory size in the BACKUPS directory is growing with respect to the original mail folders. I believe this is due to deleted mails not being purged in the backup. We are doing regular