<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Missing Envelope-to email header after migration in Email</title>
    <link>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037820#M58273</link>
    <description>&lt;P&gt;I am trapping "X-Spam: Yes" using Thunderbird and MS Outlook on the desktop.&lt;/P&gt;</description>
    <pubDate>Sun, 15 Feb 2026 08:37:13 GMT</pubDate>
    <dc:creator>PhilipHeyes</dc:creator>
    <dc:date>2026-02-15T08:37:13Z</dc:date>
    <item>
      <title>Missing Envelope-to email header after migration</title>
      <link>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2034152#M57100</link>
      <description>&lt;P&gt;When an email was received through the Plusnet system, there was an email heeder of Envelope-To which contained the real email address that the email was sent to, taken from the Envelope data. This is not the same as the contents of the To header. I have used the Envelope-To data here in my email client to filter the email into its correct location for 30 years!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It seems that after migration the Greenby system does not currently provide an Envelope-To header, but instead provides a Delivered-To header. However this contains the mailbox address that the email was delivered to, which is NOT the email address. This has resulted in emails not being filtered locally to their correct locations, despite being assured that no changes would be required.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have noticed that Greenby does have a new additional non-standard header X-Original-Recipient, which seems to contain the actual email address from the Envelope data. However, my email client cannot filter on this non-standard field.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note that the mailbox concerned has over 70 aliases for the mailbox, so it is totally impractical to create a mailbox for each address.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have asked Greenby if the Envelope-To header be re-instated to be like Plusnet, as we were assured.&lt;/P&gt;
&lt;P&gt;While I await a response, I am posing here in case others are also affected.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jan 2026 18:32:27 GMT</pubDate>
      <guid>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2034152#M57100</guid>
      <dc:creator>mavison</dc:creator>
      <dc:date>2026-01-06T18:32:27Z</dc:date>
    </item>
    <item>
      <title>Re: Missing Envelope-to email header after migration</title>
      <link>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037820#M58273</link>
      <description>&lt;P&gt;I am trapping "X-Spam: Yes" using Thunderbird and MS Outlook on the desktop.&lt;/P&gt;</description>
      <pubDate>Sun, 15 Feb 2026 08:37:13 GMT</pubDate>
      <guid>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037820#M58273</guid>
      <dc:creator>PhilipHeyes</dc:creator>
      <dc:date>2026-02-15T08:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: Missing Envelope-to email header after migration</title>
      <link>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037822#M58274</link>
      <description>&lt;P&gt;&lt;a href="https://community.plus.net/t5/user/viewprofilepage/user-id/107337"&gt;@PhilipHeyes&lt;/a&gt;&amp;nbsp;Sorry, but what relevance has the X-Spam header got to my post?&lt;/P&gt;
&lt;P&gt;Greenby have confirmed to me that they no longer provide the (standard) Envelope-To header containing &amp;lt;address&amp;gt;@&amp;lt;account&amp;gt;.f9.co.uk, but it has been replaced by a Delivered-To header containing &amp;lt;mailboxname&amp;gt;@&amp;lt;account&amp;gt;.f9.co.uk and the non-standard X--Original-Recipient header which contains what the Envelope-To header used to. This has cause me major problems in filtering incoming emails, as my client does not recognise the non-standard X-Original-Recipient header.&lt;/P&gt;
&lt;P&gt;One of the many undocumented changes made in the supposed 'seamless' migration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 15 Feb 2026 10:55:25 GMT</pubDate>
      <guid>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037822#M58274</guid>
      <dc:creator>mavison</dc:creator>
      <dc:date>2026-02-15T10:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Missing Envelope-to email header after migration</title>
      <link>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037824#M58276</link>
      <description>&lt;P&gt;If I can trap X-Spam, I could also trap : X-Original-Recipient&lt;/P&gt;</description>
      <pubDate>Sun, 15 Feb 2026 11:22:09 GMT</pubDate>
      <guid>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037824#M58276</guid>
      <dc:creator>PhilipHeyes</dc:creator>
      <dc:date>2026-02-15T11:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: Missing Envelope-to email header after migration</title>
      <link>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037825#M58277</link>
      <description>&lt;P&gt;I am sure you can, using Thunderbird or Outlook. But for one mailbox am not using either, and my client cannot trap the non-standard X-Original-Recipient header.&lt;/P&gt;</description>
      <pubDate>Sun, 15 Feb 2026 11:27:26 GMT</pubDate>
      <guid>https://community.plus.net/t5/Email/Missing-Envelope-to-email-header-after-migration/m-p/2037825#M58277</guid>
      <dc:creator>mavison</dc:creator>
      <dc:date>2026-02-15T11:27:26Z</dc:date>
    </item>
  </channel>
</rss>

