Re: Dead Links???

Robert Williams wrote:
> Where do we report dead links?

This subject is a routing issue;  but the purpose of the routing ng is
for someone who has researched a routing issue to present an argument or
case for a different notify than that which would pertain by the normal
SC notify derivation or different from what has been entered manually
into the routing db.

> I reported a SPAM e-mail and received
> an e-mail from that domain's System Administrator stating that the
> e-mail wasn't deliverable.

In spite of all that you have posted here, what is going on at wanadoo's
end isn't altogether apparent.

The basics of this are that a userIP 82.122.118.211 rDNS
ANice-252-1-24-211.w82-122.abo.wanadoo.fr of Wanadoo France was a
spamsource -- and indeed it is multilisted as spamsource and
proxytrojan.

The further basics are that the ripe derived and abuse.net notifies are
[email protected] AND [email protected] for not only the /24
82.122.118.0 - 82.122.118.255 -- but also the 82.122.0.0/16 ie AS3215

The further experience is that SC notifies to the pm bounce a lot, 205
sent : 103 bounces, [meaning of 308, 103 bounced] so SC uses a devnull
handling to the pm and sends its notify to the abuse username.

Of the information which you were provided in the bounce, one particle
is the reportid 1558650829.

That reportid 'belongs' to you and only to you.  If you use it with
sufficient skill, you would be able to see the item, its parsing, and
its reporting.  No one else can see that but you, but you could use it
to derive a tracker link which /would/ show us all that.  The point of
that is that if I or someone would see the parsing reporting
information, the most likely thing they would see would be that the
report was sent to abuse at wanadoo and the pm devnull addy.

What you posted here was a failure of a notify to abusecyrus.

My guesswork so far indicates that no notify was sent to abusecyrus;  so
my further guesswork and supposition is that mail to abuse is either
copied or redirected to abusecyrus by an internal and unseen wanadoo
process not reflected in all of what you posted here.

So, then the question comes down to whether or not anyone here 'cares'
whether or not wanadoo can be notified better or not -- that is, does
anyone care to develop a better abuse notify for wanadoo.fr than that
which is existent

I for one do not.  Wandoo is a huge .fr provider and has a
responsibility to look after its abuse addresses.  I don't think SC has
some kind of special obligation to ferret out some 'alternate' address
if some of wanadoo's 'manufactured' notifies go astray because of
wanadoo's handling.

In this type of case, having a mail to a different address than was
emailed to have delivery trouble doesn't strike me as needing to be
fixed.


-- 
Mike Easter
kibitzer, not SC admin