348622 - abricoo1102.tempdomainname.com[161.58.163.41] is "blacklisted" on smtp.osuosl.org

Status: RESOLVED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Matthew Gertner]

Every time I send a mail to the mozilla.org domain, it bounces back with the following:

The original message was received at Mon, 14 Aug 2006 11:21:07 -0600 (MDT)
from 81.104.95.80.ip.b26.cz [80.95.104.81]

   ----- The following addresses had permanent fatal errors -----
<[e-mail]>
    (reason: 554 <abricoo1102.tempdomainname.com[161.58.163.41]>: Client host rejected: Access denied)

   ----- Transcript of session follows -----
... while talking to smtp.osuosl.org.:

>>>>>> DATA

<<< 554 <abricoo1102.tempdomainname.com[161.58.163.41]>: Client host rejected: Access denied
554 5.0.0 Service unavailable
<<< 554 Error: no valid recipients

Mails to mozilla.com work fine. I guess our mail server is blacklisted on mozilla.org.

Comment 1

[chizu]

It looks like 161.58.163.41 was blacklisted by http://moensted.dk/spam/no-more-funn/. It's been taken off the list. Can you see if this has fixed the issue for you?

Comment 2

[Jeremy Orem [:oremj]]

Assumed fixed, please reopen if this happens again.

Comment 3

[Matthew Gertner]

Just tried again and got the same bounce back message.

Comment 4

[chizu]

161.58.163.41 seems to have been readded to that blacklist. Is this your own mailserver? If not, I would suggest sending via another SMTP server. If it is, you should either forward through another SMTP server (such as your ISP probably provides) or remove it from lists like http://moensted.dk/spam/no-more-funn/ by fixing whatever is causing it to become blacklisted in the first place.

Comment 5

[Mike Shaver (:shaver emeritus)]

Why do we honour that blacklist for mozilla.org?  Can we just turn that off, given the false positives here?

Comment 6

[Justin Fitzhugh]

I'm not sure that is the right solution - has the user tried to get off the black list or correct the issue (possible relaying)?  Usually there is a reason they are on these lists, and we don't want to accept mail from someone who is on them for a valid reason.  

If this is a true case of false positive, then we can look at that but I'd like to verify there isn't a valid reason for the host being on the blacklist first.  The "tempdomainname.com" doesn't inspire confidence either :-)

Comment 7

[Mike Shaver (:shaver emeritus)]

Well, we _are_ accepting mail from this relay when addressed to mozilla.com, so I don't understand why we wouldn't do the same for mail to the mozilla.org addresses as well.

Previous comments outline the removal from the blacklist in question, and then some subsequent re-adding.  It's not clear that the reporter has any control over the server in question.  (I've had bad experiences in the past in which my entire class C was blacklisted because someone else at the rent-a-racked-box provider was naughty, though that's not necessarily the case here.)

Comment 8

[Dave Miller [:justdave]]

(In reply to comment #7)
> Well, we _are_ accepting mail from this relay when addressed to mozilla.com,
> so I don't understand why we wouldn't do the same for mail to the mozilla.org
> addresses as well.

We have very little control over the mozilla.com email handling.  It's handled by a third party email hosting company.

Comment 9

[Corey Shields [:cshields]]

From looking at the transcript it looks as if your MTA is trying to pipeline without "discussing" the option with our MTA first.  We deny this (postfix reject_unauth_pipelining) since it is a typical spam app move.  Most spam applications don't care what the server is, what it's capabilities are, or even if it is a legit server..  just connect, fire, and go.

-C

Comment 10

[Justin Fitzhugh]

Per comment #9, this is an issue with the mail server in question - closing wontfix.

Comment 11

[Justin Fitzhugh]

Heh - right after I did this OSL found that this hostname "tempdomainname.com" was  blacklisted sometime a long time ago.  OSL is removing this, so this should be "Fixed".