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

I want specific non-fatal messages to precede others and interpret long sentences. #26

Open
rmast opened this issue Dec 11, 2016 · 1 comment

Comments

@rmast
Copy link

rmast commented Dec 11, 2016

The newest version I found still can't cope with lines that have been split up by different rules of the max. linesize, like
The mail system

<xxxxxxxxxxxxxxxxxxxxxx>: maildir delivery failed: "Sorry, the user's
maildir
has overdrawn his diskspace quota"

so I'll come up with a new version. I'm trying to get this library to read IMAP-mails as well.
Probably the well maintained IMAP-implementation will lower the needed complexity for header and body interpretation.

At the moment I have an IMAP-user with some really bounced e-mails, for which I want all possible retries and mailbox full messages to appear before a 550 as a last resort appears. I even think about being more clear about not knowing, just answer 9.9.9 or something, as 550 already could be anything.

The resulting status can then be updated to the mail-relation records, to be able to decide to keep them. As I'm not confident I'll ever succeed at matching 100% I could imagine it would be convenient just to be able to click on some link with the mail-relation-record just to open the original e-mails without having to search for them.

@rmast
Copy link
Author

rmast commented Dec 17, 2016

I forked for these fixes. I didn't include IMAP-functionality to keep the testset in file-format.

Apart from the concatenation of broken lines, there also is a 'recurse'-function that doesn't recurse but just skip the line on which the recipient is found. This line sometimes contains the most crucial message however, so I chose not to skip it.

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

1 participant