ItchyWeight

joined 1 year ago
sorted by: new top controversial old
Questions about caddy as an alternative to traefik, with docker, and docker-compose in c/main@selfhosted.forum
[–] ItchyWeight@alien.top 1 points 11 months ago (1 children)

https://github.com/lucaslorentz/caddy-docker-proxy

Been using that some time now, also for work projects. Works like a charm with only a couple of additional labels in your compose. Originally, I had also looked at Traefik but decided on caddy proxy for simplicity without loosing functionality.

Forwarding incoming email with an smtp as a service relay in c/main@selfhosted.forum
[–] ItchyWeight@alien.top 1 points 1 year ago

Interesting, although I have to admit, this brings back memories of dealing with sendmail rewrite rules back in the 90s when I had to maintain a uucp based mailserver as an intern ;-) I’ll have look, thanks!

Forwarding incoming email with an smtp as a service relay in c/main@selfhosted.forum
[–] ItchyWeight@alien.top 1 points 1 year ago (2 children)

Yeah, well, empirically, I had repeated issues with t-online and gmail recipients mostly. And I was never sure if it was my config, my IP (hosted on netcup), or something else, but it required constant attention. And that problem should really be gone with an smtp as a service (hopefully).

But maybe I'll have a look at mailu anyway...

1
Forwarding incoming email with an smtp as a service relay (alien.top)
 

After having hosted my own postfix server, including SPF, DKIM and DMARC for years, I finally gave up since there were still fluctuating delivery issues for outgoing mail. So the plan is to use an an external service as relay for outgoing mail, handling generated transactional mails like user registrations and such. (there's still a postfix running on that box)

For now, I've chosen smtp2go which requires sender verification, which is fine for those transactional outgoing mails whose sender is always the same.

With my completely self-hosted setup, I forwarded incoming email to an info address on that domain to my gmail address (to avoid an additional inbox). But unfortunately, that doesn't work with smtp2go because the actual sender for a to be forwarded email is obviously someone who's not a verified sender from smtp2go's perspective and therefor bounces. I suspect other smtp providers might handle that the same way.

The only option I see now is to leave incoming mail on that server, install dovecot or something and setup my main google address to pull messages from that server - which is kind of awkward...

How do you guys deal with such a scenario?