Skip to content
This repository has been archived by the owner on Nov 25, 2022. It is now read-only.

Emails without Message-ID header are not seen #673

Open
themchn opened this issue Apr 30, 2019 · 6 comments
Open

Emails without Message-ID header are not seen #673

themchn opened this issue Apr 30, 2019 · 6 comments
Labels

Comments

@themchn
Copy link

themchn commented Apr 30, 2019

  • Platform: Android
  • Device: LG V10
  • Delta Chat Version: 0.301.1
  • Expected behavior: Receive all emails that arrive in inbox
  • Actual behavior: Certain messages are not visible in deltachat
  • Steps to reproduce the problem:

I'm trying to get an email from some software into deltachat but the client doesn't seem to acknowledge that the email even exists. The email does come into my inbox without any issue. If I manually send an email from a "normal" email client then deltachat received it without any issue. Below is a copy of the headers off an email deltachat does not "see".

Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mymailserver
    by mymailserver (Dovecot) with LMTP id Sq06F3WIyFzUWQAAxtmbUg
    for <[email protected]>; Tue, 30 Apr 2019 10:40:05 -0700
Received: from hostname (unknown [host ip address])
    by mymailserver (Postfix) with ESMTPSA id 4F53E2083D
    for <[email protected]>; Tue, 30 Apr 2019 10:40:05 -0700 (MST)
Date: Tue, 30 Apr 2019 10:40:05 -0700
From: [email protected]
To: [email protected]
Subject: Test Notification
Priority: normal
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

And this is a copy of the headers from an email I sent from the same address via a webmail client which deltachat can see without any issue.

Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mymailserver
    by mymailserver (Dovecot) with LMTP id a6gMMASlyFy4YwAAxtmbUg
    for <[email protected]>; Tue, 30 Apr 2019 12:41:56 -0700
Received: from mymailserver (localhost [127.0.0.1])
    by mymailserver (Postfix) with ESMTPA id B14772083D
    for <[email protected]>; Tue, 30 Apr 2019 12:41:56 -0700 (MST)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
    format=flowed
Content-Transfer-Encoding: 7bit
Date: Tue, 30 Apr 2019 12:41:56 -0700
From: [email protected]
To: [email protected]
Subject: test from roundcube
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/1.2.3

My suspicious is due to the lack of a Message-ID in the problem email as out of all the emails I have received, the common thing between them and this problem email is they all have a Message-ID.

@r10s
Copy link
Member

r10s commented Apr 30, 2019

i think missing Messages-ID headers have the potential to cause any kind of problems :)

@themchn
Copy link
Author

themchn commented Apr 30, 2019

Perhaps I should be filing a issue with the software that is responsible for sending the message then. Still, other email clients don't have an issue viewing the message.

@r10s
Copy link
Member

r10s commented Apr 30, 2019

normally, it should be displayed anyway in delta chat, iirc, delta chat creates a message-ID on receiving if it is missing. so, the issue of the not-appearing message may be different.

the message-id as such is a SHOULD in RFC 5322 iirc, however, i think a MUA should have very good reasons to leave it out.

@themchn
Copy link
Author

themchn commented Apr 30, 2019

Well I can confirm that the lack of a message-ID header is the problem. I've set sieve to add that header in this specific case and now it comes into deltachat without any issue.

@r10s
Copy link
Member

r10s commented May 1, 2019

@themchn thanks for checking!
i'll move this issue to the core, however. there seems not to be much android can do about this.

@r10s r10s transferred this issue from deltachat/deltachat-android May 1, 2019
@r10s r10s added the bug label May 1, 2019
@csb0730
Copy link
Contributor

csb0730 commented May 1, 2019

With issue #534 I did the same findings. See comment from Jan 23th.

I think label "bug" is appropriate here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants