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

[feature] SpamAssassin integration. #195

Open
timbirk opened this issue Feb 9, 2018 · 1 comment
Open

[feature] SpamAssassin integration. #195

timbirk opened this issue Feb 9, 2018 · 1 comment

Comments

@timbirk
Copy link

timbirk commented Feb 9, 2018

Hey, this is more of a placeholder for something I might look into. Integrating mailhog with a spam engine like the widely used SpamAssassin.

The motive behind this is to pre score email templates etc. Before they are ever sent to a customer.

I already use Selenium with mailhog to validate HTML email content (unsubscribe links, https resources / valid html). It would be awesome to have a spam filters point of view on the email too.

@allangood
Copy link

Hello @timbirk, I'm using Mailhog for a while now and what I like it most is its simplicity. It's just one single binary file that you put on your computer an run it. Also, I'm a big fan of Prometheus, another awesome tool that is incredible simple. One thing that keep Prometheus awesome is the fact that all developers keep coding/adding features to the core of the project, on what is really important, and they keep all complex and "not a core functionality" to be implemented by other projects. In this link you will find more information about what I'm talking about: https://prometheus.io/docs/operating/security/#authentication-authorization-and-encryption

I might be wrong, but in my opinion, antispam/antivirus/encryption/authentication and many other functionalities are not part of the "core functionalities" and they need a lot of effort to be implemented and maintained. How many flaws in the SSL protocol were discovered in the past year? Should the developer keep fixing these problems instead of adding new features? Also, these functionalities can be easily achieved by a SMTP gateway.

For instance, if you install Postfix and Mailhog in the same box, all "difficult to implement and maintain" features will be done by Postfix and you just need to add this line on your Postfix main.cf file: smart_host = [127.0.0.1]:1025 to make it forward all processed/clean/checked e-mails to Mailhog.
More information here: http://www.postfix.org/STANDARD_CONFIGURATION_README.html

So, IMHO, antispam/antivirus/encryption/authentication should be left outside of the main code, like Nginx/Apache does for many other projects (like Docker or Prometheus)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants