Hi @jengelh ,
thanks for the input.
- Couldn't get MFCMAPI to work, is there a howto somewhere?
- Figured out, its every mail i reply to, not just Dell's.
I did the following:
- Replied to the grommunio post notification mail in Windows Mail, but did not send.
- Closed the Mail (mail gets saved into "drafts" folder in mailbox)
- Opened mailbox in Grommunio Webmailer
- Found the Mail in drafts folder
- Downloaded the Mail as MSG
- Opened the MSG in Texteditor, and here is the the header:
MIME-Version: 1.0
To: "noreply@grommunio.com" <noreply@grommunio.com>
Importance: Normal
Sensitivity: Normal
Date: Fri, 28 Jul 2023 17:34:21 +0200
Subject: AW: [New Post] Read receipt and invalid@invalid recipient
Thread-Topic: [New Post] Read receipt and invalid@invalid recipient
Thread-Index: AVvB2QFlP1vNrTWX/0yrVGzSnplLqP////9h
Message-ID: <gxZT.JMvTUj1adkqdwctIr8u4cw@ThuiUkeJpEWU_SxZlhyrfAlbJFc7-FBAnmrvw2MK5ek.xz>
Content-Language: en-us
Content-ID: <a1d8422c47226044a8823b7cee106e19@ostermayer.club>
X-Mailer: gromox-oxcmail 2.10.126.29c078d
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="utf-8"
As you can (or cannot) see: there is no sender header at all in the draft!
Guess the invalid@invalid gets added somewhere from the pressing "send" inside Windows mail to Postfix.
When replicating the same in Grommunio Web Mailer, header looks as follows:
(cleaned sender Mail from Header)
MIME-Version: 1.0
Sender: "Christoph Ostermayer" <c*****@*******.club>
To: "grommunio Community" <noreply@grommunio.com>
Importance: Normal
Sensitivity: Normal
Date: Fri, 28 Jul 2023 17:47:15 +0200
Subject: Re: [New Post] Read receipt and invalid@invalid recipient
Thread-Topic: [New Post] Read receipt and invalid@invalid recipient
Thread-Index: AWrB2QGwDfEHoMST0EC2C3E4JNWYTv////96
Message-ID: <gxZT.x2LdCzEAyUm5mgGumC7gUA@J194Xp0MR0KwAERF_24xLVMCTuWl6jpDrorCv2eP3cY.xz>
Content-Language: en-us
Content-ID: <6dd7acfa80786f45aeb0702411bf71e2@ostermayer.club>
X-Mailer: gromox-oxcmail 2.10.126.29c078d
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0005_768D4E0A.566228B"