Recent content by Alex Presland

Sorry, wrong wording... please contact your SERVER PROVIDER and ask them to open up inbound port 8443 to your server in their firewall. @Kaspar has also given a good alternate solution of using the "enable access domain" feature, if your server provider won't open up inbound port 8443.

Contact your ISP Support and get them to open port 8443 in their firewall

Hi @Solarom It is worth confirming that your server is listening on Port 8443. I'm also on a Ubuntu 22.04 based server and get the following when checking which ports are open: alex@mypleskserver:~$ sudo ss -tl | grep 8443 LISTEN 0 511 0.0.0.0:8443...

Indeed. I once had someone who had accidentally blocked a sender in their client. Any email from them thereafter always disappeared. I had to provide them email client specific advice on how to find and remove this block...

Removed means that the email server has completed processing the email and has done all the deliveries that it needs to. Similar to "End" or "Complete".

We have email-only subscriptions on our server. The DNS is hosted on Plesk, which helps SPF, DKIM and the webmail certificates work. The DNS then points the website to a different IP address. One recommendation is that your external website is hosted on WWW.domain.tld and that you have...

Thanks for all your work on this @danami - I can also confirm that this fix is also working for me. Lots of needed email fixes in 18.0.59 ! :)

This evening my co-Administrator spotted a number of email validation fixes listed in the changelog to Plesk Obsidian 18.0.59: I repeated the test which I originally reported above, while still on Plesk Obsidian 18.0.58 Update #2 and these failed DKIM tests. I then upgraded to Plesk Obsidian...

Tried that but sadly DMARC is still showing as broken. :-( Thanks for the idea...

I'm not really sure what is going on here... but I've got perfectly valid non-spam email coming into our Plesk server. However, when it is forwarded it is rejected before being sent. @danami any idea how this can be please? The email is going [email protected] --> [email protected] (which...

When I (previously) used Mailman 2 lists, there were 2 configuration settings which both involved the word "munge". Effectively, they munge the message so it isn't being forwarded and is represented as being ORIGINATED from the mailing list. At this point it all just worked. My suggestion is...

All this makes me more and more convinced that those writing the RFCs have utterly messed up. I've read the DKIM & DMARC RFCs and it lists all sorts of scenarios which it should work in... but the bottom line is that it doesn't work with the MAJOR email hosts. I had a bounce forwarded to me...

Interesting. We're getting these errors and don't have Plesk Email Security installed.

Hi All. I got busy on my festive break and then got busy with paid work after that. Apologies for my lack of reply. The above is still an issue in my book, but very happy for events to supersede this. I see that ARC was implemented in 18.0.58 with an issue still being in focus for some...

People should also be aware of the issue in this thread: https://talk.plesk.com/threads/arc-errors-in-maillog.372933/ As far as I'm aware, this issue currently isn't resolved.