Selfhosted

40008 readers

724 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

[Help needed] issue self hosting lemmy and email smtp (vlemmy.net)

submitted 1 year ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

I am trying to setup my own lemmy server. I used ansible.

I can access my server via my domain just fine. But emails are not working.

First i had my mail and mx records pointing to privateemail via namecheap.

Then i tried using cloudflare email routing and their mx records.

neither worked for me with error connecting.

I thought maybe using dovecot? But self hosting email is new to me

I was hoping to use namecheaps privateemail but wasn’t sure how to get it working.

The email account worked and can send / receive but Lemmy and postfix cannot communicate with it.

Now I have no Mx records as I’m not sure what I should be using I am sure I am missing something obvious but idk what

Any ideas ?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 1 year ago

That really should work, I would check for potential firewall issues or something.

Mine is basically identical to yours:

email: {
    smtp_server: "mail.h.max-p.me:465"
    smtp_login: "[email protected]"
    smtp_password: "REDACTED"
    smtp_from_address: "[email protected]"
    tls_type: "tls"
  }

It's possible your server is slightly misconfigured and actually serve plain traffic on 465 and requires the use of the STARTTLS command.

Can you reach your server with openssl?

openssl s_client -connect smtp.domain.de:465

This should end up with something like that:

    Start Time: 1688422790
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
***
read R BLOCK
220 hosting.max-p.me ESMTP Postfix