From owner-freebsd-questions Tue Feb 6 21:37:47 2001 Delivered-To: freebsd-questions@freebsd.org Received: from transbay.net (dns1.transbay.net [209.133.53.2]) by hub.freebsd.org (Postfix) with ESMTP id 1DC4F37B491 for ; Tue, 6 Feb 2001 21:37:27 -0800 (PST) Received: from transbay.net (rigel.transbay.net [209.133.53.177]) by transbay.net (8.11.2/8.11.2) with ESMTP id f175b8O66852; Tue, 6 Feb 2001 21:37:08 -0800 (PST) Message-ID: <3A80E2FF.E7149987@transbay.net> Date: Tue, 06 Feb 2001 21:54:07 -0800 From: UCTC Sysadmin Organization: UC Telecommunications Company X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Scott Reese Cc: support@transbay.net, postmaster@msn.com, abuse@msn.com, fraud@ftc.gov, rbl@mail-abuse.org, abuse@uu.net, paul@vix.com, abuse@above.net, dlr@bungi.com, postmaster@boardwatch.com, postmaster@freshmeat.net, jgrosch@mooseriver.com, questions@freebsd.org, sales@uu.net, info@uu.net, support@transbay.net Subject: Re: Not Receiving MSN email.... References: <5.0.2.1.2.20010206093201.00a83da8@mail.transbay.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG His mail is coming through a uu.net dialup, lax3.da.uu.net, which we are blocking. I have at least three complaints about mail from users using services that we block since they don't control their spam. I will work on my spam filter to add the capability to allow users despite the rest of the domain's mail being blocked. Meanwhile, if he wants to bother, have him send a complaint to MSN to have MSN tell UU.NET to deal with abuse complaints generated by other-party ISPs. In english: Joe ISP has a contract with UU.NET to provide dialup access in LA. So does MSN. Joe ISP allows his users to spam us. We complain to UU.NET. UU.NET does nothing (they may forward the complaint to Joe ISP, but ... see next line.) Joe ISP does nothing (his spammers are still happy campers.) UU.NET doesn't bother to follow up, so Joe ISP's spammers have free rein. We continue to get Joe ISP's users' spam, so we block the specific UU.NET regional dialup facility. MSN users are therefore also blocked. Because UU.NET NEVER FOLLOWS UP ON COMPLAINTS and because the Joe ISPs of this world violate UU.NET's AUP with impunity, MSN users (and we) are inconvenienced. UU.NET is supposed to be a reputable company, but they are too busy making money to pay any attention to the grief their inattention causes. We have complained numerous times to UU.NET (hundreds, literally) and they do nothing, and no human from UU.NET ever contacts us. We have complained to the FTC, to the RBL, to everyone we can think of whose email address we can guess off the top of our heads and nobody does a damned thing. There is some joker in Panama City, Florida who alone accounts for 25% of all spam we trap and trash, who has been spamming for MONTHS with impunity, because Earthlink doesn't do a damned thing about them and UU.NET doesn't enforce their policies even after I have called them on the phone to explain the situation and ask them to follow up on the complaints they forward to Earthlink. Earthlink has done exactly zero (0) about this spammer despite their $million dollar TV ad suggestion that they fight spam. Forget 7-up, image IS everything. The RBL could get Earthlink's and UU.NET's attention immediately if they listed Earthlink and/or uu.net in their tables, but they have studiously ignored my complaints for reasons of their own which they choose not to share with me, despite my sending them a file containing some 100 trapped-mail headers documenting the problem and despite my explicitly asking for feedback, even if they felt they couldn't address the problem. So maybe if your dad complains to the right person at MSN we might see some action on this, but I won't hold my breath. It's left to little ISPs like us to defend ourselves and handle the mail because NOBODY, including multimillion dollar access (Earthlink) and transport (uu.net) providers, and enforcement agencies (RBL), lifts a finger to stop this rampant abuse. Our users don't get the Panama City spam because I wrote a modification of sendmail explicitly to trap such third-party-relayed spam. Unfortunately your dad uses UU.NET thanks to MSN's using them as a transport provider in LA and so his mail is also trashed. I have to do even more work to allow a few "good" users' mail to get through. I seriously would make more money going INTO the spam business - obviously the big boys won't bother to stop me. Crime pays thanks to the indifferent. -ecsd@transbay.net (Eric Dynamic) Scott Reese wrote: > > Hi Solitaire, > > My dad is still having problems emailing me from his msn address. He can send and receive email from everyone > else he corresponds with, so this leads me to believe that there may be a problem at our end. Here are the headers > from a message that he sent to my hotmail account. I hope this helps: > > From: "monkeya" Save Address - Block > Sender > To: "Scott Reese" <*******@hotmail.com> Save Address > Subject: Re: Hello > Date: Tue, 6 Feb 2001 09:17:52 -0800 > > MIME-Version: 1.0 > Received: from [207.46.181.18] by hotmail.com (3.2) with ESMTP id > MHotMailBC497CDD00BC40043113CF2EB51205AF9; Tue Feb 06 09:18:42 2001 > Received: from oemcomputer ([63.23.78.34] unverified) by ^^^^^^^^^^^ see below > cpimssmtpu02.email.msn.com with Microsoft SMTPSVC(5.0.2195.1600); Tue, 6 Feb > 2001 09:17:56 -0800 > From monkeybestia@email.msn.com Tue Feb 06 09:18:51 2001 > Message-ID: <009001c09060$bf850580$d24d173f@oemcomputer> > X-Priority: 3 > X-MSMail-Priority: Normal > X-Mailer: Microsoft Outlook Express 4.72.3155.0 > X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 > Return-Path: monkeybestia@email.msn.com > X-OriginalArrivalTime: 06 Feb 2001 17:17:57.0268 (UTC) > FILETIME=[BFA1B540:01C09060] > > Thanks in advance for your assistance. > > -Scott > > Scott Reese > Internet Sales/Development station36[209] # traceroute 63.23.78.34 traceroute to 63.23.78.34 (63.23.78.34), 30 hops max, 40 byte packets 1 cromwell (209.133.53.1) 0.703 ms 0.697 ms 0.624 ms 2 ITalkToTheWind (209.133.55.10) 2.894 ms 3.091 ms 5.251 ms 3 main-133-88.sjc.above.net (209.133.88.4) 5.175 ms 3.194 ms 2.916 ms 4 core5-main1-oc12.sjc1.above.net (208.185.175.249) 3.116 ms 3.043 ms 2.983 ms 5 core3-sjc1-oc48.sjc2.above.net (208.184.102.206) 3.030 ms 4.696 ms 5.851 ms 6 pao1-sjc2-oc48.pao1.above.net (208.184.233.142) 9.377 ms 17.416 ms * 7 POS1-1-0.GW9.PAO1.ALTER.NET (157.130.197.121) 12.633 ms 6.750 ms 3.960 ms 8 136.ATM2-0.XR1.PAO1.ALTER.NET (152.63.52.186) 6.660 ms 8.494 ms 7.175 ms 9 189.at-2-0-0.TR3.SCL1.ALTER.NET (152.63.48.222) 23.299 ms 5.687 ms 4.880 ms 10 107.at-5-1-0.TR1.LAX9.ALTER.NET (146.188.140.137) 94.203 ms 87.450 ms 84.307 ms 11 297.at-1-0-0.XR1.LAX9.ALTER.NET (152.63.112.237) 85.003 ms 90.146 ms 102.171 ms 12 191.at-3-0-0.HR1.LAX9.ALTER.NET (152.63.114.113) 139.951 ms 139.420 ms 128.945 ms 13 111.ATM3-0.DR3.LAX3.ALTER.NET (152.63.113.137) 118.416 ms 113.181 ms 113.944 ms 14 tnt9.lax3.da.uu.net (206.115.153.201) 117.823 ms 115.177 ms 133.320 ms 15 2Cust34.tnt9.lax3.da.uu.net (63.23.78.34) 3095.949 ms 3277.546 ms 3913.309 ms To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message