Displaying 8 results from an estimated 8 matches similar to: "Emails with sender MISSING_MAILBOX@missing_domain"
2015 Oct 15
0
Emails with sender MISSING_MAILBOX@missing_domain
-----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
2005 Mar 22
2
Address with whitespace shows as ""@MISSING_DOMAIN
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
2020 Aug 31
0
Bug: Dovecot appending "MISSING_DOMAIN" to fetch envelope responses
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:
2020 Sep 01
1
Bug: Dovecot appending "MISSING_DOMAIN" to fetch envelope responses
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
2020 Aug 15
2
Bug: Dovecot appending "MISSING_DOMAIN" to fetch envelope responses
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
2009 Mar 30
1
Empty To: Header and message_address_parse
Using dovecot 1.2beta (but earlier versions should behave similarly) we
have a problem in conjunction with empty To: headers and the RT request
tracker.
RT sends mail out using Bcc: and no To: header at all. To make some
mailers happy one can configure to send a dummy To: header, which we do.
Our To header looks like:
To: "AdminCc of rt Ticket #123456":;
The message_address_parse
2005 Sep 21
1
Another address-spec problem
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
2005 Aug 01
1
Dovecot 1.0-test77 endless loop hang
Client: Bynari Insight Connector 3.0.5. (http://www.bynari.net/)
This is an IMAP-based plugin for Outlook that can also store Outlook
collaboration objects (calendar, tasks, notes, etc.) in IMAP messages on the
server side. It does not require special server extensions, and it was
actually (mostly) working with 1.0-stable.
Below is a rawlog dump showing what is going back and forth. After