home.social

#qmail — Public Fediverse posts

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

  1. 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

  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. 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

  4. 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

  5. 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

  6. #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

  7. #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

  8. #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

  9. #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

  10. #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

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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. 😩

  17. 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. 😩

  18. 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. 😩

  19. 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. 😩

  20. 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. 😩

  21. 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

  22. 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

  23. 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

  24. Hachtz. 😍 Wegen der anstehenden Mail-Migration auf U8 bei @ubernauten mal genauer mit dem

    $ uberspace mail ….

    Kommando auseinander gesetzt. War ja immer noch auf #qmail unterwegs.

    Dabei #sieve fürs Mail filtern wieder in den Fokus geraten und plus-addressing entdeckt. 😍

    Und ja ich brauchte eine kleine Hilfe vom @hallo Support. Wieder wie gewohnt fix und natürlich mit einer Lösung. ❤️

    Danke hier an das Team auch nochmal hier öffentlich. 🏆

  25. 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.

  26. 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.

  27. 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.

  28. 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.

  29. 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.

  30. 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

  31. 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

  32. 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

  33. 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

  34. 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

  35. @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

  36. @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

  37. @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

  38. @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

  39. @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

  40. @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.

    [...]

  41. @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.

    [...]

  42. @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.

    [...]

  43. @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.

    [...]

  44. @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.

    [...]