Gmail

Mayfly — Mon, 18 Nov 2024 14:22:09 GMT

I know this has been mentioned dozens of times over the years.

But can someone explain to me in laymans terms please why I can recieve Gmail emails but I can't reply to them I just get ....

Delivery to the following recipients failed permanently:

even when replying to an gmail email. Is there a remedy at all?

Re: Gmail

MisterW — Mon, 18 Nov 2024 15:47:35 GMT

Are you sending from an <account>.plus.com address or do you have your own domain address ?

Re: Gmail

Townman — Tue, 19 Nov 2024 10:48:30 GMT

The rest of the error message (if any) would be helpful - there is a whole host of reasons for this event, which is qualified by the rest of the message.

Re: Gmail

Mayfly — Tue, 19 Nov 2024 10:54:47 GMT

I have my own domain address.

Whole message

 This is an automatically generated Delivery Status Notification.      

Delivery to the following recipients failed permanently:

   * chrxxxxxx@gmail.com

Reason: A message that you sent to the following recipient could not be delivered due to a permanent error. ** The remote server ?? responded with: ** chrxxxxxx@gmail.com ??:?? This message was created automatically by mail delivery software on the server .

Final-recipient: rfc822; chrxxxxxx@gmail.com
Diagnostic-Code: smtp; 550-5.7.1 [84.93.230.227] Messages missing a valid Message-ID header are not

Last-attempt-Date: Mon, 18 Nov 2024 13:17:56 +0000

Re: Gmail

Townman — Tue, 19 Nov 2024 11:01:12 GMT

Thank you - see Message could not be delivered due to Missing valid MessageID Header - Gmail Community

Have a look at this...

Mitigating email delivery failures (notably Gmail)

Many users are reporting challenging issues in sending emails to some of the big email players. Some of those providers (notably Gmail, but only in respect of their free email accounts) have mandated the SPF & DKIM non-mandatory RFCs on other email providers, such as Plusnet. This can bring about significant difficulty when attempting to send emails using the various Plusnet and vISP legacy email services.

How you mitigate Google's behaviour very much depends on how you send your emails via Plusnet's SMTP servers and which Plusnet vISP email brands you use.

A Plusnet email account or a legacy brand (for example MAAF) email account
you@youraccount.plus.com (native Plusnet email address)
you@yourdomain.co.uk which is registered and hosted by Plusnet (or MAAF)
you@yourdomain.co.uk which is registered elsewhere and hosted by Plusnet
you@yourdomain.co.uk which is hosted elsewhere which forwards mail to your Plusnet (or MAAF) mailbox

The vISP email brands have different level of mitigation capability - for some, the only practical solution might be to migrate your email hosting elsewhere.

Native Plusnet email address

If a user sends email using a from address of you@youraccount.plus.com then DKIM signing will be applied to the email automatically (and pass Gmail's imposed restrictions) if the SMTP server is configured to require authentication. Somewhat unhelpfully, Plusnet's email setup guide suggests that such authentication is NOT required if connecting over a Plusnet connection. Whilst technically true, operational complications can occur and it is much tidier to just enable authentication with the "use the same account settings as the incoming server" option.

Your own domain

If you send from your own domain name, then DKIM signing is not available and you will need to configure SPF instead. How to do this depends on where your domain is hosted - by Plusnet or by third party.

Plusnet fully hosted and registered domain

For Plusnet brand registered and managed domains, SPF configuration is facilitated by the addition of a TXT record in the domain's DNS settings. Plusnet's DNS configuration tool for hosted domains does not permit the creation of TXT records. However, there is an unsupported "facilitation" which will create an SPF record for a hosted domain.

On the basis that your account ALREADY has a hosted domain:

Log into the user portal
Go to Manage Account
Manage Your Domains (Manage your domains link)
Configure domain name
Create an "Additional DNS records (Advanced)" as follows...

For the avoidance of doubt leave the left side blank, exactly as shown. It might take Plusnet's systems up to 6 hours to generate the SPF record.

If your email service is provided by one of the legacy vISP brands (for example MAAF) acquired over the years by Plusnet, similar options are not available to you.

Domain name registered and managed elsewhere (third party)

There are two scenarios here:

Plusnet hosts the email service for the domain
The domain forwards email to the native Plusnet email address

THESE ARE NOT THE SAME. Ideally email forwarding should be avoided as it brings about numerous complications - you should use the DOMAIN's email servers to received and send your domain email, not Plusnet's.

To configure SPF on a domain name registered elsewhere, you must use your domain name provider's DNS configuration tools to set up the applicable SPF record:

v=spf1 a mx include:_spf-internal.plus.net include:_spf-internal2.plus.net ~all

or

v=spf1 include:_spf-internal.madasafish.com include:_spf-internal2.madasafish.com include:_spf-external.madasafish.com -all

topic Re: Gmail in Email

Gmail

Re: Gmail

Re: Gmail

Re: Gmail

Re: Gmail

Mitigating email delivery failures (notably Gmail)

Native Plusnet email address

Your own domain

Plusnet fully hosted and registered domain

Domain name registered and managed elsewhere (third party)