Pyramid sending mail: pyramid_mailer or marrow.mail

Question

I am interested in adding outgoing email support to a Pyramid-based web application. I know pyramid_mailer and marrow.mail (formerly known as TurboMail), with an example of pyramid integration here .

There is a similar SO question , but it does not give me the expert opinion I am looking for.

I also have no experience, but both of them seem pretty well cooked. My needs are modest and there will be very low traffic ... ease of use will exceed performance if they are in conflict. Both have transport support that will work for me (I don't need any fancy delivery features).

At first glance, I like the fact that pyramid_mailer supports repoze.tm2 transactional capture, which would be convenient for my project (I'm sure I could hack manrower to do the same, but I would prefer not to do it without good reason) . I also like that inline images are supported in the body of Message () in manrower (leading to the possible conclusion that the latter is more fully formed).

I am looking for opinions, recommendations, and possibly sample integration code.

I found a discussion on the mailing list that also covers this.

Answer 1

The expert answer is that if you just want to send email through an SMTP server, pyramid_mailer is easier to set up and execute. The Lamson Message class, which is verified and reliable, is stable, tested, and supports everything you want to send via email, including attachments and html. The mail program also supports a simple dump of all messages to the queue directory, where later you can simply run bin/qp /path/to/queue/dir to send messages asynchronously.

The other side of the story is that Turbomail has been around for a while, now it is renamed to marrow.mailer and supports a ton of backends, not just SMTP. Alice is actively working on adding transaction support for integration with repoze.tm2, so there is some interest in making the marrow.mailer solution more attractive.