-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 25 Apr 2003 08:43:08 +0800, Ladislav Bodnar wrote: > I live in Asia (and have a dynamic IP assigned to me > by my ISP) and I find that an increasing number of my emails don't reach > their destinations. > > Yes, Asian spam is annoying, but if I look in my inbox, a good 90% of it still > originates in the US. Asia *is* the major source of SPAM/UCE. In your case, thank all those customers of HiNet who abuse the network and flood it with SPAM or who run open relays and insecure machines that are abused. Blame your provider for not taking proper action upon receiving abuse reports (HiNet have got many abuse notifications from me, too, in the past). It can't be repeated often enough -- whether it applies in this case or not -- a common misconception about the origin of SPAM/UCE mail is due to the recipient not reading the message headers correctly. The used e-mail sender address can be chosen arbitrarily. Often the spammer just uses a domain name like @excite.com or @yahoo.com, which does exist, but a mail address which does not exist. The language which is used in the message doesn't count either. English SPAM is posted from hosts in .cn, .tw, .kr, or .br (.telesp.br increasingly popular) as well as German SPAM or Asian SPAM. I'd like to point out that it is incredibly stupid to send me content which I cannot even read. Faked host names that are used as a greeting during contact with the first mail server, are another source of confusion. The real IP address often is in brackets. If you want to find out from where a message was sent, rely on IP addresses and the "whois" or "awhois" utility. Don't rely on what looks like valid host names. My mailbox at Yahoo!Mail receives 6-7 MiB of unsolicited commercial e-mail in just a few days. A lot of the SPAM has been from Taiwan, Korea, China, Brazil, but also England (NTL is getting popular, probably open relays on cable modem). That fills the mailbox quickly. Once it's filled, no one of the spammers cares about the bouncing messages. They don't even see the bouncing messages, since they don't use valid return addresses. - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+qRCW0iMVcrivHFQRAlRzAJ4qxop86r2EUVr18rHlyM/zElZenACffOD0 GKlvenEtStJK/SB6LCih1Bs= =NJdo -----END PGP SIGNATURE-----
