Legacy user, multiple email issues...

[#1]

Hi All

I've just upgraded my phone, and I'm now experiencing a couple of issues. so I'm looking for some confirmation and advice.

Issue 1:

After moving from an iPhone 13 to a 15, I can no longer access my ...@freenetname.co.uk email or my domains @auroradesign.co.uk emails, via the Mail app.

I've tried various settings, but it seems to be the email address that iOS doesn't like anymore - please see attached image.

All was working flawlessly on the iPhone 13.

I can access everything via the free-online webmail, and via Thunderbird.

Issue 2:

Sending e-mails to Gmail addresses (trying to forward @freenetname emails to my phone mainly) are bouncing back.

I realise this is a common issue, and as far as I can tell this is a SPF or MX problem(?), but as a Legacy user, it seems there is no fix for this, or at the very least, its beyond my abilities.

Also my renewal is due in the new year.

Does this mean, It's now time for me to switch host? Would switching hosts rectify both of these issues?

thanks all

Ryan

[#2]

Personally for me I would switch hosts because it's a well known fact that our servers aren't the greatest and to be honest you would get better support from a dedicated domain host than you would with us. 

I'm sure one of the superusers would be able to help more as they have more experience with email than me, but that's my 2 cents

[#3]

@willcutforth 

That is a tad defeatist!!  Granted in the case of sending email using a personal domain name with a MAAF account in the face of Gmail's questionable draconian behaviours to FREE @gmail.com accounts ... there is minimal remedy here ... beyond sending to @googlemail.com (their so called secure email service leaks like a sieve!).

@auroraonline 

If you could get this working using an iPhone 13, it should work with iPhone 15.

The invalid email address message covers the account settings.  I would suspect that the issue is that the settings are using your domain name version of your email address as the user name ... rather than your @MAAF.com email address.

Unfortunately sending to @gmail.com using your own domain name as the sending address will require SPF or DKIM (both non-mandatory) configured.  Whilst SPF exists for the native @MAAF.com email address, this cannot be configured for domain names hosted on MAAF.

The alternative approach is to "fool" Gmail by sending to their alias domain name - for fred@gmail.com send to fred@googlemail.com