Advertisement
Guest User

Untitled

a guest
May 16th, 2016
136
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.47 KB | None | 0 0
  1. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  2. Customer's query:
  3.  
  4. As for email forwarder - kstan@hextar.com <mailto:kstan@hextar.com> either me nor Kenny didn’t create it as no one have the cpanel username & password. Only me and Kenny have it. If Kenny create any of the forwarder, he will inform me. Our cpanel password is secure with us as we don’t give it to anyone of them. Therefore kstan@hextar.com <mailto:kstan@hextar.com> forwarder is legit.
  5.  
  6. By the way, kstan@hextar.com <mailto:kstan@hextar.com> does not have email account how this email can be send out by itself?
  7.  
  8. This not the first time happens. It happen few times already till very boss very frustrated. I still think the new VPS is having problem. Maybe you take a look into the new VPS.
  9. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  10. Our Engineer's Answer;
  11.  
  12. Dear Joyce,
  13.  
  14. An email forwarder doesn't need an account. It just an alias email address that will auto forward any emails destined to kstan@hextar.com to another valid email address. In this case would be:
  15.  
  16. kstan@hextar.com >forward to> kenny.tan@hextar.com
  17.  
  18. kenny.tan@hextar.com must a valid email account.
  19.  
  20. Following are the exim_maillog by locate the said email account
  21.  
  22. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
  23. # more /var/log/exim_mainlog | grep 1b0V1P-0004AZ-H7
  24. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 H=([89.36.179.178]) [89.36.179.178]:21685 Warning: "SpamAssassin as hextarc detected message as NOT spam (2.4)"
  25. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 <= kstan@hextar.com H=([89.36.179.178]) [89.36.179.178]:21685 P=esmtp S=7205 id=2c0b9a8ebd09$27b6aee06bb4069eb$@hextar.com T="Emailing: Photo 05-11-2016, 77 11 75" for kstan@hextar.com
  26. 2016-05-11 22:22:01 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1b0V1P-0004AZ-H7
  27. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 => kenny.tan (kstan@hextar.com) <kstan@hextar.com> R=virtual_user T=virtual_userdelivery
  28. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 Completed
  29. #
  30. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  31.  
  32. From this logs, it show the email was sent from 89.36.179.178 to kstan@hextar.com. As kstan@hextar.com is just an email forwarder, exim then will automatically forward the email to kenny.tan - denoted by this - kenny.tan (kstan@hextar.com)
  33.  
  34. You should remove the forwarder kstan@hextar.com as soon as possible if you think this forwarder should NOT be there.
  35.  
  36. Thank you.
  37.  
  38. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  39.  
  40. Customer's reply;
  41.  
  42. upport,
  43.  
  44.  
  45.  
  46. We are aware of the function of forwarder. The forwarder for kstan@hextar.com to kenny.tan@hextar.com is indeed created by me. What we need to find out is how can kstan@hextar.com SEND an email out WITHOUT having an account created in the Server. The email header below is what I capture for your investigation. Please provide your investigation report. If the server is having problem please rectify it ASAP!
  47.  
  48.  
  49.  
  50. Return-path: < <mailto:kstan@hextar.com> kstan@hextar.com>
  51.  
  52. Envelope-to: <mailto:kstan@hextar.com> kstan@hextar.com
  53.  
  54. Delivery-date: Wed, 11 May 2016 22:22:01 +0800
  55.  
  56. Received: from [89.36.179.178] (port=21685)
  57.  
  58. by mail.hextar.com with esmtp (Exim 4.85)
  59.  
  60. (envelope-from < <mailto:kstan@hextar.com> kstan@hextar.com>)
  61.  
  62. id 1b0V1P-0004AZ-H7
  63.  
  64. for <mailto:kstan@hextar.com> kstan@hextar.com; Wed, 11 May 2016 22:22:01 +0800
  65.  
  66. From: < <mailto:kstan@hextar.com> kstan@hextar.com>
  67.  
  68. To: < <mailto:kstan@hextar.com> kstan@hextar.com>
  69.  
  70. Subject: Emailing: Photo 05-11-2016, 77 11 75
  71.  
  72. Date: Wed, 11 May 2016 18:51:50 +0430
  73.  
  74. Message-ID: < <mailto:2c0b9a8ebd09$27b6aee06bb4069eb$@hextar.com> 2c0b9a8ebd09$27b6aee06bb4069eb$@hextar.com>
  75.  
  76. MIME-Version: 1.0
  77.  
  78. Content-Type: multipart/mixed;
  79.  
  80. boundary="----=_NextPart_000_6303_43F2C1BC.5939F1B4"
  81.  
  82. X-Mailer: Microsoft Outlook 16.0
  83.  
  84. Content-Language: en-gb
  85.  
  86. X-Spam-Status: No, score=2.4
  87.  
  88. X-Spam-Score: 24
  89.  
  90. X-Spam-Bar: ++
  91.  
  92. X-Ham-Report: Spam detection software, running on the system "mail.hextar.com",
  93.  
  94. has NOT identified this incoming email as spam. The original
  95.  
  96. message has been attached to this so you can view it or label
  97.  
  98. similar future email. If you have any questions, see
  99.  
  100. root\@localhost for details.
  101.  
  102.  
  103.  
  104. Content preview: Your message is ready to be sent with the following file or
  105.  
  106. link attachments: Photo 05-11-2016, 77 11 75 Note: To protect against computer
  107.  
  108. viruses, e-mail programs may prevent sending or receiving certain types of
  109.  
  110. file attachments. Check your e-mail security settings to determine how attachments
  111.  
  112. are handled. [...]
  113.  
  114.  
  115.  
  116. Content analysis details: (2.4 points, 5.0 required)
  117.  
  118.  
  119.  
  120. pts rule name description
  121.  
  122. ---- ---------------------- --------------------------------------------------
  123.  
  124. 0.7 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail)
  125.  
  126. -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
  127.  
  128. [score: 0.0000]
  129.  
  130. 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS
  131.  
  132. 2.8 DOS_OUTLOOK_TO_MX Delivered direct to MX with Outlook headers
  133.  
  134. X-Spam-Flag: NO
  135. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  136.  
  137. OUr Engineer's reply;
  138.  
  139. Dear Kenny,
  140.  
  141. Following is the snippet from the exim maillogs for the said email.
  142.  
  143. # more /var/log/exim_mainlog | grep 1b0V1P-0004AZ-H7
  144. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 H=([89.36.179.178]) [89.36.179.178]:21685 Warning: "SpamAssassin as hextarc detected message as NOT spam (2.4)"
  145. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 <= kstan@hextar.com H=([89.36.179.178]) [89.36.179.178]:21685 P=esmtp S=7205 id=2c0b9a8ebd09$27b6aee06bb4069eb$@hextar.com T="Emailing: Photo 05-11-2016, 77 11 75" for kstan@hextar.com
  146. 2016-05-11 22:22:01 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc 1b0V1P-0004AZ-H7
  147. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 => kenny.tan (kstan@hextar.com) <kstan@hextar.com> R=virtual_user T=virtual_userdelivery
  148. 2016-05-11 22:22:01 1b0V1P-0004AZ-H7 Completed
  149. #
  150.  
  151. Based on this logs, the email coming from ip address 89.36.179.178 with the subject "Emailing: Photo 05-11-2016, 77 11 75". 89.36.179.178 might be sender's ip address or some unknown server's ip address. 89.36.179.178 may have bounced back to sender as no email user kstan@hextar.com in it. However, the sender has forged the email account (kstan@hextar.com) in his Outlook the Return Path as kstan@hextar.com. All mail servers will bounced back the email to what been stated in the Return Path. So 89.36.179.178 has proceeded send the email to the correct mail server - mail.hextar.com. Since kstan@hextar.com is just a forwarder address to kenny.tan, so exim (mail server) proceed forward the email to kenny.tan@hextar.com instead. The logs shown above, correspond the mail header which you have provided.
  152.  
  153. You may review the maillog at following path : /var/log/exim_mainlog
  154.  
  155. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
  156.  
  157. Our Customer's reply;
  158.  
  159. I understand your mail but my question here is we need to find out how can kstan@hextar.com SEND an email out WITHOUT having an account created in the Server? Because what I received is the mail from kstan@Hextar.com to kstan@Hextar.com <mailto:kstan@Hextar.com> . We want to know how kstan@hextar.com <mailto:kstan@hextar.com> sending out the email?
  160.  
  161. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement