home.social

#qmail — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #qmail, aggregated by home.social.

fetched live
  1. Dealt with a lovely and very helpful third-party support person for a client's E-mail and once again was reminded why I don't use #Office365 for E-mail. What a nightmare to administer. Bear in mind, I'm still running a couple medium sized #qmail servers.

    As I type this, Office365 still isn't letting us send E-mail but I'm sure we'll get there.

    #email #sysadmin #techsupport

  2. I laughed at the description of `sendmail` as “... less a mail transfer agent and more a recurring CVE subscription.”

    blog.calif.io/p/we-asked-claud

    #qmail #security #risks #mail

  3. #Claude Code fand eine Remote Code Execution in einer populären Distribution des Mailservers #qmail.

    Das Problem lag an #popen und man benötigt einen wunderschönen MX-Record der Form:

    x'`id>/tmp/pwned`'y.example.com

    Das "reine" qmail von @djb ist nicht betroffen.

    blog.calif.io/p/we-asked-claud

    github.com/califio/publication

    #RCE #security #mail #MTA #Mailserver

  4. I blogged about migrating my MX (email) from self-hosted #Qmail, with Gmail as the front-end, to @fastmail: rainskit.com/blog/migrating-fr

    Many #yaks were shaved in this adventure, and I'm much less visible to Google, now!

    The post is long, mostly because I needed to eulogize the end of 25 years of email self-hosting. But it might be interesting to some of you. And it might be helpful if you are on Qmail and want to stop self hosting.

  5. Bisher war ich von #Uberspace eigentlich recht angetan. Nun komm ich aber mit der Umsetzung meiner eigentlichen Mailstruktur an meine Grenzen. Ggf. kann man das mit einer eigenen #qmail-Konfiguration umsetzen. Aber da #U8 ohne qmail irgendwo am Horizont auftaucht, ist mein Enthusiasmus mich in die qmail-Configs einzuarbeiten, irgendwie sehr gering. 😩

  6. I made the mistake of starting to learn about GEMINI from its Frequently Asked Questions document.

    It's not aimed at people like me, who already understand the benefits and tradeoffs of static content servers. So it drives lots of points home, repeatedly, that I already know.

    It's apparently aimed at the same sort of monoculture Chrome+Apache Think for HTTP that parallels the old BIND Think and Sendmail Think that #qmail and #djbdns were up against years ago.

    #GEMINI #djbwares #publicfile

  7. Hedwig was once a trusty #Qmail mail server named by @ChrisHardie

    Now Hedwig is being re-incarnated as a #Linux desktop notification utility by @dnkl

    linuxrocks.online/@dnkl/112841

    It’s like notify-send but only depends on d-bus and not also libnotify.

  8. Who's making a LLM-based spam filter plugin for #Spamassassin or #Rspamd?

    Gmail has advanced AI-based filtering. Now that LLMs are becoming democratized, I'm ready for a self-hosted AI spam filter.

    It seems much more popular to publish research papers on the viability of LLM-based spam filtering than it is to build LLM-based spam filtering software. Here are dozens of papers: arxiv-sanity-lite.com/?rank=pi Nothing on GitHub, yet.

    #llm #ai #spam #phishing #SelfHosting #postfix #exim #sendmail #qmail

  9. @lauren @djb

    #qmail, for example, dates from the late 90s, and has never been susceptible to this problem. It knows what the end of message marker is, and doesn't accept anything but that to end a message. No confusion, no problem.

    I haven't dug into the updates from Postfix, Exim, sendmail, but I suspect their default configurations don't make them vulnerable to this as relay servers - perhaps as final-destination servers, where it could act as a #DMARC bypass mechanism.

    4/x

  10. @ska @schmonz

    I haven't. I sent a message to the #qmail list, replying to something or other, some time back, in which I described the lasting legacy of qmail as its #design, not its #codebase, and suggested perhaps a group project to maybe modernize a couple of design things - small! - and then start with fresh #implementations of the components to add #features or whatever - and noted they don't all have to be in the same implementation language etc.

    [...]

  11. @dangoodin @djb @0x0FFF

    Dan G.: to butt in, from experience with #djb from mailing lists for #qmail, #djbdns, etc...

    When djb states facts, he is invariably correct. When he presents a logical argument, he is rigorous, but it is frequently non-trivial to follow. Very dense logic, and perhaps omission of the more "obvious" steps, mean you can't grasp it on first read.

    When taking apart someone else's argument, it's even denser and crammed with references. But worth it. Spend the time.

  12. @cks

    It looks like it would be a 1-line patch to new-inject and ofmipd in DJB's mess822. Just drop the header in the very same way that they already drop "Bcc:".

    Erwin Hoffmann could probably be persuaded to add it to s/qmail.

    @cazabon

    #InternetMail #privacy #qmail

  13. "Note that the original Qmail site is gone" says the #Dovecot doco.

    A quick check confirms that cr.yp.to/qmail.html is still there and has been all along.

    It turns out that the Dovecot doco writers didn't know where #qmail originated, and thought that qmail.org was its original WWW site. But a quick check reveals that even that is still there, too.

    #djbwares