"Send a Message" Function on LCR

[rmrichesjr]

I had also discovered the line length violation around May of 2020 and posted this: viewtopic.php?p=210805&hilit=corrupt#p210805

For any recipients with motivation and skills, I have a workaround here: viewtopic.php?p=205956#p205956

tl;dr: The bug was reported in or before 2020. The system involved was scheduled to be replaced soon after that. The bug report was doing to be remembered to make sure the new/replacement system did not duplicate the bug.

I'll try to find the bug report I mentioned in my former post.

[rmrichesjr]

Still trying to find the bug report itself, but I did find that I filed it approximately December 30, 2019.

[rmrichesjr]

Case number GSC05010336

This was the reply sent via ServiceNowGSC:

Attachments are not working reliably in Send a Message at this time. I have forwarded your report to the developers. They are working on redesigning the messaging feature and will need to make sure this isn't repeated. Thank you.

[ambldsorg]

I had also discovered the line length violation around May of 2020 and posted this: viewtopic.php?p=210805&hilit=corrupt#p210805

Yes, this looks very similar to the bug I mentioned in other threads. Whether or not the corruption can be recovered from depends entirely on the recipients email system and what it does with such invalid emails. If the corruption is due to truncation, no workaround exists to recover from it because the data has been lost. If it's some other kind of corruption, then it may be possible. Most people have little control over which SMTP software that their ISP runs and how it behaves with respect to messages that violate the RFCs. That's why I've stated that it's unpredictable and undefined behavior---for some the email might show up just fine, for some it could result in corruption, for some it could result in the email being rejected outright.

Thanks for confirming. I'm glad that you were able to actually get an official bug filed, but it's going on 5 years now and still no resolution (well, 5 years since I noticed the bug in September of 2019). I believe that LRC's send message tool is using JavaMail and I'm actually kind of surprised that it allows the sending of messages in such a poor state.

[rmrichesjr]

That's a very good point that the workaround I referred to does not always work.

For fun, I just replied to the message from ServiceNowGSC about the case number. The optimist in me says there's a chance it might help move the problem toward resolution.

[ambldsorg]

An agent at Yahoo told me that Yahoo was not blocking Church emails from being sent or received, as some in the forum suggested.

That's because it's more likely that the Church itself is "blocking" the emails, not Yahoo. I believe that the Church has a blacklist of email addresses that it won't deliver emails to and when a member's email address is on that list, LCR simply refuses and claims that the message was "rejected by the server".