Just wonder what if my mail server went offline for some periods, and the sending party couldn’t deliver.
Will there be any consequences except I don’t get the mail? I tried searching but they all in the perspective of a sender and get a bounce, rather the other way around.
If you’re concerned about missing emails, you might want to sign up for a forwarder instead. I don’t see the point of running an email server that’s going to be off for long periods of time.
Generally it’s not going to put you on a blacklist if a sending server doesn’t manage to send, but some have very short queue times before they’ll drop it, so you’re going to miss a lot of mail that way.
I’ve been self-hosting Postfix for several years and it’s not difficult, if you’re absolutely confident what you do. I don’t recommend it if you don’t know basic behaviors and internals of SMTP and relaying. Also you need to know how to secure your server so you don’t get spammed a lot and getting hammered with brute force attacks.
From time to time you need to react to delivery problems. Most interesting one is perhaps Microsoft, which you need to ask to whitelist your server or your email won’t be accepted.
Unless something has changed massively since I was deeply involved with this stuff, the people that sent you email may get a notification after some hours that their message is being delayed, and maybe after like 24-48 hours they might get a bounce. But if it’s just your SMTP server going down for an hour or two every now and then, the system should be able handle that seamlessly (barring some hiccups like messages showing up with timestamps hours in the past which sometimes is confusing).
I think 8 hours starts to get into territory where they might get an informational message about the delay? That also starts to be long enough that the emails might get lost in the distant past in the client and never be seen, by the time they arrive.
I think when I used to do this, it was one advisory message every 24 hours that a message was holding in the queue, and after 5 days it would bounce, but I have to assume that those limits have shrunk in the modern day. How much, IDK; it might be worth experimenting with it though before committing to creating that situation since it might not go okay.
The problem with this is the probability of your server being available for the next retry is fairly low.
Usually some sort of exponential backoff is used so it might retry after 5 minutes, 15 minutes, an hour, 3 hours, 6 hours, 24 hours, 48 hours, give up.
6-8 hours is probably too much for anything serious where you don’t want emails to just drop. It will work so if you’re just using it to sign up to sites and stuff, you can make sure your server is on to receive the verification emails and stuff. But I wouldn’t use it for anything important.
if you need more reliability you can always use a second mailserver as backup, add a second mx record to your domain and if the first one is not responding the second one will be used. there is no limit of how many next servers there can be specified afaik.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
If you’re concerned about missing emails, you might want to sign up for a forwarder instead. I don’t see the point of running an email server that’s going to be off for long periods of time.
Generally it’s not going to put you on a blacklist if a sending server doesn’t manage to send, but some have very short queue times before they’ll drop it, so you’re going to miss a lot of mail that way.
Having control while not having my PC up the whole day?
Don’t self host email
Sorry, I can’t hear you over the artillery noise.
No need to be that maximalist. Don’t self host email on a desktop machine you turn off.
No, don’t self host email. There are so many things that can go wrong and it will be constantly attacked
Sounds like you had an awful experience about self-hosting email. Want to share with this community so everyone learns?
I’ve been self-hosting Postfix for several years and it’s not difficult, if you’re absolutely confident what you do. I don’t recommend it if you don’t know basic behaviors and internals of SMTP and relaying. Also you need to know how to secure your server so you don’t get spammed a lot and getting hammered with brute force attacks.
From time to time you need to react to delivery problems. Most interesting one is perhaps Microsoft, which you need to ask to whitelist your server or your email won’t be accepted.
SMTP is designed with queues and retries
Unless something has changed massively since I was deeply involved with this stuff, the people that sent you email may get a notification after some hours that their message is being delayed, and maybe after like 24-48 hours they might get a bounce. But if it’s just your SMTP server going down for an hour or two every now and then, the system should be able handle that seamlessly (barring some hiccups like messages showing up with timestamps hours in the past which sometimes is confusing).
What if longer? 6 to 8 hours per day?
I think 8 hours starts to get into territory where they might get an informational message about the delay? That also starts to be long enough that the emails might get lost in the distant past in the client and never be seen, by the time they arrive.
I think when I used to do this, it was one advisory message every 24 hours that a message was holding in the queue, and after 5 days it would bounce, but I have to assume that those limits have shrunk in the modern day. How much, IDK; it might be worth experimenting with it though before committing to creating that situation since it might not go okay.
Thanks for the info. Greatly appreciated.
The problem with this is the probability of your server being available for the next retry is fairly low.
Usually some sort of exponential backoff is used so it might retry after 5 minutes, 15 minutes, an hour, 3 hours, 6 hours, 24 hours, 48 hours, give up.
6-8 hours is probably too much for anything serious where you don’t want emails to just drop. It will work so if you’re just using it to sign up to sites and stuff, you can make sure your server is on to receive the verification emails and stuff. But I wouldn’t use it for anything important.
Oh yeah. I didn’t think of that. Thanks for the heads up.
Some things to consider:
So noting substantial other than I don’t get the mail and might get kick out of newsletters?
Correct. But at least for me, even the low risk of some e-mails getting lost is pretty substantial.
if you need more reliability you can always use a second mailserver as backup, add a second mx record to your domain and if the first one is not responding the second one will be used. there is no limit of how many next servers there can be specified afaik.
Sure. But you could also just not turn off the mail server for a start ;)
True, but I had the crazy idea of running it on my laptop that goes with me.
That’s a truely unusual way. Why not set it up on a raspberry pi?
In the name of science? And a laptop is what I only have rn.