![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/0943eca5-c4c2-4d65-acc2-7e220598f99e.png)
This feels like more of an operating system issue than a hardware issue. What you’re looking for is a way to reduce the power it sips while still allowing downloads to happen. Leaving aside the edge cases like OS updates others have mentioned, the major issue is that applications aren’t structured like that.
If I have Firefox open with one tab displaying a website that runs 1,102 javascript routines all the time in an attempt negotiate a really good advertising deal for each of the banner ads it’s showing - you know, the type you visit and your machine starts crawling and the fans start blowing almost immediately - and another open on Ubuntu.com where I’ve just clicked on the “Download Ubuntu desktop ISO” button, only Firefox knows which of those tasks can be backgrounded and right now (as far as I can see) there’s no API in any of the major OSes where it can say “Send me this signal and I’ll only do the thing that can’t be interrupted.” nor “I’ve put the stuff that can’t be interrupted in this thread, so only run this when you’re trying to save power and nobody’s using the computer anyway”)
Would it be a good idea? Well, that would depend on whether developers actually use that API if it ever comes into existence. I’d like it, I just see it being one of these well meaning things that devs would avoid using because it complicates their code and probably makes it easier to break.
I use Zimbra with an external email gateway that only accepts authenticated email. Zimbra is pretty heavy (it’s intended to be a Microsoft Exchange replacement) but it at least has a huge amount of protection built-in to deal with spam and comes configured out of the box to not relay (well, outside of you setting up aliases and lists.)
That said, it’s not hard to find “incoming email only” configurations that deliver to local mailboxes only, for most email servers. The thing to avoid is having a single server configuration that tries to do both - accepting external email and sending locally originated email out. The configurations do exist to do that, but they’re confusing and tricky.
External email gateways… that bit is hard. I use a mail server I set up myself on a VPS. It does not listen on incoming port 25. It requires credentials. I did this largely because I was trying to send email out via Xfinity’s customer email relay, but the latter kept upping the authentication requirements until one day Zimbra just couldn’t be configured to use it any more. And each time they changed something, I wouldn’t find out until I noticed people had clearly not received the emails I’ve sent out.
VPSes are problematic as some IPs are blocked due to spam. There’s not much you can do about it if you’re stuck with a bad IP, so if you can find a way to send outgoing email via your ISP’s outgoing email server, do that. For Postfix, you can send out authenticated email using something like: in main.cf:
relayhost = [smtp.office365.com]:587 smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_use_tls = yes
and in /etc/postfix/sasl_passwd:
[smtp.office365.com]:587 example@outlook.com:hunter2
So in summary:
Good luck.