home.social

#ryoms — Public Fediverse posts

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

fetched live
  1. New hobby: randomly k-lining hosts that I find annoying while log-surfing.

    $ grep 162.21 /var/log/mail.log | wc -l
    6187
    # ip route add blackhole 162.217.160.0/21

    Byebye. Enjoy your stay next to what seems to be the entire residential IP range(s) of Vietnam Posts and Telecommunications Group.

    …something something…less greylisting, more spamass-milter?

    #ryoms #spam

  2. New hobby: randomly k-lining hosts that I find annoying while log-surfing.

    $ grep 162.21 /var/log/mail.log | wc -l
    6187
    # ip route add blackhole 162.217.160.0/21

    Byebye. Enjoy your stay next to what seems to be the entire residential IP range(s) of Vietnam Posts and Telecommunications Group.

    …something something…less greylisting, more spamass-milter?

    #ryoms #spam

  3. New hobby: randomly k-lining hosts that I find annoying while log-surfing.

    $ grep 162.21 /var/log/mail.log | wc -l
    6187
    # ip route add blackhole 162.217.160.0/21

    Byebye. Enjoy your stay next to what seems to be the entire residential IP range(s) of Vietnam Posts and Telecommunications Group.

    …something something…less greylisting, more spamass-milter?

    #ryoms #spam

  4. New hobby: randomly k-lining hosts that I find annoying while log-surfing.

    $ grep 162.21 /var/log/mail.log | wc -l
    6187
    # ip route add blackhole 162.217.160.0/21

    Byebye. Enjoy your stay next to what seems to be the entire residential IP range(s) of Vietnam Posts and Telecommunications Group.

    …something something…less greylisting, more spamass-milter?

    #ryoms #spam

  5. New hobby: randomly k-lining hosts that I find annoying while log-surfing.

    $ grep 162.21 /var/log/mail.log | wc -l
    6187
    # ip route add blackhole 162.217.160.0/21

    Byebye. Enjoy your stay next to what seems to be the entire residential IP range(s) of Vietnam Posts and Telecommunications Group.

    …something something…less greylisting, more spamass-milter?

    #ryoms #spam

  6. Also trying to simultaneously use Postfix in multi-instance mode, which is not covered in #RYOMS, but if something is worth doing it's worth overdoing, I guess.

  7. Also trying to simultaneously use Postfix in multi-instance mode, which is not covered in #RYOMS, but if something is worth doing it's worth overdoing, I guess.

  8. Also trying to simultaneously use Postfix in multi-instance mode, which is not covered in #RYOMS, but if something is worth doing it's worth overdoing, I guess.

  9. Also trying to simultaneously use Postfix in multi-instance mode, which is not covered in #RYOMS, but if something is worth doing it's worth overdoing, I guess.

  10. Also trying to simultaneously use Postfix in multi-instance mode, which is not covered in #RYOMS, but if something is worth doing it's worth overdoing, I guess.

  11. Running Modoboa as you mailserver?
    Need/want to migrate to a new instance?
    Want to keep mailboxes and configs, but otherwise have a clean "new" install?

    Fret no more:
    infosecworrier.dk/blog/2026/02

    #MigrateYourOwnMailServer #MYOMS #RYOMS #Modoboa

  12. Running Modoboa as you mailserver?
    Need/want to migrate to a new instance?
    Want to keep mailboxes and configs, but otherwise have a clean "new" install?

    Fret no more:
    infosecworrier.dk/blog/2026/02

    #MigrateYourOwnMailServer #MYOMS #RYOMS #Modoboa

  13. Running Modoboa as you mailserver?
    Need/want to migrate to a new instance?
    Want to keep mailboxes and configs, but otherwise have a clean "new" install?

    Fret no more:
    infosecworrier.dk/blog/2026/02

    #MigrateYourOwnMailServer #MYOMS #RYOMS #Modoboa

  14. Running Modoboa as you mailserver?
    Need/want to migrate to a new instance?
    Want to keep mailboxes and configs, but otherwise have a clean "new" install?

    Fret no more:
    infosecworrier.dk/blog/2026/02

    #MigrateYourOwnMailServer #MYOMS #RYOMS #Modoboa

  15. Running Modoboa as you mailserver?
    Need/want to migrate to a new instance?
    Want to keep mailboxes and configs, but otherwise have a clean "new" install?

    Fret no more:
    infosecworrier.dk/blog/2026/02

    #MigrateYourOwnMailServer #MYOMS #RYOMS #Modoboa

  16. @r Polished my setup a bit. Everyone’s happy except Outlook.com. So there’s absolutely no actionable intelligence in that report, or is there?

    I’m using: github.com/techsneeze/dmarcts-

    #ryoms #dmarc

  17. @r Polished my setup a bit. Everyone’s happy except Outlook.com. So there’s absolutely no actionable intelligence in that report, or is there?

    I’m using: github.com/techsneeze/dmarcts-

    #ryoms #dmarc

  18. @r Polished my setup a bit. Everyone’s happy except Outlook.com. So there’s absolutely no actionable intelligence in that report, or is there?

    I’m using: github.com/techsneeze/dmarcts-

    #ryoms #dmarc

  19. @r Polished my setup a bit. Everyone’s happy except Outlook.com. So there’s absolutely no actionable intelligence in that report, or is there?

    I’m using: github.com/techsneeze/dmarcts-

    #ryoms #dmarc

  20. @r Polished my setup a bit. Everyone’s happy except Outlook.com. So there’s absolutely no actionable intelligence in that report, or is there?

    I’m using: github.com/techsneeze/dmarcts-

    #ryoms #dmarc

  21. The 00s called and want their open relays back…(this is unfiltered back-to-back mail-log)

    #ryoms

  22. The 00s called and want their open relays back…(this is unfiltered back-to-back mail-log)

    #ryoms

  23. The 00s called and want their open relays back…(this is unfiltered back-to-back mail-log)

    #ryoms

  24. The 00s called and want their open relays back…(this is unfiltered back-to-back mail-log)

    #ryoms

  25. The 00s called and want their open relays back…(this is unfiltered back-to-back mail-log)

    #ryoms

  26. I've enjoyed following @rfcs. It's a steady reminder of the history I've lived through, what came before me, and alternate histories not taken.

    But it just threw RFC 3463 at me, and: TOO SOON, BOT, TOO SOON. #ryoms

  27. I've enjoyed following @rfcs. It's a steady reminder of the history I've lived through, what came before me, and alternate histories not taken.

    But it just threw RFC 3463 at me, and: TOO SOON, BOT, TOO SOON. #ryoms

  28. I've enjoyed following @rfcs. It's a steady reminder of the history I've lived through, what came before me, and alternate histories not taken.

    But it just threw RFC 3463 at me, and: TOO SOON, BOT, TOO SOON. #ryoms

  29. I've enjoyed following @rfcs. It's a steady reminder of the history I've lived through, what came before me, and alternate histories not taken.

    But it just threw RFC 3463 at me, and: TOO SOON, BOT, TOO SOON. #ryoms

  30. I've enjoyed following @rfcs. It's a steady reminder of the history I've lived through, what came before me, and alternate histories not taken.

    But it just threw RFC 3463 at me, and: TOO SOON, BOT, TOO SOON. #ryoms

  31. I’m seeing tons of the following in the mail-server logs. Anyone know what’s up there? Just the usual or a Xmas-special?

    sm-mta[215926]: [45.148.10.25] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[215930]: [45.148.10.29] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[216460]: [178.16.55.124] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA-v4

    #ryoms #smtp

  32. I’m seeing tons of the following in the mail-server logs. Anyone know what’s up there? Just the usual or a Xmas-special?

    sm-mta[215926]: [45.148.10.25] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[215930]: [45.148.10.29] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[216460]: [178.16.55.124] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA-v4

    #ryoms #smtp

  33. I’m seeing tons of the following in the mail-server logs. Anyone know what’s up there? Just the usual or a Xmas-special?

    sm-mta[215926]: [45.148.10.25] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[215930]: [45.148.10.29] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[216460]: [178.16.55.124] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA-v4

    #ryoms #smtp

  34. I’m seeing tons of the following in the mail-server logs. Anyone know what’s up there? Just the usual or a Xmas-special?

    sm-mta[215926]: [45.148.10.25] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[215930]: [45.148.10.29] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[216460]: [178.16.55.124] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA-v4

    #ryoms #smtp

  35. I’m seeing tons of the following in the mail-server logs. Anyone know what’s up there? Just the usual or a Xmas-special?

    sm-mta[215926]: [45.148.10.25] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[215930]: [45.148.10.29] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSP-v4
    sm-mta[216460]: [178.16.55.124] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA-v4

    #ryoms #smtp

  36. @navigium

    @mailbox_org one potential customer lost due to the lack of IPv6, which you had at the beginning of this year.

    @navigium have you looked into @Tutanota

    Depending on your concrete needs @netcup might be worth a look.

    #ipv6 #RYOMS #askfedi

  37. @navigium

    @mailbox_org one potential customer lost due to the lack of IPv6, which you had at the beginning of this year.

    @navigium have you looked into @Tutanota

    Depending on your concrete needs @netcup might be worth a look.

    #ipv6 #RYOMS #askfedi

  38. I successfully put #OpenDKIM onto a production #Postfix server today and started signing the messages that Hotmail, et.al. were rejecting, and it took me less than half a day!

    But I'm still going to tell my boss I want to buy a copy of #RYOMS and get reimbursed for it.

  39. I successfully put #OpenDKIM onto a production #Postfix server today and started signing the messages that Hotmail, et.al. were rejecting, and it took me less than half a day!

    But I'm still going to tell my boss I want to buy a copy of #RYOMS and get reimbursed for it.

  40. I successfully put #OpenDKIM onto a production #Postfix server today and started signing the messages that Hotmail, et.al. were rejecting, and it took me less than half a day!

    But I'm still going to tell my boss I want to buy a copy of #RYOMS and get reimbursed for it.

  41. I successfully put #OpenDKIM onto a production #Postfix server today and started signing the messages that Hotmail, et.al. were rejecting, and it took me less than half a day!

    But I'm still going to tell my boss I want to buy a copy of #RYOMS and get reimbursed for it.

  42. I successfully put #OpenDKIM onto a production #Postfix server today and started signing the messages that Hotmail, et.al. were rejecting, and it took me less than half a day!

    But I'm still going to tell my boss I want to buy a copy of #RYOMS and get reimbursed for it.

  43. The #BSDCan Travel Fund auction in honor of Mike Karels ends today at 5PM EDT.

    If you wanted a #RYOMS challenge coin or the special backers-only edition, this is your chance.

    mwl.io/archives/24105

  44. The #BSDCan Travel Fund auction in honor of Mike Karels ends today at 5PM EDT.

    If you wanted a #RYOMS challenge coin or the special backers-only edition, this is your chance.

    mwl.io/archives/24105

  45. The #BSDCan Travel Fund auction in honor of Mike Karels ends today at 5PM EDT.

    If you wanted a #RYOMS challenge coin or the special backers-only edition, this is your chance.

    mwl.io/archives/24105

  46. The #BSDCan Travel Fund auction in honor of Mike Karels ends today at 5PM EDT.

    If you wanted a #RYOMS challenge coin or the special backers-only edition, this is your chance.

    mwl.io/archives/24105

  47. The #BSDCan Travel Fund auction in honor of Mike Karels ends today at 5PM EDT.

    If you wanted a #RYOMS challenge coin or the special backers-only edition, this is your chance.

    mwl.io/archives/24105

  48. From the ISP I’ll be getting my ‘net from soon:

    “RevDNS? Yeah, sure, we can do that, although I’ll have to ask the boss about pricing. No one ever asked us for such a thing, and our partner company got only 2 such cases since starting in 1992.”

    I blame @mwl and #RYOMS for becoming a once-in-a-decade oddity. :blobfoxmelt2:

  49. From the ISP I’ll be getting my ‘net from soon:

    “RevDNS? Yeah, sure, we can do that, although I’ll have to ask the boss about pricing. No one ever asked us for such a thing, and our partner company got only 2 such cases since starting in 1992.”

    I blame @mwl and #RYOMS for becoming a once-in-a-decade oddity. :blobfoxmelt2:

  50. From the ISP I’ll be getting my ‘net from soon:

    “RevDNS? Yeah, sure, we can do that, although I’ll have to ask the boss about pricing. No one ever asked us for such a thing, and our partner company got only 2 such cases since starting in 1992.”

    I blame @mwl and #RYOMS for becoming a once-in-a-decade oddity. :blobfoxmelt2: