Configuration with Docker behind Reverse Proxy about kill-the-newsletter HOT 6 CLOSED

@The-Inamati: Thanks for the nice words about my work 😃

Judging by the error message, it seems like your emails are reaching a mail server, who’s declining to deliver the messages. The thing is: That doesn’t sound like the Kill the Newsletter! email server!

One thing I know for sure: Kill the Newsletter! doesn’t send that type of error message: if it doesn’t recognize an address, it considers that as spam and drops the message on the floor.

Under the hood we’re using the smtp-server package, but I don’t think it would send that kind of error message either.

Also, you’re running the email server on port 2525, which is for development/test. In production, you should use port 25, which is the appropriate port for SMTP servers receiving email from the internet.

Then again, you may not be able to do that, because it sounds like your server already has an email service running on that port…

Let me know how it goes.

from kill-the-newsletter.

You are right I do have a mail server already running on that port. Is there a way to run Kill The Newsletter through an existing mail server?

from kill-the-newsletter.

I really recommend that you let Kill the Newsletter! sit on a machine by itself.

That said: I’ve never done this myself, but I think there are two ways to do what you asked for (in the following discussion say your email server is Exim):

1. Exim relays the emails to Kill the Newsletter!

This is similar to how you’d setup email forwarding. You’re probably interested in the SMTP transport.

You must also configure Kill the Newsletter! to run the email server on a port other than 25 (for example, 2525, as you’re already doing). Check the EMAIL_PORT environment variable.

2. A mail proxy sits in front of both Exim and Kill the Newsletter!

I think the most popular solution as a mail proxy is nginx. Start here:
http://nginx.org/en/docs/mail/ngx_mail_core_module.html
https://docs.nginx.com/nginx/admin-guide/mail-proxy/mail-proxy/

Good luck. Let me know how it goes.

I’m closing this for now since the main issue seems to have been resolved.

from kill-the-newsletter.

Follow Up to this.
I added a routing rule in my mail server pointing to the Kill The Newsletter container.
When I test the routing in the mail server it appears to be working as you can see below:

The issue is that the feed isn't updated. I checked the feeds folder inside the container and there is a XML file with the feed information. How can I troubleshoot this further?

from kill-the-newsletter.

Nevermind. It's working now.

from kill-the-newsletter.

👍

What was wrong? Or was it one of those issues that solves itself and you never get to learn what happened?

from kill-the-newsletter.