Some lists and emails are distributed via ns1.samba.org. For those of you that use ORBS, you'll find it is blacklisted now. There is no mention of it on the website and it doesn't return a positive when you enter it for testing but it has slipped into the ORBS blacklist somewhere. Samba.org admins may wish to force all ns1 outbound email via another netblock, bringing it up to ORBS only seems to get more of your netblock blacklisted. In the meantime, those of you who mysteriously don't get emails from samba lists may magically get them again after you grant explicit access to ns1.samba.org [203.17.0.92]. -d -- "The difference between 'involvement' and 'commitment' is like an eggs-and-ham breakfast: the chicken was 'involved' - the pig was 'committed'." -------------- next part -------------- A non-text attachment was scrubbed... Name: david.vcf Type: text/x-vcard Size: 239 bytes Desc: Card for David Ford Url : http://lists.samba.org/archive/samba/attachments/20000821/1f1a903f/david.vcf
Michael Ju. Tokarev
2000-Aug-22 00:05 UTC
[OT but please read] ORBS blacklisting ns1.samba.org
That just reminds to _not_ to use orbs. I was forced to quickly turn their usage off at all my mail servers just a hour ago, since mails from other sites that I know never have problems with relaying started to be rejected by them. Woh. :( There should be some time at least to sort their crap out... Unfortunately, this can't be offtopic for anyone in the Internet community, since SPAM (that is why orbs, mail-abuse et al are all here) is a real pain in the ass, and we should do something with it all together. And I understand a hard task orbs people doing... Regards, Michael.
James Sutherland
2000-Aug-22 00:39 UTC
[OT but please read] ORBS blacklisting ns1.samba.org
On Mon, 21 Aug 2000, David Ford wrote:> Some lists and emails are distributed via ns1.samba.org. For those of > you that use ORBS, you'll find it is blacklisted now. There is no > mention of it on the website and it doesn't return a positive when you > enter it for testing but it has slipped into the ORBS blacklist > somewhere. > > Samba.org admins may wish to force all ns1 outbound email via another > netblock, bringing it up to ORBS only seems to get more of your netblock > blacklisted. > > In the meantime, those of you who mysteriously don't get emails from > samba lists may magically get them again after you grant explicit access > to ns1.samba.org [203.17.0.92].There's something seriously wrong with ORBS, it seems. My ISP's (NT based - they were bought by MS...) is NOT in ORBS, according to the WWW site - but I get occasional bounces citing ORBS as the reason. Come to think of it, I've a feeling david@kalifornia.com is one of the addresses doing it. Any insights, David?? James.
Christopher R. Hertel
2000-Aug-22 02:28 UTC
[OT but please read] ORBS blacklisting ns1.samba.org
For those using the ORBS service, I recommend that you look into Paul Vixie's MAPS project: http://mail-abuse.org/ MAPS has a somewhat better reputation for responsible blacklist management. The ISP I use from home is ORBS blacklisted. Not because of open relays, but because they won't allow ORBS to randomly probe them. Chris -)-----> Some lists and emails are distributed via ns1.samba.org. For those of > you that use ORBS, you'll find it is blacklisted now. There is no > mention of it on the website and it doesn't return a positive when you > enter it for testing but it has slipped into the ORBS blacklist > somewhere. > > Samba.org admins may wish to force all ns1 outbound email via another > netblock, bringing it up to ORBS only seems to get more of your netblock > blacklisted. > > In the meantime, those of you who mysteriously don't get emails from > samba lists may magically get them again after you grant explicit access > to ns1.samba.org [203.17.0.92]. > > -d > > -- > "The difference between 'involvement' and 'commitment' is like an > eggs-and-ham breakfast: the chicken was 'involved' - the pig was > 'committed'." > >Content-Description: Card for David Ford [Attachment, skipping...] -- Christopher R. Hertel -)----- University of Minnesota crh@nts.umn.edu Networking and Telecommunications Services Ideals are like stars; you will not succeed in touching them with your hands...you choose them as your guides, and following them you will reach your destiny. --Carl Schultz
Peter Samuelson
2000-Aug-22 02:49 UTC
[OT but please read] ORBS blacklisting ns1.samba.org
[David Ford <david@kalifornia.com>]> Some lists and emails are distributed via ns1.samba.org. For those > of you that use ORBS, you'll find it is blacklisted now. There is no > mention of it on the website and it doesn't return a positive when > you enter it for testing but it has slipped into the ORBS blacklist > somewhere.Check your facts. ns1 isn't in "the ORBS blacklist" -- it's listed in a different category. If you as a mail admin confuse the two it's not ORBS's fault. From their web site: Spam source and haven netblocks also get listed if our attention is repeatedly drawn to them - the easiest way to do this is for those netblocks to start filling ORBS spamtraps. These return a 127.0.0.5 A RR code. ns1 is in this category. Thus it does NOT mean that ns1 is an open relay -- it means that their upstream contains spamhausen. So, all you mail admins out there -- check your setups! If you only want to reject known open relays, set your MTAs to only look for ORBS responses of 127.0.0.2 and 127.0.0.3. 127.0.0.4 and 127.0.0.5 mean *other things*. If you don't wish to block those other things, *don't*. It's a flexible system, and I wish people would stop blaming ORBS for random mail admin mistakes. Peter