Moblog inserts incorrect data on channel title

[netz0]

Moblog has some problem detecting the emails Subject from some mail providers. One example is if messages are sent from a mail.com account.

Instead of inserting the email subject in the channel title, it instead fills up:
Date;

I assume there is something in the regex that detects the content of messages that need some improvements. This happens with tons of email servers and email providers. It works fine with other email messages like Gmail.com

[intoeetive]

While not a fix to the issue, in cases like this title can be set using override in email body
https://docs.expressionengine.com/latest/add-ons/moblog.html#entry_title

[netz0]

If you are piping mails using the module, you want the original email data from emails you don't control. Example, customer service piping emails, you want to save the data from the email as received, at least the basic info like sender, date, title and body.

It's not hard to replicate this since it happens with almost all email providers, at least the very popular ones. If this module worked as expected, it could be extremely useful for a lot of functionality that involves any sort of email reception features. One example is a customer support ticket system, or a bug tracker, event system, email alerts, or just anything that requires saving emails as EE entries for later processing. There are many good email parsers on GitHub, I suspect the reason this is not working fine is that the code is just ancient, and it's not handling the parsing correctly.

[intoeetive]

@netz0 are you aware of some other email providers having this issue? Preferrably the one where we could create a testing account

[netz0]

When I tested this 2 years ago for a small test project, almost all the major providers had these issues, even Gmail. Most of them had the message header data parsed incorrectly, so I decided to put it on hold.

My guess, the module worked fine 15 years back when Ellis Lab released it, but it requires a major refactoring on the email parser side to make it usable again or replacing the entire email parser with something more current that is used by other projects today.

[intoeetive]

It did work well on the mail providers I tested with... which mail client did you use to send the mail? Might be specific to that