This is the rudest, most arrogant abuse complaint I have seen. It is a
frigging dial up user.
james
I'm confused. Your user on 65.19.17.201 - a dialup user, probably
running an infected Windows box, sent spam to the complainant, who
figured out who to complain to, explained in great detail (and in
English) that well, it shouldn't have happened if you'd had any clue
whatsoever, and had blocked outbound port 25 connections from your own
users (or at the very least those users of yours who are listed in
DNSBLs for spamming or relaying!) and you think he's being /arrogant/?
Christ, I'd say he's being helpful.
Get over yourself and /fix your own network/. Deal with the frigging
complaint, and STFU.
I already waste /way/ too much time dealing with equally stupid and/or
lazy network/mail admins who won't frigging fix their own networks, and
doesn't blame the complainant one frigging bit. Currently, I'm dealing
with the backscatter bounces from three concurrent joe jobs, sent by
such laughably broken spamware that I'm /amazed/ any of it was accepted
in the first place, much less accepted and /then backscattered to me,
the victim/ because of still more misconfigured/idiotic antivirus
stupidity.
Sheesh. Get over /yourself/. Your network is rude by its very existence,
if it lets spammers relay crud by way of it. Your own arrogance in
thinking it's not your problem to fix is astounding.
Please don't bother to reply; it will take time away from fixing your
network.
Steve
Sheesh. Get over /yourself/. Your network is rude by its very existence,
if it lets spammers relay crud by way of it. Your own arrogance in
thinking it's not your problem to fix is astounding.
I did no say it is not my problem, we have a 10 year history of being
very pro-active for all abuse issues and have a dedicated staff person to
deal with these issues. Slaming my mail admin because a dial up user has a
virus
is rude, period. Our dial up address space is listed, if people choose to
block
mail from that space.
james
> Sheesh. Get over /yourself/. Your network is rude by its very existence,
> if it lets spammers relay crud by way of it. Your own arrogance in
> thinking it's not your problem to fix is astounding.I did no say it is not my problem, we have a 10 year history of being
very pro-active for all abuse issues and have a dedicated staff person
to deal with these issues.
OK, then, perhaps you can explain why I have received backscatter from
web.cybermesa.com [65.19.6.7]
or why even though I got spam from
sf-du170.cybermesa.com [209.12.75.170]
back in October 2001, and from
sf-du201.cybermesa.com [209.12.75.201]
in February 2002, you still haven't blocked outbound port 25 traffic from
those obviously vulnerable hosts?
Looks like you've got an ongoing problem with those dialup ranges.
Slaming my mail admin because a dial up user has a virus is rude,
period.
Nope. Sorry. Emitting spam/viruses or backscatter even though you know
you (or your users) have a problem, expecting everyone else to block
your network, and whining when someone has the gall to call you on it -
that's rude.
Of course, it's pretty common, but that doesn't make it any less rude.
Our dial up address space is listed, if people choose to block mail
from that space.
I'm curious - where is it listed? I don't see anything on your Web site
that even suggests a place to go looking for abuse/helpdesk/support
info. Much less a banner inviting more responsible mail admins to block
your listed netblocks....
Will a regex of [a-z]+[0-9]*\-du[0-9]+\.cybermesa\.com block all of
your dialup ranges by rDNS? What about your DSL and ISDN ranges? How
are they named? Consistently, I hope. And of course I also hope they
resolve back-and-forwards to the IP, so spam/viruses don't squeak through
sendmail due to being "possibly forged".
Why aren't they named so that sendmail and other MTAs can block your
dynamic ranges by RHS in access.db, instead of having to use regexes?
Hint: blah-1-2.dynamic.cybermesa.com or blah-3.4.dialup.cybermesa.com
or foo-5-6-7-8.dsl.cybermesa.com makes this much less annoying and
difficult, and conveys the same information as sf-du120.cybermesa.com.
I apologize if I offended you personally, I intended to do it professioanlly.
Steve
Listed where? I don't see it jumping out anywhere on your web site or in
any common/free DNSBL and the way your rDNS is setup isn't doing anyone
any favors.
201.10.19.65.in-addr.arpa name = albq-du201.cybermesa.com.
201.16.19.65.in-addr.arpa name = sf-du201.cybermesa.com.
The more primitive MTAs need you do be doing something like
albq-201.du.cybermesa.com. Then they can be setup to reject
du.cybermesa.com, which will reject .*\.du\.cybermesa\.com.
And if you think their message was rude, just try to imagine the crap
people send _to_ DNSBLs. It makes the message from the Swedes seem like
they were kissing your @$$.
Listed where? I don't see it jumping out anywhere on your web site or in
any common/free DNSBL and the way your rDNS is setup isn't doing anyone
any favors.
We were a MAPS customer/user for a number of years and were listed then and
I see we are not now.
We will be listed again, shortly.
james