Our system is built to minimize any potential abuse.
We constantly monitor
all incoming and outgoing email activities. We do not allow open relay. We do not allow
a user to send more than 20 mails per hour. We do not even favor a message to have more
than 5 recipients. Neither do we allow any individual to use our service to
collect the response mails from unsolicited advertising.
We are strongly opposed to any kind of spamming practice. Our policy is that if any violation, if any user directly or indirectly involved with unsolicited email spamming, the account would be closed immediately without prior notice. We truly appreciate the spamming report when an account on our server is involved with unsolicited commercial emails. We are very serious about it and take immediate action once receiving the report.
However, most of the time, the spamming is not related to our service. The spammer may merely place an email address (either @yifan.net, or at other email services) as a From, or Reply-To, or Return-Path addresses to divert the recipeint's attention, or even intended to direct the spamming victims to complain on the irrelevant sites, while sending the unsolicited mails from somewhere else.
The email address appeared on the sender info may be just a fake. Report the spamming to all sites appearing on the spamming mail may help those sites to kick out the individual from their services (if the account does exists), but chance is little to actually stop the spamming. To effectively stop the spammer, the most important thing is to trace which site delivers the mail to you (and probably where it is originated). It may not be straightforward to track the origination. But it should be relatively simple (and more reliable) to find out where you receive the junk mail from. Following is a sample mail header involved in a spamming:
One must look at the 'Received: from' lines one by one (top down) to trace the origination or at least the final relay server (the first 'Received: from' on the headers) (in this case, cliff.edw2.uc.edu [10.72.1.232]) that delivers it. Then report to the administrator of this relay server and ask the administrator to further trace it if the spamming is not originated from his/her server.
The IP address is more reliable than the domain name. If the IP and the domain do not match (it happens most often in spamming practice), it would be obvious the server associated with the given domain is not directly involved with the spamming, and the report had better go to the administrator who manages the listed IP block. Only doing so may the spamming be effectively stopped.
Otherwise, if solely reporting to yifan.net or yahoo.com, the only thing they could do is to close the accounts of jimmy20022@yifan.net or jerry20022@yahoo.com if they do exists. The spamming would go on. This is simply because the server that is used for the spamming is completely unrelated with either yifan.net or yahoo.com and it may still be hiding somewhere and doing the damage.
We are strongly opposed to any kind of spamming practice. Our policy is that if any violation, if any user directly or indirectly involved with unsolicited email spamming, the account would be closed immediately without prior notice. We truly appreciate the spamming report when an account on our server is involved with unsolicited commercial emails. We are very serious about it and take immediate action once receiving the report.
However, most of the time, the spamming is not related to our service. The spammer may merely place an email address (either @yifan.net, or at other email services) as a From, or Reply-To, or Return-Path addresses to divert the recipeint's attention, or even intended to direct the spamming victims to complain on the irrelevant sites, while sending the unsolicited mails from somewhere else.
The email address appeared on the sender info may be just a fake. Report the spamming to all sites appearing on the spamming mail may help those sites to kick out the individual from their services (if the account does exists), but chance is little to actually stop the spamming. To effectively stop the spammer, the most important thing is to trace which site delivers the mail to you (and probably where it is originated). It may not be straightforward to track the origination. But it should be relatively simple (and more reliable) to find out where you receive the junk mail from. Following is a sample mail header involved in a spamming:
Return-Path: <jimmy20022@yifan.net>
Received: from cliff.edw2.uc.edu (cliff.edw2.uc.edu [10.72.1.232])
by email.edw2.uc.edu (8.9.2/8.9.2) with ESMTP id WAA08995
for ; Mon, 18 Mar 2002 22:10:01 -0500 (EST)
From: jimmy20022@yifan.net
Received: from blues.fd1.uc.edu (jazz.san.uc.edu [10.97.6.152])
by cliff.edw2.uc.edu (8.9.2/8.9.2) with ESMTP id WAA30501
for ; Mon, 18 Mar 2002 22:01:15 -0500 (EST)
Received: from mail.gmf.co.kr (root@[211.63.199.58])
by BLUES.FD1.UC.EDU (PMDF V5.1-12 #D3948)
with SMTP id <01KFISAGXSWK95N7X0@BLUES.FD1.UC.EDU> for hagemabs@email.uc.edu;
Mon, 18 Mar 2002 22:03:23 EST
Received: from 202.122.208.148
(host-216-78-120-95.sav.bellsouth.net [216.78.120.95])
by mail.gmf.co.kr (8.9.3/8.9.3) with SMTP id TAA25826; Mon,
18 Mar 2002 19:11:03 +0900
Date: Mon, 18 Mar 2002 22:04:43 -0500
Subject: GET CASH, NO EQUITY REQUIRED! APPLY TODAY! 20402
To: Undisclosed.Recipients@mail.gmf.co.kr
Reply-to: jerry20022@yahoo.com
Message-id: <00002ddc356f$00000424$00004fb2@202.103.18.93>
Though jimmy20022@yifan.net appears as return path and from address, and jerry20022@yahoo.com as reply-to address,
reporting to yifan.net or yahoo.com would not stop the spamming. One must look at the 'Received: from' lines one by one (top down) to trace the origination or at least the final relay server (the first 'Received: from' on the headers) (in this case, cliff.edw2.uc.edu [10.72.1.232]) that delivers it. Then report to the administrator of this relay server and ask the administrator to further trace it if the spamming is not originated from his/her server.
The IP address is more reliable than the domain name. If the IP and the domain do not match (it happens most often in spamming practice), it would be obvious the server associated with the given domain is not directly involved with the spamming, and the report had better go to the administrator who manages the listed IP block. Only doing so may the spamming be effectively stopped.
Otherwise, if solely reporting to yifan.net or yahoo.com, the only thing they could do is to close the accounts of jimmy20022@yifan.net or jerry20022@yahoo.com if they do exists. The spamming would go on. This is simply because the server that is used for the spamming is completely unrelated with either yifan.net or yahoo.com and it may still be hiding somewhere and doing the damage.
กก
กก
|
|
|
|
Copyright
by Yifan, LLC. All rights Reserved.