Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

backscatterer block right DSN

10 views
Skip to first unread message

fuimar

unread,
Aug 20, 2008, 1:13:30 PM8/20/08
to
In compliance with RFC, we configured mailserver to generate DSN tout-
court, but these emails are identified as bad email.

see log:

20080801 15:27:17 48297F2104F6C027 QUEUE From=<> Size=2177 Relay=Local
20080801 15:27:17 48297F2104F6C027 QUEUE
Recipient=<dwtop...@topserv.ch>
20080801 15:27:17 48297F2104F6C027 QUEUE Message-
ID=<48297F21...@mail1.netscalibur.it>
20080801 15:27:17 48297F2104F6C027 QUEUE Subject=Delivery Status
Notification
20080801 15:27:17 48297F2104F6C027 SMTP opened connection to
'mail1.itris.ch' IP 212.243.137.72
20080801 15:27:18 48297F2104F6C027 SMTP RCPT
TO:<dwtop...@topserv.ch> got reply '571 Access denied and
blocklisted: 990 (V4.07-RULE-0207) Backscatter is abusive. Visit
http://www.backscatterer.org/ to find out how to fix your problem.'
20080801 15:27:18 48297F2104F6C027 DSN For=<dwtop...@topserv.ch>
Suppressed - No envelope originator


20080812 13:53:21 48297F2105AF44D2 QUEUE From=<> Size=2305 Relay=Local
20080812 13:53:21 48297F2105AF44D2 QUEUE
Recipient=<linanger...@angermeier.de>
20080812 13:53:21 48297F2105AF44D2 QUEUE Message-
ID=<48297F21...@mail1.netscalibur.it>
20080812 13:53:21 48297F2105AF44D2 QUEUE Subject=Delivery Status
Notification
20080812 13:53:22 48297F2105AF44D2 SMTP opened connection to 'post.spv-
server.de' IP 217.23.49.197
20080812 13:53:22 48297F2105AF44D2 SMTP RCPT
TO:<linanger...@angermeier.de> got reply '571 Access denied and
blocklisted: 990 (V4.07-RULE-0207) Backscatter is abusive. Visit
http://www.backscatterer.org/ to find out how to fix your problem.'
20080812 13:53:22 48297F2105AF44D2 DSN
For=<linanger...@angermeier.de> Suppressed - No envelope
originator

In other words, we have configured our mail server in this way, as
suggested also by our supplier, to avoid DSN loop, and from our point
of view this is not a valid reason to black list a mail server.

This configuration is allowed from all other black list.

If our blacklistation is dued to a bad role or a misconfiguration, we
kindly ask you to remove from you list our server 194.244.215.2.

Hoply in a your positive replay and to be useful indicating you a
probabily misconfiguration.

Best regards

--
Comments posted to news.admin.net-abuse.blocklisting
are solely the responsibility of their author. Please
read the news.admin.net-abuse.blocklisting FAQ at
http://www.blocklisting.com/faq.html before posting.

David W. Hodgins

unread,
Aug 20, 2008, 2:23:17 PM8/20/08
to
On Wed, 20 Aug 2008 13:13:30 -0400, fuimar <luca.m...@gmail.com> wrote:

> In compliance with RFC, we configured mailserver to generate DSN tout-
> court, but these emails are identified as bad email.

See section 1.5 of http://www.ietf.org/rfc/rfc2505.txt or read
http://www.backscatterer.org/?target=backscatter

Accepting an email for delivery, and then generating a DSN to a forged
from address is abusive.

If the email cannont be delivered, reject it during the smtp layer.

> TO:<dwtop...@topserv.ch> got reply '571 Access denied and
> blocklisted: 990 (V4.07-RULE-0207) Backscatter is abusive. Visit
> http://www.backscatterer.org/ to find out how to fix your problem.'

If a spammer starts using your addresses in your domain, as the forged
from address, you'd appreciate having a list like backscatterer, so you
could block the incoming flood of DSN messages.

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Shmuel (Seymour J.) Metz

unread,
Aug 21, 2008, 2:04:28 PM8/21/08
to
In <f6bf2802-4b52-4b1c...@x41g2000hsb.googlegroups.com>, on
08/20/2008
at 05:13 PM, fuimar <luca.m...@gmail.com> said:

>In compliance with RFC,

RFC 2821 does not require you to give a 250 response to a bad e-mail; it
only allows it. Just as it allows open relays, which will also get you
labelled as a spam facilitator.

>we configured mailserver to generate DSN tout-court,

That would be okay if you only sent the DSN's to authenticated reverse
paths, but since you also send them to bogus addresses, they're spam.

>but these emails are identified as bad email.

Quite properly.

>TO:<dwtop...@topserv.ch> got reply '571 Access denied and blocklisted:
>990 (V4.07-RULE-0207) Backscatter is abusive. Visit
>http://www.backscatterer.org/ to find out how to fix your problem.'

Why didn't you visit the web site.

>In other words,

No. That;s not what they said.

>we have configured our mail server in this way, as
>suggested also by our supplier, to avoid DSN loop,

How does sending an inappropriate 250 avoid a loop?

>and from our point
>of view this is not a valid reason to black list a mail server.

Then don't block sources of outscatter. Your servers, your rules. Your
point of view, however, is irrelevant to those rejecting your mail.

>This configuration is allowed from all other black list.

Untrue.

>If our blacklistation is dued to a bad role or a misconfiguration, we
>kindly ask you to remove from you list our server 194.244.215.2.

It's due to a miosconfiguration of *your* server.

--
Shmuel (Seymour J.) Metz, truly insane Spews puppet
<http://patriot.net/~shmuel>

I reserve the right to publicly post or ridicule any abusive
E-mail. Reply to domain Patriot dot net user shmuel+news to contact
me. Do not reply to spam...@library.lspace.org

0 new messages