I cannot figure out how to find where in my email there are (or are not) the appropriate CR LF sequences. I also have seen that it may be that two CR LF combinations are required to signal the end of an email. As I understand it, the absence of a CR before an LF is what causes some systems, servers, or whatever the correct term is to reject the email message. Unfortunately, when I look at emails in HTML, I do not know what characters or character combinations represent a bare line feed ("LF") and what represents a carriage return("CR"). So, I finally tried to get back to resolving this. SMTPSEND.BareLinefeedsAreIllegal message contains bare linefeeds, which cannot be sent via DATA and receiving system does not support BDAT The mail client submitted this message with bare line feeds, which cannot be sent via SMTP protocol DATA command and receiving system does not support BDAT. rejected your message to the following email is a fictional email) I can't tell what the coding in the background is, so it makes editing very difficult and, as I now hypothesize, allows bare line feeds to end up on the email body, which results in this Undeliverable mail notice: I often have big fights with TBird to get it to allow my email formatting to look the way I want. I think I resolved the failed delivery based on bare line feeds being unacceptable to a server by copying and pasting my TBird email to my word processor, removing all formatting that I suspected to cause a bare line feed w/out a carriage return, pasting it back into a new TBird email & sending it.Ĭan anyone suggest an email editor for TBird that is easier to work with or a manual on how to format email with TBird?
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |