On 17/12/20 15.39, Budi Setiawan wrote: --- Mohon tidak menggunakan top posting style saat reply di milis ini. Selalu gunakan bottom posting atau interleave style seperti contoh berikut ini
https://wiki.openstack.org/wiki/MailingListEtiquette#Replies Top posting merepotkan pembacaan karena perlu waktu scroll up/down untuk mengerti konteks pembicaraan. http://daringfireball.net/2007/07/on_top The fundamental source of poor email style is the practice of quoting the entire message you’re replying to. If that’s what you do, then it doesn’t matter whether you put your response at the top or bottom. In fact, if you’re going to quote the entire message, top-posting probably is better. But both are poor form. Writing an email is like writing an article. Only quote the relevant parts, interspersing your new remarks between the quoted passages. Don’t quote anything at all from the original message if you don’t have to. Does it take more time to edit the portions of quoted text included in your reply? Yes. So does spell-checking and proofreading. It also takes time to shower and brush your teeth each day. Untuk gmail apps, cara inline reply seperti contoh dibawah ini https://webapps.stackexchange.com/questions/49884/how-to-insert-a-reply-inline-in-gmail/49886 kalau dari webmail gmail.com https://www.lifewire.com/how-to-reply-quoting-only-highlighted-text-in-gmail-1172095 --- > Apakah seperti ini detail logny Pak Syafril : Ya. > Thu 2020-12-17 11:35:27.028: [01206160] --> 250-mail.asanogear.co.id > <http://250-mail.asanogear.co.id> Hello vms23.kagoya.net > <http://vms23.kagoya.net> [153.127.230.16], pleased to meet you > Thu 2020-12-17 11:35:27.127: [01206160] Performing PTR lookup > (16.230.127.153.IN-ADDR.ARPA) > Thu 2020-12-17 11:35:27.140: [01206160] * D=16.230.127.153.in-addr.arpa > TTL=(58) > PTR=[vms23.kagoya.net <http://vms23.kagoya.net>] > Thu 2020-12-17 11:35:27.149: [01206160] * D=trustpositif.kominfo.go.id > <http://trustpositif.kominfo.go.id> TTL=(0) A=[27.54.116.70] Ini salah result oleh DNS resolver atau lebih tepat dikatakan DNS resolvernya difilter oleh ISP sehingga hasil resolvenya salah (DNS hijacking). Memangnya pakai DNS apa saja di MDaemon? http://mdaemon.dutaint.co.id/mdaemon/20.0/index.html?default-domain-and-servers_dns.htm Saya juga baru menyadari bahwa beberapa ISP melakukan DNS hijacking (lagi) akhir-akhir ini, khususnya yang pakai koneksi wired broadband (Firtmedia, myrepublic, Indihome dls) Ini hasil check pakai koneksi link.net.id $ host vms23.kagoya.net 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: vms23.kagoya.net is an alias for internetpositif3.firstmedia.com. internetpositif3.firstmedia.com has address 202.137.1.74. $ host vms23.kagoya.net 202.137.3.111 Using domain server: Name: 202.137.3.111 Address: 202.137.3.111#53 Aliases: vms23.kagoya.net is an alias for internetpositif3.firstmedia.com. internetpositif3.firstmedia.com has address 202.137.1.74 $ host vms23.kagoya.net ns3.dutaint.com Using domain server: Name: ns3.dutaint.com Address: 113.20.31.196#53 Aliases: vms23.kagoya.net has address 153.127.230.16 Koneksi Telkomsel wireless broadband (selular) $ host vms23.kagoya.net 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: vms23.kagoya.net is an alias for mypage.blocked.bltsel. mypage.blocked.bltsel has address 202.3.218.137 Kalau dari server IDC cyber1 Kuningan $ host vms23.kagoya.net 8.8.8.8 Using domain server: Name: 8.8.8.8 Address: 8.8.8.8#53 Aliases: vms23.kagoya.net has address 153.127.230.16 kelihatannya yang selamat (safe) kalau pakai DNS resolver milik sendiri atau lakukan permintaan khusus ke ISP agar tidak dilakukan filter untuk DNS query yang berasal dari public IP MDaemon server. Atau pakai DNS resolver milik DNS hoster yang tentunya DNSnya tidak difilter (DNS hijacking). Untuk sementara bisa dicoba dulu DNS resolver yang belum difilter oleh ISP, termasuk DNSnya ISP dengan cara sbb: dari dos shell (dos prompt) c:\ nslookup vms23.kagoya.net 8.8.8.8 c:\ nslookup vms23.kagoya.net 202.158.3.7 hasil yang ok akan mirip berikut ini $ nslookup vms23.kagoya.net 113.20.31.186 Server: 113.20.31.186 Address: 113.20.31.186#53 Non-authoritative answer: Name: vms23.kagoya.net Address: 153.127.230.16 cobakan ke beberapa public DNS. https://www.lifewire.com/free-and-public-dns-servers-2626062 Setelah itu lakukan update DNS resolver di MDaemon. http://mdaemon.dutaint.co.id/mdaemon/20.0/index.html?default-domain-and-servers_dns.htm [ ] Use Windows DNS servers [x] Reload DNS server hourly [x] Use EDNS0 UDP packet size: 1280 Manually configured DNS servers: {isikan IP DNS yang hasilnya OK dari test} -- syafril -------- Syafril Hermansyah MDaemon-L Moderator, run MDaemon 21.0 64bit Beta D Mohon tidak kirim private mail (atau cc:) untuk masalah MDaemon. Most people spend their entire lives in a fantasy Island called ‘Someday I’ll.’ --- Denis Waitley -- --[mdaemon-l]---------------------------------------------------------- Milis ini untuk Diskusi antar pengguna MDaemon Mail Server di Indonesia Netiket: https://wiki.openstack.org/wiki/MailingListEtiquette Arsip: http://mdaemon-l.dutaint.com Dokumentasi : http://mdaemon.dutaint.co.id Berlangganan: Kirim mail ke [email protected] Henti Langgan: Kirim mail ke [email protected] Versi terakhir: MDaemon 20.0.3, SecurityGateway 7.0.2
