Although I still am strongly against open relays, something did just occur to me. I think my ISP sysadmin actually said this, but even if he didn't it's still an open question. What about secondary MX services? When a provider offers secondary MX, as my home DSL provider does, it is now necessary that all mail received for my domain on my provider's mail server be accepted for relaying and queued until my machine comes back up. Obviously, this isn't a *wide open relay*, but it does allow relaying *from* anywhere. And as the provider offers secondary MX to more and more domains, the server may never be a truly wide open relay, but the effect might end up being the same, or pretty close. So is there any way to provide secondary MX services in a more secure fashion? Seems like a catch 22 to me. But something tells me that there's got to be a way to do this without being vulnerable to grubby-little-maggot spammers.
On Fri, Mar 08, 2002 at 08:03:26PM -0500, Paul Iadonisi wrote: > On Fri, Mar 08, 2002 at 07:13:05PM -0500, Ken D'Ambrosio wrote: > > On Fri, 2002-03-08 at 18:57, Paul Iadonisi wrote: > > [snip] > > > Time to dump 'em, and let us know who they are. > > I thought I'ld get some confirmation on this list. Let the opinions keep > pouring in, though. I think I have a good idea which way the scale's gonna > tilt on this one. > For now, for reasons I hope are obvious, I won't reveal who it is. Once > our connectivity is safely in the hands of a provider who knows better, I'll > let y'all know who it was. FYI: they're a tiny 10-ish person company, so > I don't think they have a huge number of customers. My educated guess is that > NO-ONE on this list is a customer of theirs. -- -Paul Iadonisi Senior System Administrator Red Hat Certified Engineer / Local Linux Lobbyist Ever see a penguin fly? -- Try Linux. GPL all the way: Sell services, don't lease secrets ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
