On Mon, 8 Dec 2003 [EMAIL PROTECTED] wrote:
> >Unless you like playing whack-a-mole, you need a smarter hammer, not a
> >bigger one.
>
> Email peering *IS* a smarter hammer. If all the cluefull email
> administrators would set up peering agreements with each other
> and exchange contact informatio
[EMAIL PROTECTED] writes on 12/8/2003 5:16 AM:
Anyone for a joint NANOG/CAUCE meeting? http://www.cauce.org
Over at APRICOT, CAUCE Asia Pacific (apcauce) is holding an antispam
tutorial and conference track, which will also double as an apcauce meeting.
APCAUCE (http://www.apcauce.org) holds tu
> Part of the problem is that there are no agreed rules of engagement
> for email abuse issues. By setting up email peering agreements in
> advance, we could put those rules of engagement in place and we
> could ensure that our email peers have the *RIGHT* contact
> information.
Agreed. One of t
On Mon, 08 Dec 2003 10:16:49 GMT, [EMAIL PROTECTED] said:
> Email peering *IS* a smarter hammer. If all the cluefull email
> administrators would set up peering agreements with each other
> and exchange contact information, there would be fewer of these
> situations.
There's a lot more people doi
>Unless you like playing whack-a-mole, you need a smarter hammer, not a
>bigger one.
Email peering *IS* a smarter hammer. If all the cluefull email
administrators would set up peering agreements with each other
and exchange contact information, there would be fewer of these
situations. Part of th
james writes on 12/5/2003 11:09 PM:
I was not aware one can fake everything in the mail headers, including
the sending mail server.
1. HELO forged in the first header where the connecting IP hands off to
your MX
2. All other headers below that can be, and are, heavily forged.
--
srs (postmaste
james wrote:
>
> On Fri, 2003-12-05 at 16:05, Laurence F. Sheldon, Jr. wrote:
>
> > Everything else was forged, spoofed, or unintelligble.
> >
> > I was probably not filtering off traffic from you (for any value of
> > "you"), I was filtering off stuff with your IP address in it.
>
> I was not
On Fri, 2003-12-05 at 21:20, just me wrote:
> On 5 Dec 2003, james wrote:
>
> On Fri, 2003-12-05 at 16:05, Laurence F. Sheldon, Jr. wrote:
>
> > Everything else was forged, spoofed, or unintelligble.
> >
> > I was probably not filtering off traffic from you (for any value of
> > "you")
On 5 Dec 2003, james wrote:
On Fri, 2003-12-05 at 16:05, Laurence F. Sheldon, Jr. wrote:
> Everything else was forged, spoofed, or unintelligble.
>
> I was probably not filtering off traffic from you (for any value of
> "you"), I was filtering off stuff with your IP address in it.
I
On Fri, 2003-12-05 at 16:05, Laurence F. Sheldon, Jr. wrote:
> Everything else was forged, spoofed, or unintelligble.
>
> I was probably not filtering off traffic from you (for any value of
> "you"), I was filtering off stuff with your IP address in it.
I was not aware one can fake everything
[EMAIL PROTECTED] writes on 12/5/2003 7:24 PM:
did not even record whey thy blocked him. Not only should they have recorded
it but perhaps had a location where Tom could find that:
1. He's being blocked
2. Why he is being blocked with particular example of abuse that caused it
3. How long will
I think part of the problem is not only to notify but provide information
for techs at another ISP to know what kind of problem they have (and if
you block them, they may not be able to reach you to even ask).
I would remind that this thread started from Tom telling us that roadrunner
did not
james wrote:
>
> : > I may be reaching here but I think perl scripting can do this.
> :
> : I wish. I've been experimenting with doing exactly that for years.
>
> That is what I ment by "reaching", it was not intended to be a smart a** comment.
> How about mailing to abuse/postmaster@ ? I real
On Fri, 5 Dec 2003, james wrote:
> To me the important thing is at least trying to notify.
> So the clueless miss out. Tuff. Those of us that care would like to know
> there is a problem, so we can solve it.
Thank you James, thats my point exactly :)
The people who care or have a clue will have
: > I may be reaching here but I think perl scripting can do this.
:
: I wish. I've been experimenting with doing exactly that for years.
That is what I ment by "reaching", it was not intended to be a smart a** comment.
How about mailing to abuse/postmaster@ ? I realize that the postmaster/
james wrote:
: When you're introducing thousands of IP blocks per day, it's pretty hard
: to notify them all.
I may be reaching here but I think perl scripting can do this.
I wish. I've been experimenting with doing exactly that for years.
Problems:
- WHOIS data is often incomplete, w
On Fri, 05 Dec 2003 14:30:57 MST, james <[EMAIL PROTECTED]> said:
> : When you're introducing thousands of IP blocks per day, it's pretty hard
> : to notify them all.
> I may be reaching here but I think perl scripting can do this.
Yes, a perl script can send thousands of warning e-mails to bogu
On Fri, 5 Dec 2003, Laurence F. Sheldon, Jr. wrote:
> A reasonable reaction to protect own-turf is to plug up holes as
> you identify the local end of it and wait to see if anybody cares
> about it after the fire-fight.
So block a /30, not a /24
> The likelyhood of being able to contact anybody
"Tom (UnitedLayer)" wrote:
>
> So, I got an e-mail back from RR after I posted here.
> They claim to have no specific record of why we were blocked, so they
> removed it. They said it was probably DOS or a Mailbomb, both of which we
> would have squelched IMMEDIATELY.
>
> Frankly, I think that i
: When you're introducing thousands of IP blocks per day, it's pretty hard
: to notify them all.
I may be reaching here but I think perl scripting can do this.
James Edwards
Routing and Security
[EMAIL PROTECTED]
At the Santa Fe Office: Internet at Cyber Mesa
Store hours: 9-6 Monday through F
Tom (UnitedLayer) wrote:
Frankly, I think that its pretty poor practice to block someone and not
tell them, especially when contact information is clearly available
everywhere. We've got e-mail, various phones, and INOC-DBA, so its not
that hard to get ahold of us :)
When you're introducing thou
So, I got an e-mail back from RR after I posted here.
They claim to have no specific record of why we were blocked, so they
removed it. They said it was probably DOS or a Mailbomb, both of which we
would have squelched IMMEDIATELY.
Frankly, I think that its pretty poor practice to block someone a
I need to speak with someone at RR about blocking issues.
Apparently they've decided to block mail from Apache.org and some of our
other customers without any notice to UL.
I've followed their instructions and e-mailed the listed addresses,
I've waited quite a while (over 24 hours) and have yet t
//Second posting//
Good evening all, anyone have a good contact for AOL (ATDN) engineers?
Having a problem with users on a /17 getting mail there, checked for
blackholes on my end, would like to know if my routes are being
null0'd.
TIA
J. Oquendo
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
http://info.us.bb.verio.net/vrr.html
On Tue, Nov 11, 2003 at 12:47:57PM -0800, [EMAIL PROTECTED] wrote:
>
>
> I need to give somebody contact for verio routing database to have several
> of the database entries removed from there (they have beenadded without
> consent of ip block administrat
I need to give somebody contact for verio routing database to have several
of the database entries removed from there (they have beenadded without
consent of ip block administrator and he does not want them there).Who
would the be correct person to contact at verio?
--
William Leibzon
Elan N
Could someone from Road runner contact me off list please?
This is for a routing issue.
Jeffrey Sharpe
CyberLynk Helpdesk and Support
414.858.9335 or 800.942.8022
[EMAIL PROTECTED]
I am seeking a contact at Everyone Internet (EV1.NET) who can address a
routing problem at EV1's borders that is causing our users to be unable to
reach many popular sites hosted there, or that have DNS servers there.
We've tried contacting them by telephone, only to be referred to
[EMAIL PROTE
Can someone with a clue in ChoiceOnes IP operations contact me off list
please.
--
Robert Blayzor, BOFH
INOC, LLC
[EMAIL PROTECTED]
PGP: http://www.inoc.net/~dev/
Key fingerprint = A445 7D1E 3D4F A4EF 6875 21BB 1BAA 10FE 5748 CFE9
Quality assurance: A way to ensure you never deliver shoddy good
29 matches
Mail list logo
