Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Submission + - War against small mail servers? 4

softegg writes: "My company hosts our own mail server. We have high-speed business connections through Verizon and Comcast.

Recently, Verizon and Comcast have been blocking port 25 causing our private mail server to stop functioning. Additionally, a lot of ISPs just started blocking any mail coming from any IP in the address block of cable modems.

So we started laundering our mail through a 3rd party service called DNSexit. Now McAfee's MAPS anti-spam system tells us that they are blocking DNSExit for spam.

Essentially, we are finding ourselves increasingly cut off from sending any outgoing mail. What is a small company supposed to do if you want to host your own mail?"
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

War against small mail servers?

Comments Filter:
  • At least in the past, most ISPs will only block port 25 for non-business users. And most ISP level blocks are against the consumer DHCP ranges.

    So spend the extra money on business accounts with static addresses, and take up the port blocking with your account manager if it's still an issue.

    Barring that, spend $20 a month or so on a hosted VM somewhere, and run your mail through that. (Securely, please.)

    A system administrator.

  • I checked, and yes, we do have business accounts with Verizon and Comcast. It seems like our main on Comcast *might* be going out, but our mail on Verizon definitely is not.

  • Why not get a cheap 512MB VPS from someone like, stick postfix on it and configure you existing mail server to use that as a smart host?

These screamingly hilarious gogs ensure owners of X Ray Gogs to be the life of any party. -- X-Ray Gogs Instructions