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

Inability to filter messages,via commands #1

Closed
skx opened this issue Mar 6, 2014 · 1 comment
Closed

Inability to filter messages,via commands #1

skx opened this issue Mar 6, 2014 · 1 comment

Comments

@skx
Copy link

@skx skx commented Mar 6, 2014

Although your Email::Filter library has all the obvious primitives I'm thinking there is an omission - which is the ability to filter a mail via an external binary.

For example the CRM114 mail filter will run against a mail and output an updated message. Something like this:

    steve@ssh ~ $ /usr/bin/crm -u /home/steve/.crm /usr/share/crm114/mailreaver.crm < Test.mail 
    To: foo@bar.com
    From: steve@steve.com
    Subject: UNS: Hello
    X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-27CA1CFB 
    X-CRM114-CacheID: sfid-20140306_154124_764652_540A67EC 
    X-CRM114-Status: UNSURE (   0.02  )

As you can see the output is an updated message.

Now I see I can access the input message via $obj->simple()->as_string(), and then construct a new Email::Simple object which I pass back to $obj->simple(), but it seems like it would be more natural to have a sub filter( cmd ) method.

Does that seem like a reasonable suggestion?

@rjbs
Copy link
Collaborator

@rjbs rjbs commented Jul 2, 2014

This seems reasonable, and would not disrupt the library's precious purity of essence.

Loading

@skx skx closed this Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants