Two more different error codes at Greenby

[#1]

I've mentioned before that I have email forwarded by myself to PN/Greenby which has the side effect that when it isn't playing, I get to see it. Other people won't see this as you see nothing at the PN/Greenby end, the people emailing them initially will see these errors

Today I've had this new one

Technical details of the failure: 
4.3.0 Error: queue file write error

Which I see another person talk about here:

https://community.plus.net/t5/Email/SMTP-Error-451-4-3-0-Error-queue-file-write-error/td-p/2034948

3 days ago I had this wierd one:

Technical details of the failure: 
5.7.1 <[email protected]>: Recipient address rejected: Domain inactive

Both of these errors are intermittent, emails before and after are fine with no configuration changes. And of course the initial emails are accepted perfectly at my first receiving email provider, aren't spam etc. Both are I believe fatal, I certainly never received the one from the second error (which was actually reasonably important).

[#2]

In recent days I have also seen a sporadic : 4.3.0 Error: queue file write error  when sending via Greenby hosted SMTP relay.force9.net  So far it has cleared on the next Send / Receive.

I opened a Greenby Ticket reporting the issue was seen via : relay.force9.net, the AI Bot was mostly concerned with berating me for using SMTPS Encryption and for not using the Plusnet SMTP and flatly rejected the idea there any SMTP issues just ignoring the full error message shown below.  

Send test e-mail message: Your outgoing (SMTP) e-mail server has reported an internal error. If you continue to receive this message, contact your server administrator or Internet service provider (ISP). The server responded: 451 4.3.0 Error: queue file write error

[#3]

@PhilipHeyes 

Please persevere with the bot until you get to an agent - they ARE aware there is a problem.

You could try including "please pass to an agent"

One hopes the more complaints will speed up fix!

[#4]

@mavison 

My ticket was passed to a Agent on 30/06/2026   
I shall keep it open and add any further occurrences or oddities.