Nick Smith ([EMAIL PROTECTED]) scribbled: > yes they can get mail but not send mail, the reason for relaying through > comcast.net is because if they relay through their own domain it gets > marked as spam etc, that whole DUL thing, they only (cheapest) way to > get it working was to relay through comcast, my client is running > *cough* exchange 2000, but if i can offer a linux alternative that will > work, im sure i can get them to switch, i am running a > postfix/courier-imap setup for my domain at home on the comcast network > and they havnt shut me down as of yet, but i think its only a matter of > time, which is why i want to find out now if there is a way around this.
Here's what I had. I relocated to an area with Cox cable as the provider. They block incoming _and_ outgoing port 25 connections (email). Previously, I received mail on port 25 and relayed my outgoing through comcasts' smtp server (where I lived before). Does this sound like your problem? Here's how I fixed it. I emerged postfix, and configured it like a normal MTA. I then went to dyndns.org where I had my domain registered (lakedaemon.net, duh :) ). I registered for "Mailhop Relay" (incoming), and "Mailhop Out/going/bound/" (outgoing). This costs ~US$50 per year. I configured those services (on the dyndns.org website) to do port 2525 incoming and outgoing. Then I followed the postfix instructions provided by dyndns.org to relay outgoing to outbound.mailhop.org:2525 and to listen for incoming on port 2525. As you can see, it works. :-) (check my headers) If you decide to go that route, let me know of any questions and I'll give you more specifics, config files, etc. hth, Cooper. -- [email protected] mailing list
