Thank You - Thank You - Thank You
I'm testing this right now and am getting emails through to their destination with the Subject Line as typed...but I am not seeing the content line. In fact the email looks like not even a line feed or carriage return is interpreted (ooo, do those terms date me).
So based on what I found I question how the content is being interpreted by the mail reader. Maybe an HTML vs TEXT interpretation thing. Maybe nothing you can do about this on my side, but others in the future might wonder why they too don't see the content so I'm posting this.
Event log in reverse order; assume stated error has nothing to do with msg content line.
|telnet|Disconnected, email sent.
|telnet|Disconnected. receive error: Stream is closed
Looking at the Email Source info in mail reader I do see the text line:
X-Sender: me@ xyz.com
From: me@ xyz.com
To: me@ abc.com
Subject: HE Msg Relay
sending email from HE
X-CMAE-Envelope: long HEX string
I saw nothing in the more detailed system log that indicated what the posted error was for.
Would be cool if the Subject line was a dynamic variable for quick scan purposes. This might also avert SPAM blocking from seeing the same subject from the same sender repeatedly (Shouldn't matter at this volume of messages but it might).
One other question, what in your opinion is the security risk in using this facility. What is getting transmitted "in the open" other than the msg content ( ignoring what's sitting in the device field entries on the HE ).
Thanks again for your work.