This might have something to do with a server that I have set the root user with a forward rule to send me emails. But I am not sure and I can't figure out why... Is it possible that my server has been used by other people to do spamming? My server is in a local network by the way.
Based on the returned content of the email, it's for several spam emails. Pure spam. And the sender is not even ME, not even a proper address (some random name). That's why I think it feels like someone seems relaying emails (spam) through my server. And I got all the returned emails back. My email server (a very good company) didn't treat this as spam. They normally help me block tons of spam automatically.
The original message was received at Sun, 26 Jan 2014 05:05:40 -0700 from m50-134.163.com [126.96.36.199] ----- The following addresses had permanent fatal errors ----- <email@example.com> (reason: 550-5.1.1 The email account that you tried to reach does not exist. Please try) ----- Transcript of session follows ----- ... while talking to aspmx.l.google.com.: >>> DATA <<< 550-5.1.1 The email account that you tried to reach does not exist. Please try <<< 550-5.1.1 double-checking the recipient's email address for typos or <<< 550-5.1.1 unnecessary spaces. Learn more at <<< 550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 ha7si10821727icc.12 - gsmtp 550 5.1.1 <firstname.lastname@example.org>... User unknown <<< 503 5.5.1 RCPT first. ha7si10821727icc.12 - gsmtp
priearl2003 is the spammer I think.
Content-Type: Message/delivery-status Content-Description: Delivery error report Final-Recipient: rfc822; email@example.com Action: failed Status: 5.0.0 Diagnostic-Code: SMTP; SMTP error, DOT: 550 5.7.0 (SNT0-MC4-F26) Message could not be delivered. Please ensure the message is RFC 5322 compliant..(SMTP error, DOT: 550 5.7.0 (SNT0-MC4-F26) Message could not be delivered. Please ensure the message is RFC 5322 compliant.) --------------Boundary-00=_MQ805PDL3A1S4OLBH890 Content-Type: Message/Rfc822 Content-Description: Undelivered Message Content-Transfer-Encoding: 8bit Received: from mycomputer (unknown [188.8.131.52]) by smtp4 (Coremail) with SMTP id DtGowECZB0Ue6ORSchJSDQ--.24287S3; Sun, 26 Jan 2014 18:49:20 +0800 (CST) From: "markp markp" <priearl2003> To: "keacyking" <firstname.lastname@example.org>, "KC" <email@example.com>, "sexy kio kyle hot7187493825" <firstname.lastname@example.org>, "rod isreal" <email@example.com>, "korey 3369724167" <firstname.lastname@example.org>, "junglefever 04" <email@example.com>, "Keino" <firstname.lastname@example.org>, "Y U WANNA KNOW autour detroit" <email@example.com>, "Kennen butler buffalo" <firstname.lastname@example.org>, "=?ISO-8859-1?Q?Charles_Knowles=2C_Jr?=" <email@example.com> Subject: markp markp Date: Sat, 26 Jan 2014 11:49:14 +0100 MIME-Version: 1.0 X-mailer: Microsoft Office Outlook, Build 11.0.5510 Reply-To: priearl2003 Content-type: Multipart/mixed; boundary="3E762EB7_62CA3E41_boundary" Content-Description: Multipart message X-CM-TRANSID:DtGowECZB0Ue6ORSchJSDQ--.24287S3 X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UbIYCTnIWIevJa73UjIFyTuYvjxUa038UUUUU X-Originating-IP: [184.108.40.206] --3E762EB7_62CA3E41_boundary Content-type: text/html; charset=UTF-8 Content-Transfer-Encoding: Quoted-printable Content-Disposition: inline Content-Description: HTML text =EF=BB=BF<html><head><meta http-equiv=3D"content-type" content: text/html;= charset= =3DUTF-8></head><body>http://atasehiringilizcekurslari.org/vhwk/jgmbsvgubadcgt= ecpios.dcgpurxvlyoigqhfjgxeg</body></html> --3E762EB7_62CA3E41_boundary--