Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a true pre-parse event point #592

Open
Hildy opened this issue Feb 9, 2018 · 2 comments
Open

Add a true pre-parse event point #592

Hildy opened this issue Feb 9, 2018 · 2 comments
Milestone

Comments

@Hildy
Copy link
Collaborator

Hildy commented Feb 9, 2018

With the current pre-parse event (mail filtering), we"ve already evaluated and processed the message to a certain extent. This means that structural problems with the message (where it"s not following spec, for instance) can"t be addressed.

When gmail ignores the faulty MIME headers and displays a message that we can"t (because it"s technically broken), it"d be nice to be able to have that event point where it"s still a raw email and we can "fix" it.

The specific use case I"m referring to is a mailer (belonging to an important client of a customer, so they can"t make them fix it) that improperly claims a message is "multipart/mixed" when it"s just a plain-text message. Changing the MIME header allows the message to parse, but we can"t do that in the mail filtering because it"s already been processed by that point.

@jstanden
Copy link
Owner

This will be a lot easier with automations in 10.0+ now.

@jstanden jstanden added this to the 10.0 milestone Oct 26, 2019
@jstanden jstanden modified the milestones: 10.0, 9.6 Jun 13, 2020
@jstanden jstanden modified the milestones: 9.6, 10.0 Jun 16, 2020
@jstanden
Copy link
Owner

Now that 10.0 is out we should explore this again. Doing with this automation events will be very simple.

@jstanden jstanden modified the milestones: 10.0, 10.1 Apr 28, 2021
@jstanden jstanden modified the milestones: 10.1, 10.2 Sep 15, 2021
@jstanden jstanden modified the milestones: 10.2, 10.3 Feb 18, 2022
@jstanden jstanden modified the milestones: 10.3, Backlog Jan 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants