{ "version": "https://jsonfeed.org/version/1", "title": "EMDiscussions - Notes from the Inbox", "description": "", "home_page_url": "https://emdiscussions.github.io", "feed_url": "https://emdiscussions.github.io/feed.json", "user_comment": "", "icon": "https://emdiscussions.github.io/media/website/3d-emd-logo-160.png", "author": { "name": "EMD" }, "items": [ { "id": "https://emdiscussions.github.io/zoho-mail-forever-free-plan.html", "url": "https://emdiscussions.github.io/zoho-mail-forever-free-plan.html", "title": "Zoho Mail Forever Free Plan", "content_html": "

Zoho Mail - 'The Forever Free Plan' - is currently available in the US, EU, and India data centers only. Your IP address determines to which data center you are allocated. For example, if you are in NL, you will be allocated to the Amsterdam data center.

\n

Go to: https://www.zoho.com/workplace/pricing.html

\n

Scroll down towards the end of the page:

\n
\"Screencap
\n

Click on the 'Sign Up now' to proceed. If you're in NL, you'll be directed to the zoho.eu sign up web page: 

\n
\"Screencap
\n

At this point, you need to choose the 'Business Email' option, to be able to use your own domain. The 'Personal Email' option only offers a zohomail email address.

\n

Complete all required fields, including your 'mobile number' to proceed.

\n

Once all is completed, you're allowed to use only one own domain, but can create up to 5 users (5GB storage per user) for that domain.

\n

As with any new provider, it takes time to become familiar with the UI, set up the domain DNS records, users, etc.

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-02-14T14:31:44+00:00", "date_modified": "2026-03-03T18:52:51+00:00" }, { "id": "https://emdiscussions.github.io/mxroute-alias-manager.html", "url": "https://emdiscussions.github.io/mxroute-alias-manager.html", "title": "Create and manage email aliases with MXroute", "content_html": "
\"Screencap
\n
\n

MXroute Alias Manager lets you create unique email aliases for every website directly from your browser. Stop giving out your real email address—create a dedicated alias for each service and keep your inbox organized.

\n
\n

This is an extension recently made available for the Chrome browser. It lets you create unique email aliases directly from the browser.

For those of you already familiar with MXroute, and have an account, the extension is basically a shortcut for creating forwarders inside the account.

\n

This is quite easy to set up:

1. Install the 'MXroute Alias Manager' from the Chrome Web Store. 

2. Log into your MXroute Account.

3. Go to Advanced/API Keys. Complete the 'Server' and 'Username' fields, then click on 'Create API Key'.

4. Most important - COPY the API Key, and SAVE it somewhere safe, ready for the next phase of the set up.

5. Go back to the installed browser extension (ensure that you 'pin' the extension for easy access).

6. Go to the extension settings and complete the various tabs:

Credentials Tab - Complete the Server, Username, and API KEY fields. Test the connection, and if all is OK, click on 'Save Credentials'.

Settings Tab - Select the default alias format. Choose between Domain Based, Random, and Manual entry. If you have more than one domain, choose the default domain. Click on 'Save Settings'.

Domains Tab - Here you choose the default forwarding destination for your domain.

Aliases Tab: Lists the aliases created in the extension, in addition to any forwarders that have been created in the Admin account. From here, one can also copy or delete aliases.

The aliases created in the extension will also now be added into the admin account, where one can 'fine tune' the forwarder - change the forwarding email address, reject, discard silently, or delete it.

\n

I've set up the extension for creating manual entries, so I may create easier to remember aliases.

\n

The beauty of using this extension is that you don't need to set up your domain as a 'wildcard', thereby setting it up as a primary target for spammers.

\n

That's it - all set up, tested, and working!

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-02-10T18:59:03+00:00", "date_modified": "2026-03-04T08:38:28+00:00" }, { "id": "https://emdiscussions.github.io/atomic-mail-my-thoughts.html", "url": "https://emdiscussions.github.io/atomic-mail-my-thoughts.html", "title": "Atomic Mail - My Thoughts", "content_html": "

I signed up for an Atomic Mail account today, and I thought it may be a good idea to set my thoughts on to my blog.

This first image is the log-on screen:

\n
\"Screencap
\n

I've set up my password manager (KeePassXC) for this account. Usually KeePassXC offers to save the login credentials, but it didn't on this occasion - I had to create the entry manually.

After entering my user name (first part of my email address) the password screen appears:

\n
\"Screencap
\n

After entering the password, I have enabled two-factor authentication (2FA) so then the 2FA screen appears:

\n
\"Screencap
\n

One can choose from either an authenticator code, or a seed phrase to proceed. For myself, I elect to choose the authenticator code, which is generated from my Aegis phone app:

\n
\"Screencap
\n

After entering the code, the webmail finally opens:

\n
\"Screencap
\n

As you can see, the layout is fairly basic. There is no option to change to a dark theme.

The email view is set as 'conversation view' - I can't see any way to change that.

A good point is that one allowed 10 aliases - a useful addition considering that some providers may only allow a few or none at all. 

The settings options are fairly basic:

\n
\"Screencap
\n

There is no option to create filters, although one can manually move emails into different folders. There's no mention of IMAP/SMTP, so I assume that it's not available. I suppose that is comparable to ProtonMail and Tuta - they rely on webmail and dedicated phone apps.

Atomic Mail does have an Android phone app - available on the Google Play Store - but unfortunately I could not get that to work. I suspect that the 2FA is the problem here. I tried to log in using the app - looking identical to the webmail layout, however when I expecting to see a request for the 2FA code that didn't happen - instead it said something like wrong email address or password, and I couldn't proceed.

I suppose I should have tried again, but this time by disabling the 2FA to see it that would work. I may try that again at a later date.

I could log on the webmail account using my phone web browser without problem.

Today was my first time using Atomic Mail - why not try it for yourself?

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-01-28T15:18:25+00:00", "date_modified": "2026-02-21T19:41:00+00:00" }, { "id": "https://emdiscussions.github.io/zoho-mail-a-cautionary-tale-with-a-happy-ending.html", "url": "https://emdiscussions.github.io/zoho-mail-a-cautionary-tale-with-a-happy-ending.html", "title": "Zoho Mail - a cautionary tale, with a happy ending?", "content_html": "

Once upon a time . . . well, around February 2012 (to narrow it down!), I signed up for a Zoho Mail Free account. A short time later, I guess I must have abandoned it and forgot all about it.

Fast forward to the present day, I've had a Zoho paid account for a few months, and I decided to move one of my domains over to this email provider. All proceeded according to plan - domain was verified, DNS records all propagated, and it just remained to create aliases for that domain.

First problem encountered: I created a few new aliases, but when I tried to add another specific alias to my account, I got this warning:

\n
\n

The email address you have entered belongs to a different deployment/region. Please contact support for assistance.

\n
\n

I looked in my password manager (I still have old databases saved) but could not find anywhere that I had used this domain with Zoho. So, I approached Zoho Support and they gave me a 'rough' indication of the username that the alias had been used. I made a guess at the username and got that right, then I was stumped (of course!) by the password - I made a few educated guesses, but not educated enough! So, the next step was the 'forgotten password?' option. Luckily, I still had the recovery address, and so got the new password - and finally got into the account - the account that I had set up in 2012!

Looking into the Admin Console, I saw that I had deleted the domain in question, but hadn't deleted the alias - and THAT was the big mistake on my part!

Second problem encountered: Now, to get rid of the alias. I tried to delete it, but Zoho wanted me to verify myself using 2FA authenticator code!

\n

Hmm, now this IS a problem!

Where would that code be? I must have saved it somewhere!

\n

What phone was I using 13 years ago? I've slept a few times since then, and can't remember. Would the code be in an authenticator app on that phone anyway? That's the million dollar question!

I was, more or less, resigned to the fact that I wouldn't be able to use that alias in my current Zoho account, but gave it one last try. After further experimentation, the problem was the lack of the authenticator code - whatever I tried, I came up against that brick wall.

Delving further into the account settings, I then looked at the 'MFA Mode' and the 'Authenticator app' option. There was the 'secret key'! I copied that key into my phone authenticator app, and finally managed to complete the deletion of that alias!

Going back into my current Zoho account, I then added that alias - success!

The cautionary tale is: Never abandon a Zoho Mail account if you've attached any own domain aliases to it!

The happy ending?

Well, apart from finally solving the alias problem, I now also had full access to that 2012 account - and that account has 40GB of storage (basic plan of 5GB plus 'Add-on allotted' of 35GB) and 25 licences!
 
Plus, even though it's a free account, I am able to access my emails using IMAP/SMTP, via my choice of desktop and phone apps.

Now, I need to figure out a use for that old account!

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-01-28T10:47:08+00:00", "date_modified": "2026-02-21T19:41:11+00:00" }, { "id": "https://emdiscussions.github.io/port87-label-powered-email.html", "url": "https://emdiscussions.github.io/port87-label-powered-email.html", "title": "Port87 - label powered email", "content_html": "
\"Port87
\n

It was recently announced that Port87 was out of beta. I had heard about the service previously but had not signed up to test it.

Here's a link to their website, which will explain their service much better than I could:

Port87 - A new kind of email
 
Today, I signed up for the free service - Basic Mail - which has 500MB of storage. Note that only covers receiving of emails. If you want to send emails, get more storage, or use your own domain(s), it's at an additional cost. 
 
Here's the link to their pricing:

Pricing - Port87
 
When signing up for the service, I had to provide a recovery email address - I used a Gmail address, their verification email was received and verified.

Now for first test - I created a label 'Social' for - guess what? - social media stuff. Next I logged into my Runbox account and sent a test message to 'myusername-social@port87.com'.

\n

Shortly after I received this auto-response from Port87:

\n
\n
This address has email screening enabled. Therefore, Port87 needs you to do a one-time verification that you're a real person. If you can see the blue-gray checkmark below, you're all set. If not, you can enable remote images in your email client or click the link to verify your address. Once verified, your message will be delivered.
\n
 
\n
Verify Address
\n
 
\n
Port87 uses this verification process to prevent unwanted mail from getting to our users. Until you complete this verification, your message will be on hold. If you don't complete this verification within 60 days, your message will be deleted. We apologize for the inconvenience and appreciate your understanding.
\n
 
\n
Best,
\n
The Port87 Team
\n
\n
 
\n
Once I had verified my address, the original email then appeared in my Port87 account. So far so good!
\n
 
\n
The next test was sending an email to what Port87 calls my 'bare' address - 'myusername@port87.com'. I would prefer to call it my 'default' address, but anyway . . .
\n
 
\n
This time, sending from the Gmail account that is my recovery email address for my Port87 account. This is where I encountered the first problem. Although I had received the verification email from Port87 when setting up the account, this time I received nothing - nothing in my Gmail inbox or spam folder! That was surprising to me that Gmail did not flag the first email from Port87, and then just silently dropped the second one. Gmail appear to be classing the second email as spam.
\n
 
\n
So that test failed.
\n
 
\n
Tried the same thing again, but sending from an email address hosted by MXroute. Again, and the same as Gmail, I got nothing back. It seems that MXroute had dropped the email.
\n
 
\n
So that test also failed.
\n
 
\n
One more try, this time sending from a Fastmail account. Luckier, this time, I got a response back from Port87, but it landed in the spam folder. At least I could mark it as 'not-spam' and then it all worked OK from then on. This is the auto-response received from Port87:
\n
 
\n
\n
It looks like you've emailed my bare Port87 address, myusername@port87.com, which doesn't get through to me. In order to protect against unwanted messages, Port87 requires you to use a special address to email me. Please re-send your email to one of these addresses:
     
myusername-friends@port87.com
Please use this address if you are a friend or family. 
     
 myusername-inquiries@port87.com
 Please use this address if you have a question or request for me. 
     
 myusername-other@port87.com
 Use this address for all other reasons. 
     
 myusername-social@port87.com
 Please use this address if you are a contact on social media.
\n
\n
 
\n
The labels for the first three email addresses (Friends/Inquiries/Other) are already in the system, the fourth label (Social) was created by myself, as stated previously.
 
I've since whitelisted the port87.com domain within my Gmail, MXroute and Fastmail accounts. I've not re-tested those accounts, although that is the logical next step.
 
Early days, first steps, etc.
 
Update - November 14th 2025:
 
I received a message today from Hunter Perrin, the creator of Port 87 - he had seen my blog entry. He advised that, at the time of my testing the product, there was a bug in Port87 preventing the DKIM signing of the auto-responses to bare address emails. He has since fixed the bug, and so it should be working as expected.
 
I have re-tested again - this time sending from Gmail and Zoho Mail accounts. The verification emails were received as expected in each account.
 
Result = success!
\n
 
\n
 
", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-01-28T10:33:29+00:00", "date_modified": "2026-02-22T10:22:25+00:00" }, { "id": "https://emdiscussions.github.io/understanding-dmarc-reports.html", "url": "https://emdiscussions.github.io/understanding-dmarc-reports.html", "title": "Understanding DMARC reports", "content_html": "

I decided it was about time that I sat down and tried to understand these reports, and I think that I now have a better understanding of the reports.

Below, was the (then) current published DMARC record for one of my domains. The record that I originally had (and which had generated this DMARC report) was to provide an aggregate (rua) report, but I have now changed it to provide only a failure (ruf) report:

\n
\n

v=DMARC1; p=reject; ruf=mailto:dmarc@example.com; adkim=r; aspf=r;

\n
\n

Note, that I have used ‘example.com’ as the domain, instead of my actual domain name.

As for the received DMARC report (in XML format) - that was generated based on my original DMARC record - this is broken down into sections, with a real received example of a RUA (Aggregate) report:

\n
\n

<?xml version=\"1.0\" encoding=\"UTF-8\"?>
<feedback>
<version>1.0</version>
<report_metadata>
<org_name>kddi.com</org_name>
<email>noreply-dmarc-support@kddi.com</email>
<extra_contact_info>https://support.kddi.com/dmarc</extra_contact_info>

\n
\n

Above is the first section of the report, it contains information about the ISP (here it's kddi.com), their email address, etc.

Next up, it’s the report ID:

\n
\n

<report_id>20241118133820067715</report_id>

\n
\n

Followed by the date range:

\n
\n

<date_range>
<begin>1731881931</begin>
<end>1731904700</end>
</date_range>

\n
\n

Use https://timestamp.online/ to convert this: For example:

1731881931 = 17/11/2024, 22:18:51

1731904700 = 18/11/2024, 04:38:20

Next is policy published:

\n
\n

<policy_published>
<domain>example.com</domain>
<adkim>r</adkim>
<aspf>r</aspf>
<p>reject</p>
<sp>reject</sp>
<pct>100</pct>
<fo>0</fo>
</policy_published>

\n
\n

Next is the source (as an IP address) of the sender and how many attempts:

\n
\n

<source_ip>165.154.234.207</source_ip>
<count>1</count>

\n
\n

A check of the IP address shows the location of the sender as ‘Lagos, Lagos, Nigeria’.

Next is policy evaluated:

\n
\n

<policy_evaluated>
<disposition>reject</disposition>
<dkim>fail</dkim>
<spf>fail</spf>
<reason>
<type></type>
<comment></comment>
</reason>
</policy_evaluated>

\n
\n

This says rejected - DKIM and SPF both failed.

Next, the domain that was the sender:

\n
\n

<identifiers>
<envelope_to>ezweb.ne.jp</envelope_to>
<envelope_from>example.com</envelope_from>
<header_from>example.com</header_from>
</identifiers>

\n
\n

And finally, the auth results:

\n
\n

<auth_results>
<dkim>
<domain></domain>
<selector></selector>
<result>none</result>
<human_result>no signature data</human_result>
</dkim>
<spf>
<domain>example.com</domain>
<scope>mfrom</scope>
<result>fail</result>
</spf>
</auth_results>

\n
\n

This says that both DKIM and SPF have failed, therefore the email was rejected.

As I did not send the email in question myself, the DMARC record has done it's job and rejected the email as not being legitimate - success!

I don't have any recent DMARC failure reports (in TXT format) to compare with the above aggregate report, but I may update this post when one becomes available.

Finally: Just to say, this is not an expert definitive analysis, but just my rudimentary understanding!

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-01-28T10:12:17+00:00", "date_modified": "2026-02-21T19:41:30+00:00" }, { "id": "https://emdiscussions.github.io/i-asked-chatgpt-to-create-a-google-mail-script.html", "url": "https://emdiscussions.github.io/i-asked-chatgpt-to-create-a-google-mail-script.html", "title": "I asked ChatGPT to create a Google Mail Script", "content_html": "

I asked ChatGPT:

\n
\n

Create a Google Gmail script to automatically delete emails older than 7 days that have the label '7-Days'.

\n
\n

Within a few seconds, I got this response:

\n
\"Screencap
\n

Could it be that simple, I asked myself?

There's only one way to find out, so I copied the code and went to https://script.google.com for my Gmail account and created a new project, and pasted the code.

Saved and Run, I had to authorise the use of the script.

Following the ChatGPT instructions on how to set up, I created the trigger to run once an hour, and saved that.

I was sceptical about whether it would work, but - and admittedly it's early days yet - the script does appear to work!

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-01-28T09:09:12+00:00", "date_modified": "2026-03-03T18:51:11+00:00" }, { "id": "https://emdiscussions.github.io/youve-got-mail.html", "url": "https://emdiscussions.github.io/youve-got-mail.html", "title": "You've got mail!", "content_html": "
\"Digital
\n

Up to now, I've posted any email-related 'stuff' on my personal blog, but have now decided to post that content on a separate blog.

\n

So, here it is!

\n

The plumbing!

\n

This is the combination that enables the creation of the blog:

\n

Github Pages - The blog is hosted by GitHub Pages - a static site hosting service.

\n

Publii - The blog is created by Publii, a free, open-source desktop application, developed by a small team based in Poland.

\n

ImageKit - The blog images are hosted by ImageKit, an 'all-in-one media management and delivery platform', They operate a distributed processing network across multiple regions, including Frankfurt.

\n

Hoping to leave a comment? Sorry, there aren’t any here. It’s not that your thoughts don’t matter – I just value my sanity more than moderating a comment section. If you wish to comment on any of my posts, you may comment via my Mastodon account.

", "author": { "name": "EMD" }, "tags": [ ], "date_published": "2026-01-27T18:33:25+00:00", "date_modified": "2026-04-05T09:48:37+01:00" } ] }