3 ms·

I've run my own email out of my closet for close to 20 years and have no problem sending. I think DKIM/SPF probably help a lot, but I really can't say, as I've

I've run my own email out of my closet for close to 20 years and have no problem sending. I think DKIM/SPF probably help a lot, but I really can't say, as I've never been blocked (to my knowledge).

jlgaddis 9y ago
Same here. We're a long ways from the days when your machine would come with sendmail running and accepting mail for your FQDN OOTB, though... so it's a little more difficult but certainly not out of reach of anyone who is willing to put into the time and effort to learn how to do it right. (I plan on moving my mail to a new machine (well. new VMs) over the next few days and I expect to run into nearly no issues doing so. Then again, like rhizome, I've been doing this for ~20 years.)
walrus01 9y ago
Assuming you have a clueful and attentive upstream ISP and a static /29 or something, running your own mail out of your closet with proper rDNS, spf and dkim probably has better chance of delivery success than the same software setup, but on a dedicated server sharing a /24 of IP space with clueless and occasionally abuse-generating neighboring customers in the same netblock.
- rhizome 9y ago
  I have all that except for delegated reverse DNS, but that hasn't been a problem (again, to my knowledge!).
  - jlgaddis 9y ago
    You don't really need rDNS delegated to you (and I'm pretty sure that's not what walrus01 meant), just so long as you can set (or have your ISP set) the PTR RRs to match. Correctly set PTR RRs can (will) make a huge difference (lots of MTAs will reject if FCrDNS fails).
    - walrus01 9y ago
      Functionally from an smtp perspective it doesn't really matter if the rDNS is delegated to you, just that it's set correctly... ordinarily it's something you only have to set the PTR record for once, even if you need to manually ask your upstream to do it for the /32 that is your server, get them to set it to mail.whateverdomainname.net

I've run my own email out of my closet for close to 20 years and have no problem sending. I think DKIM/SPF probably help a lot, but I really can't say, as I've never been blocked (to my knowledge).

jlgaddis 9y ago

Same here. We're a long ways from the days when your machine would come with sendmail running and accepting mail for your FQDN OOTB, though... so it's a little more difficult but certainly not out of reach of anyone who is willing to put into the time and effort to learn how to do it right. (I plan on moving my mail to a new machine (well. new VMs) over the next few days and I expect to run into nearly no issues doing so. Then again, like rhizome, I've been doing this for ~20 years.)

walrus01 9y ago

Assuming you have a clueful and attentive upstream ISP and a static /29 or something, running your own mail out of your closet with proper rDNS, spf and dkim probably has better chance of delivery success than the same software setup, but on a dedicated server sharing a /24 of IP space with clueless and occasionally abuse-generating neighboring customers in the same netblock.

rhizome 9y ago
I have all that except for delegated reverse DNS, but that hasn't been a problem (again, to my knowledge!).
- jlgaddis 9y ago
  You don't really need rDNS delegated to you (and I'm pretty sure that's not what walrus01 meant), just so long as you can set (or have your ISP set) the PTR RRs to match. Correctly set PTR RRs can (will) make a huge difference (lots of MTAs will reject if FCrDNS fails).
  - walrus01 9y ago
    Functionally from an smtp perspective it doesn't really matter if the rDNS is delegated to you, just that it's set correctly... ordinarily it's something you only have to set the PTR record for once, even if you need to manually ask your upstream to do it for the /32 that is your server, get them to set it to mail.whateverdomainname.net