※ 필수입력정보 ※

▷ 제품버젼 : Nmail ASP 3.8

▷ 오류발생 메뉴/주소 :

▷ 에러메세지 :

▷ 질문내용 :

http://www.spamhaus.org/query/bl?ip=61.33.146.200

61.33.146.200 is not listed in the SBL

61.33.146.20 is listed in the PBL, in the following records:

• PBL358918
  

61.33.146.200 is not listed in the XBL

에 대하여 해지를 신청하였고 확인을 하였는데, 이직 정상적인 동작이 되고 있지 않습니다.

정품사용자 인데요 이럴때는 어떻게 해야하나요?

>>>>>>>>>>>>>>>>>>>>>>>>> 블럭리스트 상세내용

Ref: PBL358918

61.33.0.0/16 is listed on the Policy Block List (PBL)

Outbound Email Policy of The Spamhaus Project for this IP range:

This IP range has been identified by Spamhaus as not meeting our policy for IPs permitted to deliver unauthenticated 'direct-to-mx' email to PBL users.

Important: If you are using any normal email software (such as Outlook, Entourage, Thunderbird, Apple Mail, etc.) and you are being blocked by this Spamhaus PBL listing when you try to send email, the reason is simply that you need to turn on "SMTP Authentication" in your email program settings. For help with SMTP Authentication or ways to quickly fix this problem click here.

See also: http://www.spamhaus.org/faq/answers.lasso?section=Spamhaus%20PBL

Removal Procedure

If you are not using normal email software but instead are running a mail server and you are the owner of a Static IP address in the range 61.33.0.0/16 and you have a legitimate reason for operating a mail server on this IP, you can automatically remove (suppress) your static IP address from the PBL database.

블럭리스트 해지후 메일 리턴결과

Error Message : 421 4.3.2 Your ip is filtered by RBL (http://realip.naver.com/rbl/rblinfo.html)(IP:61.33.146.200)(Caues:http://www.spamhaus.org/query/bl?ip=61.33.146.200) [****@****]

-- You SendMail --

>> Received: from mail.ilya.co.kr (61.33.146.200)
>> by ilya.co.kr (61.33.146.200) with [Nmail V3.8 20071121(ST)]
>> for <****@****>from <****@****>;
>> Tue, 02 Feb 2010 11:25:55 +0900
>> From: =?ks_c_5601-1987?b?tOu9xSi43sDPwaGwyyk=?= <****@****>
>> Subject: test
>> To: <****@****>,
>> <****@****>
>> MIME-Version: 1.0
>> X-Mailer: SM
>> Date: Tue, 02 Feb 2010 11:25:55 +0900
>> Content-Type: text/html; charset=euc-kr
>> Content-Transfer-Encoding: base64