User bio
404 bio not found
Member since Sep 21, 2016

Thanks. Yes, i thought so. I still have not yet decided which approach to take for this

1) Serialize the Mail Message into an RFC822 character stream and write methods to create %Net.MailMessage to save and load a stream (sounds simple, still it is quite a lot of work to write and test this to make it work conforming to the RFC and working with any Email message one can think of)

2) Copy the complete structure of %Net.MailMessage into own classes, remove or extend the string length limitations and perstist this within an ensemble message body object, for example MYPACKAGE.EnsMessage.EMailForwardRequest

I wonder, might there be anything wrong with taking the 2nd approach and removing the string length limitations. If not, why are the string lengths so tightly restricted in the %Net.MailMessage class in the first place? After all, %Net.MailMessage is a serial object. Shouldn't one be able to persist a Mail Message within another persistent object using this class directly?

I was hoping to find a clever way to use the SMTP and POP3 classes to trick them into generating a RFC822 string. After all, they need to be able to send and receive this. But so far no easy success.

Certifications & Credly badges:
Alexander has no Certifications & Credly badges yet.
Global Masters badges:
Alexander has no Global Masters badges yet.
Alexander has no followers yet.
Alexander has not followed anybody yet.