On 3/17/25 13:57, Slamet Raharjo via Mdaemon-L wrote:
---
Mohon tidak posting dengan top posting style di milis ini, selalu
gunakan bottom (interleaved) posting untuk memudahkan pembacaan.
https://blog.joelesler.net/2009/12/bottom-posting.html
The particular part to pay attention to is in RFC1855 --
"- If you are sending a reply to a message or a posting be sure you
summarize the original at the top of the message, or include just
enough text of the original to give a context. This will make
sure readers understand when they start to read your response.
Since NetNews, especially, is proliferated by distributing the
postings from one host to another, it is possible to see a
response to a message before seeing the original. Giving context
helps everyone. But do not include the entire original!"
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.
Hanya bottom replies yang bisa memanfaatkan inline reply dalam diskusi,
top posting itu mirip SMS (Short Message Services) atau Messenger chat
hanya untuk 1 topik saja
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style)
Agar outlook bisa otomatis menggunakan Internet Quote Style yang
diperlukan saat inline reply maka ubah settingnya seperti ini
https://www.slipstick.com/outlook/email/to-use-internet-style-quoting/
Salin selected text yang akan di quote ulang, yang sesuai contex, ke
atas signature lalu hapus quote text yang tidak lagi sesuai konteks yang
akan dijawab.
Untuk memangkas (hapus) text hanya perlu ketangkasan menggunakan mouse
dan atau keyboard.
https://www.computerhope.com/issues/ch001669.htm
---
Aktifkan SMTP/TLS di MDaemon.
Boleh pakai Self Sign Certificate atau lebih baik lagi pakai CA
(Certificate Authority) SSL.
>> $ openssl s_client -starttls smtp -connect mail.aio.co.id:25
CONNECTED(00000003)
Didn't find STARTTLS in server response, trying anyway...
Terlampr tampilan di MDaemon saya, apakah sudah benar ?
MDaemon SMTP TLS.jpg
Sudah benar.
Tetapi smtp/tls di port 25 tidak aktif, walau di port 587 (SMTP/MSA) aktif.
TLS di port 143 (IMAP) dan port 110 (POP3) tidak aktif, walau di port
443 (HTTPS Webmail) aktif.
Itu indikasi adanya firewall atau proxy (antivirus) yang aktif memfilter
tcp port 25.
Beberapa firewall dilengkapi dengan fitur proxy inspector (proxy firewall).
Coba diperika Firewall Traffic Rule untuk tcp port 25 (dan 110, 143)
khsusnya untuk inbound rule (dari internet ke server MDaemon
mail.aio.co.id), samakan exclusionnya dengan traffic rule port 587.
Traffic rule untuk outbound sudah benar mendukung SMTP/TLS.
https://www.paloaltonetworks.com/cyberpedia/what-is-a-proxy-firewall
https://www.fortinet.com/resources/cyberglossary/proxy-firewall
$ openssl s_client -starttls smtp -connect mail.aio.co.id:25
CONNECTED(00000003)
Didn't find STARTTLS in server response, trying anyway...
$ telnet mail.aio.co.id 25
Trying 202.158.62.55...
Connected to mail.aio.co.id.
Escape character is '^]'.
220 mail.aio.co.id ESMTP Service ready
ehlo dip8.dutaint.com
250-Requested mail action okay, completed
250-ETRN
250-8BITMIME
250-SIZE 26624000
250 OK
$ openssl s_client -starttls smtp -connect mail.aio.co.id:587
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R10
verify return:1
depth=0 CN = mail.aio.co.id
verify return:1
---
Certificate chain
0 s:CN = mail.aio.co.id
i:C = US, O = Let's Encrypt, CN = R10
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
v:NotBefore: Jan 24 02:00:52 2025 GMT; NotAfter: Apr 24 02:00:51
2025 GMT
1 s:C = US, O = Let's Encrypt, CN = R10
i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
v:NotBefore: Mar 13 00:00:00 2024 GMT; NotAfter: Mar 12 23:59:59
2027 GMT
---
$ telnet mail.aio.co.id 587
Trying 202.158.62.55...
Connected to mail.aio.co.id.
Escape character is '^]'.
220 mail.aio.co.id ESMTP MSA MDaemon 23.0.1; Tue, 18 Mar 2025 06:38:07 +0700
ehlo dip8.dutaint.com
250-mail.aio.co.id Hello dip8.dutaint.com [103.94.121.132], pleased to
meet you
250-AUTH LOGIN CRAM-MD5 PLAIN
250-8BITMIME
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-STARTTLS
250 SIZE 26624000
Mon 2025-03-17 12:53:26.118: ----------
Mon 2025-03-17 13:08:36.054: [03826540] Session 03826540; child 0001
Mon 2025-03-17 13:08:36.054: [03826540] Accepting SMTP connection from
202.158.62.55:54423 to 113.20.31.187:25
Mon 2025-03-17 13:08:36.054: [03826540] Location Screen says connection is from
Indonesia, Asia
Mon 2025-03-17 13:08:36.058: [03826540] --> 220 dip31.dutaint.com ESMTP MDaemon
25.0.1a; Mon, 17 Mar 2025 13:08:36 +0700
Mon 2025-03-17 13:08:36.072: [03826540] <-- EHLO mail.aio.co.id
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-dip31.dutaint.com Hello
mail.aio.co.id [202.158.62.55], pleased to meet you
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-ETRN
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-8BITMIME
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-ENHANCEDSTATUSCODES
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-PIPELINING
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-CHUNKING
Mon 2025-03-17 13:08:36.073: [03826540] --> 250-STARTTLS
Mon 2025-03-17 13:08:36.073: [03826540] --> 250 SIZE 41943040
Mon 2025-03-17 13:08:36.086: [03826540] <-- STARTTLS
Mon 2025-03-17 13:08:36.086: [03826540] --> 220 2.7.0 Ready to start TLS
Mon 2025-03-17 13:08:36.147: [03826540] SSL negotiation successful (TLS 1.2,
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)
Mon 2025-03-17 13:08:36.164: [03826540] <-- EHLO mail.aio.co.id
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-dip31.dutaint.com Hello
mail.aio.co.id [202.158.62.55], pleased to meet you
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-ETRN
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-8BITMIME
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-ENHANCEDSTATUSCODES
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-PIPELINING
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-CHUNKING
Mon 2025-03-17 13:08:36.165: [03826540] --> 250-REQUIRETLS
Mon 2025-03-17 13:08:36.165: [03826540] --> 250 SIZE 41943040
Mon 2025-03-17 13:08:36.177: [03826540] <-- MAIL
From:<prvs=1171bba100=sraha...@aio.co.id> SIZE=1934
Mon 2025-03-17 13:08:36.381: [03826540] <-- RCPT To:<mdaemon-l@dutaint.com>
--
syafril
--------
Syafril Hermansyah
MDaemon-L Moderator, run MDaemon 25.0.1 Beta A
Mohon tidak kirim private mail (atau cc:) untuk masalah MDaemon.
Tidak ada yg pernah menjadi nyata sampai dialami. Bahkan peribahasa
bukanlah peribahasa bagi Anda sampai kehidupan Anda tlh menggambarkannya
-- John Keats
--
--[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.com
Berlangganan: Kirim mail ke mdaemon-l-subscr...@dutaint.com
Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com
Versi terakhir: MDaemon 25.0.0, SecurityGateway 10.5.3
