AquaMail Forum
English - Android => How do I... => Topic started by: arf8 on February 04, 2017, 08:18:35 pm
-
I'm a little confused about the conversation mode feature of Aqua Mail.
I have tested all settings and none of them work as I was hoping after re-indexing each time.
For example I sent an email to a group of contacts, 4 of them responded to the email, however when the emails are grouped they are not grouped so all the replies are in one conversation. Instead i have 2 replies from one contact in a conversation by itself and i have other contacts who replied once in individual emails not part of that conversation.
I know unlike gmail this does not store emails the same way b/c it is not stored locally. However at least I expected all the emails with the same subject to show up in the conversation break out email.
Is there a way to fix this so all the replies with the same subject show up in one conversation
-
Most likely, the responses that didn't get linked up are:
- Either have different subjects
or
- Are missing the required (standard, official) message headers that link those responses to the original message. Setting those headers is the responsibility of the mail app(s) "on the other side". Some don't. The headers are References and In-Reply-To.
-
The subject is the same, I guess there is no fix? This is the one feature I was hoping works coming from Gmail.
I downloaded the Gmail App again and the same people responding to the email show up fine in the conversation view in the Gmail App.
Given the Gmail app handles this fine is this something which can be fixed in Aqua Mail?
-
I assure you a screenshot will not change what I posted. The way Aqua mail handles conversations is nothing like Gmail. It converges messages from the same sender into a conversation, which is great, but if you have multiple responses from different people to the same email they do not all roll up into one conversation. Each individuals response will roll up into their own conversation with the same subject as the original email.
Test it this way, send a group email out to at least 3 different contacts, have them respond to that email with at least 2 replies and you can see what I see.
I already uninstalled the gmail app and deleted those messages, but this can be repeated every time i send out a group email. :-\
-
The way Aqua mail handles conversations is nothing like Gmail.
It is different, but it is not nothing like: there are commonalities.
It converges messages from the same sender into a conversation, which is great, but if you have multiple responses from different people to the same email they do not all roll up into one conversation. Each individuals response will roll up into their own conversation with the same subject as the original email.
I can see only 2 cases when that can happen:
1. When the mail clients of your correspondents do not use standard headers "References" and "In-Reply-To" (as discussed in this thread) or
2. When they modify the subject in the way that is not known by Aquamail [Aquamail knows and disregards common prefixes and suffixes in different languages, such as Re:, Fwd:, (fwd), but that list might be missing something, especially if it is not in English). -- This would happen only if you have the option "Break a conversation on Subject change" enabled.
So, I suspect, Paris Geek asked you to post the screenshot to see if there is any subject modification. I actually thought of asking you if you have "Break a conversation on Subject change" enabled or disabled.
Personally, I'd suggest you looking at the headers of the messages in question, and checking if they have those two headers. (You can do this from the message view -> 3-dot menu -> View -> Show headers, or by check-marking an individual message in the message-list-view and 3-dot menu in the floating bar [if your configuration/version has that] ->"Show headers".)
Typically, those headers would be toward the bottom of the headers.
If those headers are absent, then the culprit is clear, as described previously here. (And then you can complain to your friends for having a poor taste in e-mail clients.)
If they are present, - we can try to help you figuring out why the messages are not linked into a single conversation in Aquamail.
Test it this way, send a group email out to at least 3 different contacts, have them respond to that email with at least 2 replies and you can see what I see.
I am doing this frequently, and they are all in one thread (conversation) in Aquamail. I've just had that yesterday, albeit with only 2 correspondents.
-
@Paris Geek: no problem.
@arf8: Just in case, one more thought I forgot to mention: By any chance, are your messages in different folders (e.g. filtered by the server filters), as opposed to being all in one folder (e.g. Inbox)?
Aquamail doesn't combine message into a conversation across the folders (except when enabled by the option "Across folders", and then only between the folder you are in and "Sent" folder).
-
I can see only 2 cases when that can happen:
1. When the mail clients of your correspondents do not use standard headers "References" and "In-Reply-To" (as discussed in this thread) or
2. When they modify the subject in the way that is not known by Aquamail [Aquamail knows and disregards common prefixes and suffixes in different languages, such as Re:, Fwd:, (fwd), but that list might be missing something, especially if it is not in English). -- This would happen only if you have the option "Break a conversation on Subject change" enabled.
The subject is not modified in any manner with suffixes by their clients, this I just confirmed by looking at the emails again. In fact in Gmail app it has never had any problems with conversation view with these same group of people I have corresponded with for over 10 years. I confirmed by looking in my Trash and they are all grouped properly as one would expect. I also just checked Aqua mail and looked in the Trash folder and the subject is the same for all the responses to that email thread.
So, I suspect, Paris Geek asked you to post the screenshot to see if there is any subject modification. I actually thought of asking you if you have "Break a conversation on Subject change" enabled or disabled.
The options I have set in Aqua is "Combine on sender + subject" although I tried all the other options it made no difference.
Personally, I'd suggest you looking at the headers of the messages in question, and checking if they have those two headers. (You can do this from the message view -> 3-dot menu -> View -> Show headers, or by check-marking an individual message in the message-list-view and 3-dot menu in the floating bar [if your configuration/version has that] ->"Show headers".)
Typically, those headers would be toward the bottom of the headers.
If those headers are absent, then the culprit is clear, as described previously here. (And then you can complain to your friends for having a poor taste in e-mail clients.)
If they are present, - we can try to help you figuring out why the messages are not linked into a single conversation in Aquamail.
I checked the headers for individual emails in question and I have attached them here, I edited the emails and names but nothing else has been modified. They all have a "In-reply-to" header and reference although the header sizes are different.
I'm hoping this helps solve the mystery. Two of the 3 have this in the header, but again the same emails are grouped properly in Gmail.
"In-Reply-To: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>"
Email 1
Delivered-To: a@gmail.com
Received: by 10.103.8.69 with SMTP id 66csp1429740vsi; Sun, 5 Feb 2017
10:20:07 -0800 (PST)
X-Received: by 10.36.64.70 with SMTP id n67mr4450549ita.21.1486318807587; Sun,
05 Feb 2017 10:20:07 -0800 (PST)
Return-Path: <p@san.rr.com>
Received: from cdptpa-oedge-vip.email.rr.com
(cdptpa-outbound-snat.email.rr.com. [107.14.166.228]) by mx.google.com with
ESMTPS id h130si7578758ioa.188.2017.02.05.10.20.07 for <a@gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Feb
2017 10:20:07 -0800 (PST)
Received-SPF: pass (google.com: domain of p@san.rr.com designates
107.14.166.228 as permitted sender) client-ip=107.14.166.228;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of
p@san.rr.com designates 107.14.166.228 as permitted sender)
smtp.mailfrom=p@san.rr.com
Return-Path: <p@san.rr.com>
Received: from [76.176.67.211] ([76.176.67.211:51887] helo=john-pc) by
cdptpa-omsmta01 (envelope-from <p@san.rr.com>) (ecelerity
3.6.9.48312 r(Core:3.6.9.0)) with ESMTP id 34/63-03423-5DC67985; Sun, 05 Feb
2017 18:20:06 +0000
Content-Type: multipart/alternative; boundary=----------ldkabf3DWpXUECiIbjrkRu
To: "A Y" <h@gmail.com>
Cc: "D L" <rr@aol.com>, "A Jet" <a@gmail.com>,
"J H" <j@hotmail.com>
Subject: Re: RMZ
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
<op.yu61x5jinwub7b@john-pc>
<CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
Date: Sun, 05 Feb 2017 10:21:04 -0800
MIME-Version: 1.0
From: aztec <p@san.rr.com>
Organization: aztec
Message-ID: <op.yu689etmnwub7b@john-pc>
In-Reply-To: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
User-Agent: Opera Mail/1.0 (Win32)
X-RR-Connecting-IP: 107.14.168.6:25
Email2
Delivered-To: a@gmail.com
Received: by 10.103.8.69 with SMTP id 66csp1402412vsi; Sun, 5 Feb 2017
08:29:22 -0800 (PST)
X-Received: by 10.107.84.2 with SMTP id i2mr4893918iob.176.1486312162827; Sun,
05 Feb 2017 08:29:22 -0800 (PST)
Return-Path: <j@hotmail.com>
Received: from SNT004-OMC1S39.hotmail.com (snt004-omc1s39.hotmail.com.
[65.54.61.76]) by mx.google.com with ESMTPS id
z186si2870297itd.89.2017.02.05.08.29.22 for <a@gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 05 Feb 2017
08:29:22 -0800 (PST)
Received-SPF: pass (google.com: domain of j@hotmail.com designates
65.54.61.76 as permitted sender) client-ip=65.54.61.76;
Authentication-Results: mx.google.com; dkim=pass header.i=@hotmail.com;
spf=pass (google.com: domain of j@hotmail.com designates 65.54.61.76
as permitted sender) smtp.mailfrom=j@hotmail.com; dmarc=pass (p=NONE
sp=NONE dis=NONE) header.from=hotmail.com
Received: from NAM02-SN1-obe.outbound.protection.outlook.com ([65.55.90.8]) by
SNT004-OMC1S39.hotmail.com over TLS secured channel with Microsoft
SMTPSVC(7.5.7601.23008); Sun, 5 Feb 2017 08:29:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com;
s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
bh=XqN/iNIZ6CPITL9Ec060TOxAiSTOq9dkNTrPsfqw/CA=;
b=R1hXTx7bKnRHTlqbPAwflffUJn5qpnJLOWRl87rhg0Rmv+46p2YImIj8iozEXsZP2ssWtI8z8udg3VurlH6LTHvhwjuxDoqjsqZnbXVUrFsQDEwqvpQH5S6eieFWey2i5zAv2VmLLTAMyy79xPGen3munWVCzKtFPPvri37GejLLp4pUEVrCW5KmRhK21SL3qrBlQqbCam70N4DFCILeOs82rrXHFttjrliu7BNr6OVd6YoXLB02I/wyAhLgY9rKlFv6qUkNjoHAbGweB/Y51s7Ga09+CDOEQYNJT2bwITdqpUW8rOsUKjN5JKf2MkCQ8/FHen3kMQxkwtjzJmabzw==
Received: from SN1NAM02FT002.eop-nam02.prod.protection.outlook.com
(10.152.72.56) by SN1NAM02HT094.eop-nam02.prod.protection.outlook.com
(10.152.73.250) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.7; Sun, 5 Feb
2017 16:29:21 +0000
Received: from MWHPR06MB2672.namprd06.prod.outlook.com (10.152.72.53) by
SN1NAM02FT002.mail.protection.outlook.com (10.152.72.94) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
15.1.888.7 via Frontend Transport; Sun, 5 Feb 2017 16:29:21 +0000
Received: from MWHPR06MB2672.namprd06.prod.outlook.com ([10.168.209.14]) by
MWHPR06MB2672.namprd06.prod.outlook.com ([10.168.209.14]) with mapi id
15.01.0888.022; Sun, 5 Feb 2017 16:29:21 +0000
From: J H <j@hotmail.com>
To: A Y <h@gmail.com>, J R
<p@san.rr.com>
CC: D L <rr@aol.com>, A Jet <a@gmail.com>
Subject: Re: RMZ
Thread-Topic: RMZ
Thread-Index: AQHSf4L8p0xwnOKgE0qb8Xbx1AMmM6FajhGAgAAJHwCAAAOf8A==
Date: Sun, 5 Feb 2017 16:29:21 +0000
Message-ID: <MWHPR06MB26721DA0CF059D605244CDAEAC410@MWHPR06MB2672.namprd06.prod.outlook.com>
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
<op.yu61x5jinwub7b@john-pc>,<CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
In-Reply-To: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: aol.com; dkim=none (message not signed)
header.d=none;aol.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:1AF289F16CE65199C698090C8EAF54ADC041042AEA08D915BF6DD0573089C9C9;UpperCasedChecksum:70562DAF3E81E0DE251D3F7F34C43E01F15B8760A811D9D3D9B15090FF86BFC6;SizeAsReceived:7994;Count:40
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [XeksETzQ0wFwaD17tZKUTQaquT/N1c6g]
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1;SN1NAM02HT094;5:JvfJ3D64PAY/3TuGp7Z5PkdihKa+IsRVOUGwOyW8Q+2KuWfvmYTaBv/U91URs1X++9wNk4GpN8T5XrDkrK1XnCuKDl+lpdegMuaYimPV7Jm2c8m/bXYIVXuIfvKvOC1EDNa+rbnEpjKa26gKqaDKdw==;24:IulYP3oDyZb5J258KKy5wkHmWSEsuU7qm9obYiUw47W+JtopA/d3BOmNgZ/Y1dgfX8eH2SWf9eTJd0yDaBCzhpEzj6CG9pef5e6YrwwJuZw=;7:fuPEy9kc2ZC8MzgFtOMQ5da7V4Z6bfcTRB0CDVD0PrcGhebIfuqMKMAk9RlsIqN48f0sz7Hr1x6jgCRVA/4F6XHfyPa9r6qLtnKBiJvLCaPH90M+43EFD6Nka522u0GOLqBVNdcZD/j5KtmiyUDHtA4wqcRrhVec5h1KggI5LjISbcI4RHYhOJf5AzSFS67Y3+eP23Kk1ep3wfgnsPQlb6ujS3Gp/NB2N2v9yHkyCwAIAAhVUuC/MDHG4pOJCdzQqnbS4eZk/ydxLdP8RXbMwLCGb3G5EfawZR/qEAjgpVN0My/F95MFttvCJcU2c4iUm3Z8OngT40GTPSMgB4u2KyGBBsW+Pq5W365qh4iumFEKxkXGy1XCzD0k/Yk9qF3eeyvAfgtxkbdbLDNMSmfXJk0gt/XzwfsTQ7qM+KJoqDB0PDzE9ifWfgIjJOlANvFWP1rZv80OxvWm11ENU2F7zcbPeiYCC1sqkdHiXkCIYLTAuwPCMmQ89pxPI+PBZFWdN3Ctw46PSnT9vY4GgtWOLQ==
x-forefront-antispam-report: EFV:NLI;SFV:NSPM;SFS:(10019020)(98900005);DIR:OUT;SFP:1102;SCL:1;SRVR:SN1NAM02HT094;H:MWHPR06MB2672.namprd06.prod.outlook.com;FPR:;SPF:None;LANG:en;
x-ms-office365-filtering-correlation-id: 6f5a9416-f2cf-4fa3-9343-08d44de423bd
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(5061506426)(5061507331)(1603103135)(1601125107)(1603101373)(1701031045);SRVR:SN1NAM02HT094;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(444111334)(432015086)(82015046);SRVR:SN1NAM02HT094;BCL:0;PCL:0;RULEID:;SRVR:SN1NAM02HT094;
x-forefront-prvs: 0209425D0A
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
boundary="_000_MWHPR06MB26721DA0CF059D605244CDAEAC410MWHPR06MB2672namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Feb 2017 16:29:21.1739 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM02HT094
Return-Path: j@hotmail.com
X-OriginalArrivalTime: 05 Feb 2017 16:29:22.0304 (UTC)
FILETIME=[01D6C000:01D27FCD]
Email3
Delivered-To: a@gmail.com
Received: by 10.103.8.69 with SMTP id 66csp1399089vsi; Sun, 5 Feb 2017
08:15:47 -0800 (PST)
X-Received: by 10.28.136.13 with SMTP id k13mr5602129wmd.94.1486311347561;
Sun, 05 Feb 2017 08:15:47 -0800 (PST)
Return-Path: <h@gmail.com>
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com.
[2a00:1450:400c:c09::22f]) by mx.google.com with ESMTPS id
v21si30189047wra.330.2017.02.05.08.15.47 for <a@gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 05 Feb
2017 08:15:47 -0800 (PST)
Received-SPF: pass (google.com: domain of h@gmail.com designates
2a00:1450:400c:c09::22f as permitted sender)
client-ip=2a00:1450:400c:c09::22f;
Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass
(google.com: domain of h@gmail.com designates
2a00:1450:400c:c09::22f as permitted sender)
smtp.mailfrom=h@gmail.com; dmarc=pass (p=NONE sp=NONE dis=NONE)
header.from=gmail.com
Received: by mail-wm0-x22f.google.com with SMTP id v77so110516wmv.0 for
<a@gmail.com>; Sun, 05 Feb 2017 08:15:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc;
bh=ZlFSM7VOapR+/tLHoyuJXHfXbayvBd2WrW9TwizbZbQ=;
b=utJuWwhzq3b9XGOfXG89rWq/bOSWgHQqfMDy1AKs239L6Q4ve8qK9I9O7EnkL1+BSL
B0m+ghkmF1v6sZX7KXCREgWCbD+9t1FP0dqTlPkmQDvsX/V1u6se9MGVia9tfhX6cYq7
PaOU+jNHg+nWWGJ0SkBknxdUSvy+mJaJ5kOCVJfNLBPZiMB6EYFCYbL9D8udNCWvb0TU
Beh77NiViLugQ9kvmmS+9Qjz+K0UAgPIoY4lz0IfKLePQvx9jedJQKjBK4d22aWo2c17
RUufysbG0mLGvLbYKxdPUyOUQrsS5g6vX+T+XtZGSs2V/lgjBpbK7YUrBXcgjQxby22J s+Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net;
s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc; bh=ZlFSM7VOapR+/tLHoyuJXHfXbayvBd2WrW9TwizbZbQ=;
b=cL6d1YH9GrlvlVnDv5Tw0PjEDP3LEY+EzMXa/NpjRXN+e9Yx2REYWqMqcES3CeMiwz
PotSQt9TmQnEfZOd83/Kp+096U36GDJAZtbXz2qutcimpqfReO8UGxRdnxJKnm6M0xmc
dV7Z5l70MTmdBIQKz/Frs0/xdR1sqFn4bVS8vWO+GDjrutsZ7Qv4BEBGSUvwkT5JY/zi
gGQmLxhjLze3C+cTV+uT8xNLM4l9WNbKBHcXr76OWNOKGzRPVfPhYW0FUFljmlGhkG8V
s7jw6BxCSQvhmRJasrR1GDOqL7wveLXICOB/LXr41+UrlIJvkp7seKQaqnR2eNyvi+HR CQMA==
X-Gm-Message-State: AMke39mfFP+WNka3kmL6kmNraByGbhNcol5YYXl8hTyvDxn3hXACsaRz2iVENjhsXCJ6fJQwJlCOtEv2mWwSvQ==
X-Received: by 10.28.153.196 with SMTP id b187mr5111472wme.53.1486311347073;
Sun, 05 Feb 2017 08:15:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.91.6 with HTTP; Sun, 5 Feb 2017 08:15:46 -0800 (PST)
Received: by 10.28.91.6 with HTTP; Sun, 5 Feb 2017 08:15:46 -0800 (PST)
In-Reply-To: <op.yu61x5jinwub7b@john-pc>
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
<op.yu61x5jinwub7b@john-pc>
From: A Y <h@gmail.com>
Date: Mon, 6 Feb 2017 00:15:46 +0800
Message-ID: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
Subject: Re: RMZ
To: J R <p@san.rr.com>
Cc: D L <rr@aol.com>, A Jet <a@gmail.com>, JIM
HOULIHAN <j@hotmail.com>
Content-Type: multipart/alternative; boundary=001a114b429ede38750547cad3e0
-
@Paris Geek: no problem.
@arf8: Just in case, one more thought I forgot to mention: By any chance, are your messages in different folders (e.g. filtered by the server filters), as opposed to being all in one folder (e.g. Inbox)?
Aquamail doesn't combine message into a conversation across the folders (except when enabled by the option "Across folders", and then only between the folder you are in and "Sent" folder).
All in the same folder and I only have one email account setup in Aqua mail for now. Until the notifications from different contacts is added in the future.
-
So far, I don't see anything that should prevent these three messages to be grouped in one conversation in Aquamail, as long as "Settings -> Conversations -> Conversation combining" is enabled.
Let's try a test:
1. From the account/folder list view (the most "top" view) -> 3-dot menu -> About.
Approximately in the middle of the screen, does it say
isThreadSchema = true
isLinkedSchema = true
?
2. Please go to 3-dot menu -> "Settings -> Conversations -> Conversation combining". If it is check-marked, uncheck. (If the setting was not check-marked, just skip this step.) then "Reindex conversations" (two items below that) if it will allow you to do that (I suspect that option will not be available at this point).
3. Then, go back there again, and enable that setting it, and "Reindex conversations" (Very important!).
Then, go to the folder and look at the messages in question.
If this doesn't help, the next step would probably to save those message in .eml format and send them to Kostya via e-mail, or at least the headers.
Actually, prior sending them to Kostya, I'd suggest one more quick test that might help Kostya in investigating this issue: enable "Settings -> Conversations -> Across folders".
After that disable and enable back "Conversation combining", and "Reindex conversations".
This should bring the original message in "Sent" to the conversation. Check if all 3 messages (plus you original one from Sent) are in one conversation.
-
So far, I don't see anything that should prevent these three messages to be grouped in one conversation in Aquamail, as long as "Settings -> Conversations -> Conversation combining" is enabled.
thanks for looking into this for me.
Let's try a test:
1. From the account/folder list view (the most "top" view) -> 3-dot menu -> About.
Approximately in the middle of the screen, does it say
isThreadSchema = true
isLinkedSchema = true
?
Yes it is true for both
2. Please go to 3-dot menu -> "Settings -> Conversations -> Conversation combining". If it is check-marked, uncheck. (If the setting was not check-marked, just skip this step.) then "Reindex conversations" (two items below that) if it will allow you to do that (I suspect that option will not be available at this point).
Correct once the conversation combining is unchecked reindex is not possible.
3. Then, go back there again, and enable that setting it, and "Reindex conversations" (Very important!).
Then, go to the folder and look at the messages in question.
If this doesn't help, the next step would probably to save those message in .eml format and send them to Kostya via e-mail, or at least the headers.
I've posted the headers above so hopefully he can chime in once he sees this.
Actually, prior sending them to Kostya, I'd suggest one more quick test that might help Kostya in investigating this issue: enable "Settings -> Conversations -> Across folders".
After that disable and enable back "Conversation combining", and "Reindex conversations".
This should bring the original message in "Sent" to the conversation. Check if all 3 messages (plus you original one from Sent) are in one conversation.
Done, no difference same issue, i also found this happens on responses from ebay messages too when the responses which have the same subject are not grouped together
-
... i also found this happens on responses from ebay messages too when the responses which have the same subject are not grouped together
That is likely a different issue. Those responses might not have the headers in question. (You can check those yourself)
Here is what seems to be a well-defined case, so, let's not cloud it up.
-
Agree, was just pointing out this is not related to just these contacts but i don't want to speculate without looking at the header as pointed out.
Regarding the header information what is the most critical element, "in-reply-to" or something else which should match or be present?
-
Regarding the header information what is the most critical element, "in-reply-to" or something else which should match or be present?
AFAIK, matching numbers (message-id's) between messages in any of these three headers: "In-reply-to:", "References:", "Message-ID:" is sufficient for pulling messages in the same conversation.
-
Ok thanks, i'll have to look at other email chains tonight to see what i can find
-
@Kostya Vasilyev, any information you need to help fix this problem let me know.
Thanks
-
@Paris Geek: no problem.
@arf8: Just in case, one more thought I forgot to mention: By any chance, are your messages in different folders (e.g. filtered by the server filters), as opposed to being all in one folder (e.g. Inbox)?
Aquamail doesn't combine message into a conversation across the folders (except when enabled by the option "Across folders", and then only between the folder you are in and "Sent" folder).
All in the same folder and I only have one email account setup in Aqua mail for now. Until the notifications from different contacts is added in the future.
First I admit to not adsorbing all the detail in this thread (time constraints). That said, Gmail is my primary with a fairly heavy daily message flow and an extensive folder hierarchy. My solution to AquaMail's grouping methodology is to regularly sync the All Mail and Sent folders (past 90 days; unlimited messages). This results in *most* related messages being grouping into logical conversations *most* of the time yielding high consistency with native GMail groupings. The 90 day limit (which can be temporarily overridden) keeps the local database size in check. On occasion I still need to fall back to one of Gmail's native interfaces to deal with older items where accurate conversational alignment is important. A reasonable compromise given the other benefits AquaMail brings to the table.
-
Hi Davey,
That is a great suggestion, I'm hoping this issue can be fixed where the groupings work as advertised. Hoping with the header information posted this is just a minor bug that can be resolved. Otherwise like you I will have to use this work around. I really don't like having multiple email clients on the phone b/c they poll and drain the battery given the number of messages i receive daily.
Thanks
-
Hi Davey,
That is a great suggestion, I'm hoping this issue can be fixed where the groupings work as advertised. Hoping with the header information posted this is just a minor bug that can be resolved. Otherwise like you I will have to use this work around. I really don't like having multiple email clients on the phone b/c they poll and drain the battery given the number of messages i receive daily.
Thanks
You can mitigate the drain by limiting what gets loaded during routine mail checks. You'll probably need to check/adjust network settings both at the account and global level. There's obviously a trade-off in convenience and overall efficiency depending on workflow, connection type, etc. The balance (settings) I use affords long battery life without too much inconvenience. Occasionally I have to tap to fully load an especially long message or large file attachment. No biggie. Often I can act on a message w/o having to download the full content.
Good luck!
-
thanks, i have one of my clients set to sync once a day which helps but having 3 clients just does not make sense. The second one is there just to interface with Gear S3 which uses native client. Would be nice to get this fixed in Aqua mail for sure.
-
thanks, i have one of my clients set to sync once a day which helps but having 3 clients just does not make sense. The second one is there just to interface with Gear S3 which uses native client. Would be nice to get this fixed in Aqua mail for sure.
Probably not. This topic has been broadly discussed in the forums with little change. I understand the developers concerns which which must be balanced against customer satisfaction. Seems most are happy (or at least tolerant) of the current grouping methodology. Others (self) have found satisfactory work arounds. I have 4 clients that regularly sync as previously described.
-
Paris Geek, in response to your question:
The three types of unfulfilled requests about conversation grouping I've seen on this forum are:
1. Grouping by Subject only.
2. Grouping by Sender only.
3. Grouping as in GMail.
For the reference, AFAIK, the presently available methods are: Message-ID-related headers (with or without the same subject, as configured) and optionally, by Sender+Subject (even if the References and Reply-to headers are absent).
I am not sure if #1, or maybe #1+#2 covers all the cases in #3, or Gmail does something else, - e.g., body analysis (matching the quoted body content between messages).
PS. Just in case: In case of arf8, there might be a bug ... At least, I don't see why these messages with all legitimate References and Reply-to headers would not be combined in one conversation. This requires Kostya's attention.
-
@StR,
thanks for the post, I believe this is a bug based on the header information from these senders and messages received.
Cheers
-
@Davey, I'm not sure to understand conversation grouping request. What's the need and the suggestion?
Thanks
I see @StR and @arf8 have already weighed in; not much more I can add to the conversation other than personal experience. Syncing All Mail resolved 90-95% of the message combining issues for me. It doesn't always match Gmail's threads (which sometimes gets it wrong too) but rarely do I have to hunt down an orphaned message. When it does happen a resync of All Mail often fixes things up...at least to my satisfaction. An awakward solution for some, especially if other steps are not taken to manage data consumption and local database size. But it works (mostly).
-
@arf - I only now saw that you posted complete message headers for all the messages involved. Will take a look (by uploading them to one of my accounts and checking what happens).
Yes, the References and In-Reply-To are present, the subject is the same, it should have worked.
I just have one question, is there really a blank line here?
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
***** THIS BLANK LINE HERE IF YOU GO BACK TO YOUR POST ***
<op.yu61x5jinwub7b@john-pc>,<CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
-
@arf8 - and these are all incoming messages, correct?
-
@art8
Sorry can't reproduce. We can try to think of some way to diagnose this further, but so far, nothing.
BTW, I had to fix a bunch of headers compared to what you posted -- remove the blank line in the middle of one header (the one I asked about above), and fix the indentation on others. Before I did, these messages wouldn't open right in Thunderbird or Fastmail web mail.
I'm not sure if your messages were like that to begin with (meaning malformed) or they got changed when you copied / pasted.
What I ended up with it below:
Message 1, the original was *last* in your post:
In-Reply-To: <op.yu61x5jinwub7b@john-pc>
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
<op.yu61x5jinwub7b@john-pc>
From: A Y <h@gmail.com>
Date: Mon, 6 Feb 2017 00:15:46 +0800
Message-ID: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
Subject: Re: RMZ
To: J R <p@san.rr.com>
Cc: D L <rr@aol.com>, A Jet <a@gmail.com>, JIM
HOULIHAN <j@hotmail.com>
Content-Type: text/plain
Message 1
Message 2:
From: J H <j@hotmail.com>
To: A Y <h@gmail.com>, J R
<p@san.rr.com>
CC: D L <rr@aol.com>, A Jet <a@gmail.com>
Subject: Re: RMZ
Thread-Topic: RMZ
Thread-Index: AQHSf4L8p0xwnOKgE0qb8Xbx1AMmM6FajhGAgAAJHwCAAAOf8A==
Date: Sun, 5 Feb 2017 16:29:21 +0000
Message-ID: <MWHPR06MB26721DA0CF059D605244CDAEAC410@MWHPR06MB2672.namprd06.prod.outlook.com>
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
<op.yu61x5jinwub7b@john-pc>,<CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
In-Reply-To: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain
MIME-Version: 1.0
Message 2
Message 3:
Content-Type: text/plain
To: "A Y" <h@gmail.com>
Cc: "D L" <rr@aol.com>, "A Jet" <a@gmail.com>,
"J H" <j@hotmail.com>
Subject: Re: RMZ
References: <58964aca.0faa370a.645b7.50c3SMTPIN_ADDED_MISSING@mx.google.com>
<CAM4SxfgGgTFBnfy6dQ6MjJFB=Cg5o62owAz+7TaVydeUwRXL0w@mail.gmail.com>
<op.yu61x5jinwub7b@john-pc>
<CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
Date: Sun, 05 Feb 2017 10:21:04 -0800
MIME-Version: 1.0
From: aztec <p@san.rr.com>
Organization: aztec
Message-ID: <op.yu689etmnwub7b@john-pc>
In-Reply-To: <CAM4Sxfj+NZjkO9sB=2a6dZN4Kgs3FF9-Q+7f+XyMYGkw3N9kXg@mail.gmail.com>
User-Agent: Opera Mail/1.0 (Win32)
Message 3
-
Thanks for looking into this,
Yes these are all incoming messages.
That must have been from the editor Notepad++ when i copied and paste. I have the original messages if you provide me with your email I can send them to you unedited to help further troubleshoot this.
What email would you like me to forward them to you direct?
Thanks
-
Thanks for looking into this,
Yes these are all incoming messages.
That must have been from the editor Notepad++ when i copied and paste. I have the original messages if you provide me with your email I can send them to you unedited to help further troubleshoot this.
What email would you like me to forward them to you direct?
Thanks
You can send the original messages (please as attachments /. eml files) to support / at sign / aqua-mail / dot com .
-
sent
-
@arf8
Sorry can't find it, even searched by your forum profile's email (I can see it others can't).
If it's not too much trouble, can you re-send to kmansoft / gmail / dot com?
-
Sending it now to kmansoft / gmail / dot com
Thanks
-
For those wondering this is what it looks like. Data is being sent to Kostya
-
It seems to have gotten worse with v1.8, did something change in the code which handles the header information?
Surely there has to be a way to make it more robust like the Gmail app which handles header information or lack there of better.
Asking people to change their email clients is not feasible. I can rarely get a group conversation which is not broken up by individual contacts with multiple emails in v1.8.
-
There is a problem, it is documents and Kostya is well aware of it.
If you are unaware of the issue read this thread. As to if any of this was changed in 1.8 or not is TBD although the release notes makes no mention, it does not mean tweaks under the hood will be listed.
This issue is not going to fix itself or get better with time sadly and makes the conversation mode worthless.
-
There is a problem, it is documents and Kostya is well aware of it.
If you are unaware of the issue read this thread. As to if any of this was changed in 1.8 or not is TBD although the release notes makes no mention, it does not mean tweaks under the hood will be listed.
This issue is not going to fix itself or get better with time sadly and makes the conversation mode worthless.
Daily user; have not noticed any difference in conversation grouping/integrity with v1.8. If Aqua isn't serving your needs might consider a different mail client. Gmail perhaps.
-
I jumped from Gmail to Aqua because of the ability to change the colors. I have high hopes this will get resolved perhaps.
-
Re: It seems to have gotten worse with v1.8, did something change in the code which handles the header information?
No, nothing has changed in message header code or conversation code in 1.8.
-
thanks for the confirmation. It seems like more and more contacts are using clients which don't follow the header rules. Quite annoying.
-
Kostya, sorry, just in case it went off your radar:
Above in this thread, @arf8 sent you the messages (headers) that visibly had the correct headers needed for thread detection. Were you able to figure out the issue with those?
(Previously, you had a concern that the lines could have been broken up, but that could be a function of Copy-N-Paste).
I believe that might be an important key to @arf8's threads problem resolution.
-
I'll let Kostya chime in but the short answer is different email clients manage and handle header information differently. I have contacts who use hotmail, gmail, AOL, yahoo to name a few and unlike the Gmail app which can use the header information and possibly parse the message to figure out which emails are part of what conversation, Aqua mail can not do this.
So with Aqua mail you have to just expect the conversation mode feature will not work and I'm finding this to be a headache replying to emails, not knowing which one is the latest and who replied to who unless I open all the different grouped individual conversations. Really was hoping this is something that could be fixed in Aqua but it does not sound like it.
-
... unlike the Gmail app which can use the header information and possibly parse the message to figure out which emails are part of what conversation, Aqua mail can not do this.
"Any sufficiently advanced technology is indistinguishable from magic." Arthur C Clarke
There is no real magic behind thread detection in Aquamail, just a well defined logic (while I suspect GMail server might be using what is called "fuzzy logic", but my comment is not about that).
There are two issues that it looks like are being mixed up, and that's not helping anybody. I thought I explained this in the earlier part of the thread, but maybe it was not clear.
(A)
One: there is a well defined case where Aquamail does not group messages to a thread (but Gmail does/might): The same subject, different senders on the other end, and no "References" or "Reply-To" headers.
And if one disabled the option responsible for this: Aquamail will not group messages that have: the same subject, the same sender, but no "References" or "Reply-To" headers.
(Note, that everything I've seen from Davey126 and everybody else in these forums complaining about thread grouping falls into this category [since the initial quirks have been fixed more than a year ago]. So, your case here is quite likely unique.)
(B)
A very different issue that seems to be the case in the example you made above in this thread ( https://www.aqua-mail.com/forum/index.php?topic=5361.msg31829#msg31829 ) is when the headers in question are present. According to Aquamail's logic those messages should have been grouped in one thread/conversation. And that's where I suspect the culprit of most of your problems might be.
I am actually very curious to hear the result of Kostya's analysis.
So far, I expect it could be one of the following:
1. Something in your server breaks/modifies the headers of the incoming messages. But, AFAIR, you are using Gmail account (right?). In that case, I don't expect such a problem.
2. There is some "zero-day" bug in Aquamail that gets triggered in your case. -- This seems to be very unlikely, but that makes it even more important to find and fix.
3. Some type of corruption of the database.
4. Something totally weird in the device/configuration ...
So with Aqua mail you have to just expect the conversation mode feature will not work ...
Look, I understand that you are frustrated because something does not work for you. And even if it would've worked for everybody else in the world, what ultimately matters to you is that it does not work for you. But if you want the issue to be resolved, the hysteria about the issue does not help.
I know that you provided the information requested. So, let's have some patience, while awaiting the outcome of Kostya's investigation.
-
First of all, the only "hysteria" and "confusion" is caused by your own response! so relax...
As i stated this is something Kostya and I have discussed based on the data analysis, so rather than jumping to a conclusion about zero-day and what ever lavish conclusion you can come up with, why don't you take my response for what it is and except the fact different email clients handle header information differently.
There is nothing wrong on my end or theirs. It is simply the way Aqua mail handles messages based on the header information. Gmail and other apps use a logic beyond just header information to group messages in a conversation view.
There is no confusion or ambiguity and there is only one issue. Rather than to confuse yourself and everyone else, take a step back and realize this is not going to be resolved anytime soon and it is the nature of using Aqua Mail unless the developers decide to make a change which has been pointed out likely not.
-
There is nothing unknown here as I previously stated. You are simply repeating what I have stated.
Contacts with different email clients whether it is mobile or desktop handle message headers differently.
Gmail has never incorrectly grouped messages, not once in my 20+ years using Gmail! Not here to start a pissing match about gmail, but making claims like that you should be very cautious!
I have contacts who use just about every email client you can think of and they are not grouped correctly in Aqua conversation view. There is no ambiguity or confusion how these messages should be grouped and they simply are not grouped correctly.
This a NOT a Aqua bug, it is the inherent way Aqua relies on simple header information to group messages. Could this be fixed, sure if the developers want to pursue this, and it has been made clear it is not going to be fixed!
I simply asked if something had changed in v1.8 to affect conversation mode b/c it only got worse, and it was answered already by Kostya.
-
There is nothing unknown here as I previously stated. You are simply repeating what I have stated.
Contacts with different email clients whether it is mobile or desktop handle message headers differently.
Gmail has never incorrectly grouped messages, not once in my 20+ years using Gmail! Not here to start a pissing match about gmail, but making claims like that you should be very cautious!
I have contacts who use just about every email client you can think of and they are not grouped correctly in Aqua conversation view. There is no ambiguity or confusion how these messages should be grouped and they simply are not grouped correctly.
This a NOT a Aqua bug, it is the inherent way Aqua relies on simple header information to group messages. Could this be fixed, sure if the developers want to pursue this, and it has been made clear it is not going to be fixed!
I simply asked if something had changed in v1.8 to affect conversation mode b/c it only got worse, and it was answered already by Kostya.
Opinion noted but not definative. Gmail does not always get it right (however you choose to define that) with individual emails or small groups occasionally falling out of the main coversation. In this context "correctly" is a subjective term.
Your arrgresive characterizations of experienced contributors and the development team are both inaccurate and unappreciated.
-
Opinion noted
Good, leave it at that... Reading comprehension goes a long way! This thread was over many posts ago, when it was made clear no changes were made.
Ha, I'm not even going to dignify a response to the rest of your juvenile insinuatory response. This is a tech forum, you are not going to inveigle me, conduct yourself like a professional instead of inciting antagonistic comments with no merit.
-
Opinion noted
Good, leave it at that... Reading comprehension goes a long way! This thread was over many posts ago, when it was made clear no changes were made.
Ha, I'm not even going to dignify a response to the rest of your juvenile insinuatory response. This is a tech forum, you are not going to inveigle me, conduct yourself like a professional instead of inciting antagonistic comments with no merit.
Well said; another self inflicted wound.
-
There is nothing unknown here as I previously stated. You are simply repeating what I have stated.
Contacts with different email clients whether it is mobile or desktop handle message headers differently.
Gmail has never incorrectly grouped messages, not once in my 20+ years using Gmail! Not here to start a pissing match about gmail, but making claims like that you should be very cautious!
I have contacts who use just about every email client you can think of and they are not grouped correctly in Aqua conversation view. There is no ambiguity or confusion how these messages should be grouped and they simply are not grouped correctly.
This a NOT a Aqua bug, it is the inherent way Aqua relies on simple header information to group messages. Could this be fixed, sure if the developers want to pursue this, and it has been made clear it is not going to be fixed!
I simply asked if something had changed in v1.8 to affect conversation mode b/c it only got worse, and it was answered already by Kostya.
Opinion noted but not definative. Gmail does not always get it right (however you choose to define that) with individual emails or small groups occasionally falling out of the main coversation. In this context "correctly" is a subjective term.
Your arrgresive characterizations of experienced contributors and the development team are both inaccurate and unappreciated.
+1
Fully agree, thanks for your statement.
-
Opinion noted
Good, leave it at that... Reading comprehension goes a long way! This thread was over many posts ago, when it was made clear no changes were made.
Ha, I'm not even going to dignify a response to the rest of your juvenile insinuatory response. This is a tech forum, you are not going to inveigle me, conduct yourself like a professional instead of inciting antagonistic comments with no merit.
Sorry to say that, but your responses are really disrespectful, aggressive and narrow-minded.
Please calm down and PLEASE behave respectfully to other members, especially to the developer.
And btw: this is NOT a "tech forum". It's simply a forum where users may ask questions, describe their issues and where other users can offer their help.
That the developer personally takes part in different discussions, takes care of the users and is listening to their voices isn't self-evident but very exceptional and commendable.
All this this together brings up the spirit of the forum and, subsequently, the success of "our" beloved app: AquaMail.
-
Reading comprehension is not your strong suit I see, no problem!
The developer and I had a great conversation over this issue privately! Where you come off insinuating insults are hurled at anyone, including the developer is your own feeble minded view!
Your attempt at morphing this into a personal attack will not go unnoticed. This is a technical thread, behave like an adult, your response is anything but helpful to the members here, let it go and move on.