YTH Pak Syafril
Mohon bantuan..
Pagi ini user kami menerima email dari kantor pusat, namun sayangnya
attachment file di remove oleh Mdaemon.
1. Apakah ada cara untuk meloloskan attachment tersebut?
2. Padahal user dari kantor pusat sudah men-zip file attachment
tersebut namun kenapa masih terhapus oleh Mdaemon ya Pak?
3. Apakah ada penampungan untuk file-file yang di hapus Mdaemon? Jika
ada bagaimana cara mengambil file-file tersebut Pak?
4. Bagaimana cara seting file-file apa saja dan kriteria apa saja yang
dapat di loloskan atau di block oleh Mdaemon?
Berikut log emailnya dan report penghapusan dari Mdaemon saya lampirkan juga
pada attachment file..
Mon 2017-01-23 08:19:54.562: 01: ----------
Mon 2017-01-23 08:16:34.165: 05: [306670] Session 306670; child 0001
Mon 2017-01-23 08:16:34.165: 05: [306670] Accepting SMTP connection from
[211.7.82.63:46978] to [202.78.202.4:25]
Mon 2017-01-23 08:16:34.166: 03: [306670] --> 220 mail.os-selnajaya.com
ESMTP Mon, 23 Jan 2017 08:16:34 +0700
Mon 2017-01-23 08:16:34.260: 02: [306670] <-- EHLO sptxg.gemini.oneoffice.jp
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250-mail.os-selnajaya.com
Hello sptxg.gemini.oneoffice.jp, pleased to meet you
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250-ETRN
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250-8BITMIME
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250-ENHANCEDSTATUSCODES
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250-STARTTLS
Mon 2017-01-23 08:16:34.260: 03: [306670] --> 250 SIZE 25600000
Mon 2017-01-23 08:16:34.354: 02: [306670] <-- STARTTLS
Mon 2017-01-23 08:16:34.354: 03: [306670] --> 220 2.7.0 Ready to start TLS
Mon 2017-01-23 08:16:34.550: 01: [306670] SSL negotiation successful (TLS
1.0, 3072 bit key exchange, 128 bit AES encryption)
Mon 2017-01-23 08:16:34.645: 02: [306670] <-- EHLO sptxg.gemini.oneoffice.jp
Mon 2017-01-23 08:16:34.645: 03: [306670] --> 250-mail.os-selnajaya.com
Hello sptxg.gemini.oneoffice.jp, pleased to meet you
Mon 2017-01-23 08:16:34.645: 03: [306670] --> 250-ETRN
Mon 2017-01-23 08:16:34.645: 03: [306670] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Mon 2017-01-23 08:16:34.645: 03: [306670] --> 250-8BITMIME
Mon 2017-01-23 08:16:34.645: 03: [306670] --> 250-ENHANCEDSTATUSCODES
Mon 2017-01-23 08:16:34.645: 03: [306670] --> 250 SIZE 25600000
Mon 2017-01-23 08:16:34.739: 02: [306670] <-- MAIL
FROM:<[email protected]> SIZE=2278852
Mon 2017-01-23 08:16:34.739: 05: [306670] Performing PTR lookup
(63.82.7.211.IN-ADDR.ARPA)
Mon 2017-01-23 08:16:34.758: 05: [306670] * D=63.0.82.7.211.IN-ADDR.ARPA
TTL=(1345) PTR=[sptxg.gemini.oneoffice.jp]
Mon 2017-01-23 08:16:34.758: 05: [306670] * Gathering A records...
Mon 2017-01-23 08:16:34.856: 05: [306670] * D=sptxg.gemini.oneoffice.jp
TTL=(4) A=[211.7.82.63]
Mon 2017-01-23 08:16:34.856: 05: [306670] ---- End PTR results
Mon 2017-01-23 08:16:34.857: 09: [306670] Performing SPF lookup
(outsourcing.co.jp / 211.7.82.63)
Mon 2017-01-23 08:16:34.945: 09: [306670] * Policy: v=spf1
include:gemini.oneoffice.jp ~all
Mon 2017-01-23 08:16:34.945: 09: [306670] * Evaluating
include:gemini.oneoffice.jp: performing lookup
Mon 2017-01-23 08:16:35.760: 09: [306670] * Policy: v=spf1
include:netblock.gemini.oneoffice.jp include:netblock.scorpio.oneoffice.jp
~all
Mon 2017-01-23 08:16:35.760: 09: [306670] * Evaluating
include:netblock.gemini.oneoffice.jp: performing lookup
Mon 2017-01-23 08:16:35.857: 09: [306670] * Policy: v=spf1
ip4:211.7.82.0/25 ~all
Mon 2017-01-23 08:16:35.857: 09: [306670] * Evaluating
ip4:211.7.82.0/25: match
Mon 2017-01-23 08:16:35.857: 09: [306670] * Evaluating
include:netblock.gemini.oneoffice.jp: match
Mon 2017-01-23 08:16:35.857: 09: [306670] * Evaluating
include:gemini.oneoffice.jp: match
Mon 2017-01-23 08:16:35.857: 09: [306670] * Result: pass
Mon 2017-01-23 08:16:35.857: 09: [306670] ---- End SPF results
Mon 2017-01-23 08:16:35.857: 03: [306670] --> 250 2.1.0 Sender OK
Mon 2017-01-23 08:16:35.954: 02: [306670] <-- RCPT
TO:<[email protected]>
Mon 2017-01-23 08:16:35.955: 05: [306670] Performing DNS-BL lookup
(211.7.82.63 - connecting IP)
Mon 2017-01-23 08:16:36.207: 05: [306670] * zen.spamhaus.org - passed
Mon 2017-01-23 08:16:36.207: 05: [306670] ---- End DNS-BL results
Mon 2017-01-23 08:16:36.208: 03: [306670] --> 250 2.1.5 Recipient OK
Mon 2017-01-23 08:16:36.301: 02: [306670] <-- RCPT
TO:<[email protected]>
Mon 2017-01-23 08:16:36.303: 03: [306670] --> 250 2.1.5 Recipient OK
Mon 2017-01-23 08:16:36.397: 02: [306670] <-- RCPT
TO:<[email protected]>
Mon 2017-01-23 08:16:36.399: 03: [306670] --> 250 2.1.5 Recipient OK
Mon 2017-01-23 08:16:36.491: 02: [306670] <-- DATA
Mon 2017-01-23 08:16:36.491: 01: [306670] Creating temp file (SMTP):
d:\mdaemon\queues\temp\md50001424237.tmp
Mon 2017-01-23 08:16:36.491: 03: [306670] --> 354 Enter mail, end with
<CRLF>.<CRLF>
Mon 2017-01-23 08:16:58.364: 01: [306670] Message size: 2278849 bytes
Mon 2017-01-23 08:16:58.366: 10: [306670] Performing DKIM lookup
Mon 2017-01-23 08:16:58.366: 10: [306670] * File:
d:\mdaemon\queues\temp\md50001424237.tmp
Mon 2017-01-23 08:16:58.366: 10: [306670] * Message-ID:
<[email protected]>
Mon 2017-01-23 08:16:58.366: 10: [306670] * Result: neutral
Mon 2017-01-23 08:16:58.366: 10: [306670] ---- End DKIM results
Mon 2017-01-23 08:16:58.368: 19: [306670] Performing DMARC processing
Mon 2017-01-23 08:16:58.368: 19: [306670] * File:
d:\mdaemon\queues\temp\md50001424237.tmp
Mon 2017-01-23 08:16:58.368: 19: [306670] * Message-ID:
<[email protected]>
Mon 2017-01-23 08:16:58.368: 19: [306670] * Author domain:
outsourcing.co.jp
Mon 2017-01-23 08:16:58.368: 19: [306670] * Organizational domain:
outsourcing.co.jp
Mon 2017-01-23 08:16:58.368: 19: [306670] * Query domain:
_dmarc.outsourcing.co.jp
Mon 2017-01-23 08:17:58.369: 04: [306670] * DNS: 60 second wait for DNS
response exceeded (DNS Server: 8.8.8.8)
Mon 2017-01-23 08:18:58.369: 04: [306670] * DNS: 60 second wait for DNS
response exceeded (DNS Server: 8.8.4.4)
Mon 2017-01-23 08:19:58.370: 04: [306670] * DNS: 60 second wait for DNS
response exceeded (DNS Server: 208.67.222.222)
Mon 2017-01-23 08:19:58.678: 19: [306670] * No DMARC policy record found
Mon 2017-01-23 08:19:58.678: 19: [306670] * Action taken: none
Mon 2017-01-23 08:19:58.678: 19: [306670] * Result: none
Mon 2017-01-23 08:19:58.678: 19: [306670] ---- End DMARC results
Mon 2017-01-23 08:19:58.679: 06: [306670] Passing message through AntiVirus
(Size: 2278849)...
Mon 2017-01-23 08:19:59.801: 06: [306670] * Message is clean (no viruses
found)
Mon 2017-01-23 08:19:59.801: 06: [306670] ---- End AntiVirus results
Mon 2017-01-23 08:19:59.801: 07: [306670] Spam filter scan skipped; message
size (2278849) exceeds spam filter configured max size of (102400)
Mon 2017-01-23 08:19:59.802: 01: [306670] Message creation successful:
d:\mdaemon\queues\inbound\md50002021468.msg
Mon 2017-01-23 08:19:59.802: 03: [306670] --> 250 2.6.0 Ok, message saved
<Message-ID: <[email protected]>>
Mon 2017-01-23 08:19:59.898: 02: [306670] <-- QUIT
Mon 2017-01-23 08:19:59.898: 03: [306670] --> 221 2.0.0 See ya in cyberspace
Mon 2017-01-23 08:19:59.918: 01: [306670] SMTP session successful (Bytes
in/out: 2300530/2313)
Mon 2017-01-23 08:19:59.918: 01: ----------
Terima kasih
Best regards,
Agus
--- Begin Message ---
----------------------------------------------------------------------------
------------------------------------------------------
MDaemon has detected restricted attachments within an email message, please
add or compress your attachments/files into zip or rar
----------------------------------------------------------------------------
------------------------------------------------------
>From : [email protected]
To : [email protected]
Subject : Fwd: MDaemon Notification -- Attachment Removed
Message-ID: <[email protected]>
---------------------
Attachment(s) removed
---------------------
Annual(OSSelnajaya)OS Trial Balance Conversion Tool - Ver-14.3(ENG)20170121
(Comment).zip (Annual(OSSelnajaya)OS Trial Balance Conversion Tool -
Ver-14.3(ENG)20170121 (Comment).xlsm)
--- End Message ---
