Email Library

[nilshoerrmann]

One thing Symphony can be proud of is its simple, small and reliable email system. In the light of Next, wouldn't it be a good idea to release it as a standalone library? Might even be an interesting component for Laravel (which is currently relying on the huge dinosaur Swiftmailer).

[brendo]

I'd love this to happen.

We probably need to improve our CC/BBC support, but I think it's a great idea.

[michael-e]

Of course.

[nilshoerrmann]

So is this an easy or a complicated task?

[michael-e]

I have no idea, because I had no time to play with Laravel.

[nilshoerrmann]

This has nothing to do with Laravel specifically.

[designermonkey]

I wouldn't have thought so, it's just a matter of ensuring we follow a standard of coding, and keep the separation of dependencies correct.

[brendo]

It's most there, it's just creating a standalone set of classes that could be used by any code, without being Symphony specific. I think the main tie we have is the Configuration class, and that's a pretty loose dependency.

[designermonkey]

Yeah, we just need to specify that it needs configuration injecting into it, and show an example of that configuration.

[creativedutchmen]

So is this an easy or a complicated task?

Quite complicated. In fact, it will require almost an entire rewrite.

For Symphony the code works fine, because Symphony does not require its code to be automatically testable. So the email code wasn't written with that in mind.

[jensscherbl]

Wasn't the purpose of using a framework not having to do stuff like this ourselves and instead just using the framework for it?

On a side note, open source webmailer Roundcube recently decoupled its core functions for IMAP access and SMTP email sending into Roundcube framework.