I set up email gateway. Test function worked.
But email from another station gets stuck in Parking!
Please assist.
top of page
Email gets stuck in Parking
Email gets stuck in Parking
11 comments
Like
11 Comments
bottom of page
I set up email gateway. Test function worked.
But email from another station gets stuck in Parking!
Please assist.
Another issue: It seems the Test Email function should have an additional stage - it should also check the Cluster settings, and warn or fail if ClusterEmailGatewaySenderNode is not ON, and also (in the current implementation) if more than one INI in the cluster has this ON!
I suggest to enhance the Test Email function as follows: 1. Create a test email and inject it into the gateway outbox. 2. Send it to test email account - that will send a copy of the email with confirmation of receipt back to the sender's email.
Note: might need a mechanism to prevent bad actors from abusing this! But that is also a risk with the email gateway function in general.
Thank you for this guidance and information.
Having similar issue with messages to a station being PARKED. Local operator, N3XL, is running a 40M and 2M instance on his computer. He has configured instance for Internet delivery. I have asked him to confirm that "auto relay" is enabled. He checked and it was not enabled on his station, hence message were not getting delivered to the Internet.
Ok thank you for providing additional data. Is VarAC instance part of a cluster ?
He did not mark this as an Email. so VarAC thinkg there is callsign starting with 4ZPE2...
He should have marked it as email
to be sure look in the VMAIL data in the datastream of that QSO (through the Callsign history tool) and I am pretty sure you will not fine the <E> tag in that VMail so it is treated as a regular VMail.
The upcoming version checks if an EMail address was accidently used while composing a reuglar VMail and alert the user about it.
Closing the bug