[mdaemon-l] Tanya cara setting SSL
Dear Pak Syafril, Kami sudah publikasi email Mdaemon kami, tapi belom beli dan setting SSL-nya. Apakah ada tutorial untuk setting SSL di Mdaemon? Thanks, Anton -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir: MDaemon 20.0.3, SecurityGateway 7.0.2
[mdaemon-l] Penerimaan email tidak benar
Hi Pak Syafril, Mau numpang tanya, ini kami ada kejadian aneh. User kami ada kirim email dari tagihan_*@summarecon.com to ludy_***@yahoo.com Tetapi user slamat_*@summarecon.com ikut menerima email. padahal tidak di to, cc maupun bcc. Kami liat log nya agak aneh, karena itu HELO nya bisa 2x dan FROM nya juga ada 2x. Kira2 apakah yang menyebabkan kejadian ini ya pak? Thanks, Anton. smtp - in Thu 2019-03-21 16:44:10.940: 01: -- Thu 2019-03-21 16:33:42.757: 05: [547422] Session 547422; child 0010 Thu 2019-03-21 16:33:42.757: 05: [547422] Accepting SMTP connection from 172.16.0.4:53479 to 172.16.0.5:25 Thu 2019-03-21 16:33:42.769: 03: [547422] --> 220 mail.summarecon.com ESMTP MDaemon 18.0.2; Thu, 21 Mar 2019 16:33:42 +0700 Thu 2019-03-21 16:33:42.774: 02: [547422] <-- HELO WEBSERVER.summarecon.com Thu 2019-03-21 16:33:42.779: 03: [547422] --> 250 mail.summarecon.com Hello WEBSERVER.summarecon.com [172.16.0.4], pleased to meet you Thu 2019-03-21 16:33:42.779: 02: [547422] <-- HELO WEBSERVER.summarecon.com Thu 2019-03-21 16:33:42.779: 03: [547422] --> 250 mail.summarecon.com Hello WEBSERVER.summarecon.com [172.16.0.4], pleased to meet you Thu 2019-03-21 16:33:42.779: 02: [547422] <-- MAIL FROM: Thu 2019-03-21 16:33:42.800: 03: [547422] --> 250 2.1.0 Sender OK Thu 2019-03-21 16:33:42.800: 02: [547422] <-- MAIL FROM: Thu 2019-03-21 16:33:42.815: 03: [547422] --> 250 2.1.0 Sender OK Thu 2019-03-21 16:33:42.815: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.835: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.835: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.844: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.844: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.853: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.853: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.856: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.856: 02: [547422] <-- DATA Thu 2019-03-21 16:33:42.872: 01: [547422] Creating temp file (SMTP): d:\mdaemon\queues\temp\58\md5001790.tmp Thu 2019-03-21 16:33:42.872: 03: [547422] --> 354 Enter mail, end with . Thu 2019-03-21 16:33:42.875: 01: [547422] Message size: 8998 bytes Thu 2019-03-21 16:33:42.880: 11: [547422] Passing message through ClamAV Plugin (d:\mdaemon\queues\temp\58\md5001790.tmp)... Thu 2019-03-21 16:33:42.880: 11: [547422] * Message-ID: Thu 2019-03-21 16:33:42.974: 11: [547422] * Virus result: 0 - clean Thu 2019-03-21 16:33:42.992: 01: [547422] Message creation successful: d:\mdaemon\queues\inbound\61\md5037791.msg Thu 2019-03-21 16:33:42.992: 03: [547422] --> 250 2.6.0 Ok, message saved Thu 2019-03-21 16:33:42.993: 02: [547422] <-- DATA Thu 2019-03-21 16:33:43.002: 01: [547422] Creating temp file (SMTP): d:\mdaemon\queues\temp\60\md5001790.tmp Thu 2019-03-21 16:33:43.002: 03: [547422] --> 354 Enter mail, end with . Thu 2019-03-21 16:44:10.940: 04: [547422] Connection timed out! Thu 2019-03-21 16:44:10.942: 01: [547422] SMTP session successful (Bytes in/out: 9331/506) Thu 2019-03-21 16:44:10.942: 01: -- -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 18.5.3, SG 6.0
[mdaemon-l] Penerimaan email tidak benar
Berikan trasnskrip lognya yang asli, belum diotak-atik, agar saya bisa analisis dengan lengkap/akurat. smtp - out Thu 2019-03-21 16:33:36.086: 01: -- Thu 2019-03-21 16:33:45.558: 05: [547432] Session 547432; child 0002 Thu 2019-03-21 16:33:45.558: 01: [547432] Parsing message Thu 2019-03-21 16:33:45.559: 01: [547432] * From: tagihan_thespringl...@summarecon.com Thu 2019-03-21 16:33:45.559: 01: [547432] * To: ludy_...@yahoo.com Thu 2019-03-21 16:33:45.559: 01: [547432] * Subject: Surat Pemberitahuan ke-1 AZ02/003 Thu 2019-03-21 16:33:45.559: 01: [547432] * Size (bytes): 9667 Thu 2019-03-21 16:33:45.559: 01: [547432] * Message-ID: Thu 2019-03-21 16:33:45.613: 05: [547432] Attempting to send message to smart host Thu 2019-03-21 16:33:45.613: 05: [547432] Attempting SMTP connection to smarthost.dutaint.com Thu 2019-03-21 16:33:45.613: 05: [547432] Resolving A record for smarthost.dutaint.com (DNS Server: 172.16.0.2)... Thu 2019-03-21 16:33:45.620: 05: [547432] * D=smarthost.dutaint.com TTL=(3) A=[113.20.31.189] Thu 2019-03-21 16:33:45.620: 05: [547432] Attempting SMTP connection to 113.20.31.189:587 Thu 2019-03-21 16:33:45.620: 05: [547432] Waiting for socket connection... Thu 2019-03-21 16:33:45.632: 05: [547432] * Connection established 172.16.0.5:65372 --> 113.20.31.189:587 Thu 2019-03-21 16:33:45.632: 05: [547432] Waiting for protocol to start... Thu 2019-03-21 16:33:45.667: 02: [547432] <-- 220 dip33.dutaint.com ESMTP MSA MDaemon 19.0.0a; Thu, 21 Mar 2019 16:33:45 +0700 Thu 2019-03-21 16:33:45.668: 03: [547432] --> EHLO mail.summarecon.com Thu 2019-03-21 16:33:45.680: 02: [547432] <-- 250-dip33.dutaint.com Hello mail.summarecon.com [219.83.68.60], pleased to meet you Thu 2019-03-21 16:33:45.680: 02: [547432] <-- 250-AUTH LOGIN PLAIN Thu 2019-03-21 16:33:45.680: 02: [547432] <-- 250-8BITMIME Thu 2019-03-21 16:33:45.680: 02: [547432] <-- 250-ENHANCEDSTATUSCODES Thu 2019-03-21 16:33:45.680: 02: [547432] <-- 250-STARTTLS Thu 2019-03-21 16:33:45.680: 02: [547432] <-- 250 SIZE 36700160 Thu 2019-03-21 16:33:45.680: 03: [547432] --> AUTH LOGIN Thu 2019-03-21 16:33:45.693: 02: [547432] <-- 334 VXNlcm5hbWU6 Thu 2019-03-21 16:33:45.693: 03: [547432] --> ** Thu 2019-03-21 16:33:45.701: 02: [547432] <-- 334 UGFzc3dvcmQ6 Thu 2019-03-21 16:33:45.701: 03: [547432] --> ** Thu 2019-03-21 16:33:45.733: 02: [547432] <-- 235 2.7.0 Authentication successful Thu 2019-03-21 16:33:45.733: 03: [547432] --> MAIL From: SIZE=9667 Thu 2019-03-21 16:33:45.890: 02: [547432] <-- 250 2.1.0 Sender OK Thu 2019-03-21 16:33:45.890: 03: [547432] --> RCPT To: Thu 2019-03-21 16:33:45.910: 02: [547432] <-- 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:45.911: 03: [547432] --> DATA Thu 2019-03-21 16:33:45.922: 02: [547432] <-- 354 Enter mail, end with . Thu 2019-03-21 16:33:45.922: 01: [547432] Sending to [113.20.31.189] Thu 2019-03-21 16:33:45.923: 01: [547432] Transfer Complete Thu 2019-03-21 16:33:46.112: 02: [547432] <-- 250 2.6.0 Ok, message saved > Thu 2019-03-21 16:33:46.112: 03: [547432] --> QUIT Thu 2019-03-21 16:33:46.127: 02: [547432] <-- 221 2.0.0 See ya in cyberspace Thu 2019-03-21 16:33:46.127: 01: [547432] SMTP session successful (Bytes in/out: 561/9857) Thu 2019-03-21 16:33:46.127: 01: -- smtp - in Thu 2019-03-21 16:44:10.940: 01: -- Thu 2019-03-21 16:33:42.757: 05: [547422] Session 547422; child 0010 Thu 2019-03-21 16:33:42.757: 05: [547422] Accepting SMTP connection from 172.16.0.4:53479 to 172.16.0.5:25 Thu 2019-03-21 16:33:42.769: 03: [547422] --> 220 mail.summarecon.com ESMTP MDaemon 18.0.2; Thu, 21 Mar 2019 16:33:42 +0700 Thu 2019-03-21 16:33:42.774: 02: [547422] <-- HELO WEBSERVER.summarecon.com Thu 2019-03-21 16:33:42.779: 03: [547422] --> 250 mail.summarecon.com Hello WEBSERVER.summarecon.com [172.16.0.4], pleased to meet you Thu 2019-03-21 16:33:42.779: 02: [547422] <-- HELO WEBSERVER.summarecon.com Thu 2019-03-21 16:33:42.779: 03: [547422] --> 250 mail.summarecon.com Hello WEBSERVER.summarecon.com [172.16.0.4], pleased to meet you Thu 2019-03-21 16:33:42.779: 02: [547422] <-- MAIL FROM: Thu 2019-03-21 16:33:42.800: 03: [547422] --> 250 2.1.0 Sender OK Thu 2019-03-21 16:33:42.800: 02: [547422] <-- MAIL FROM: Thu 2019-03-21 16:33:42.815: 03: [547422] --> 250 2.1.0 Sender OK Thu 2019-03-21 16:33:42.815: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.835: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.835: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.844: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.844: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.853: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.853: 02: [547422] <-- RCPT TO: Thu 2019-03-21 16:33:42.856: 03: [547422] --> 250 2.1.5 Recipient OK Thu 2019-03-21 16:33:42.856: 02: [547422] <-- DATA Thu 2019-03-21 16:33:42.872: 01: [547422] Creating temp file (SMTP): d:\mdaemon\queues\temp\58\md5001790.tmp Thu 2
[mdaemon-l] Penerimaan email tidak benar
Adanya dobel Mail From dan dobel HELO mengindikasikan adanya kesalahan kirim di sisi sender. Kemungkinan salahnya bukan mail agent sender tetapi di proxy (antivirus) yang ada diantara sender dengan MDaemon sehingga mail command sequence terganggu. H Disini kami punya 1 server yang dipasangi beberapa alamat email dan bertugas mengirimkan email dengan script. Apakah mungkin terganggunya command sequence pengiriman email ini karena server kami waktu itu mengirimkan email secara paralel dari 2 alamat email (tagihan_thespringl...@summarecon.com dan admin_appro...@summarecon.com) ? Bila benar memang demikian, biasanya gimana cara untuk mengatasinya? Thanks, Anton -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 18.5.3, SG 6.0
[mdaemon-l] Penerimaan email tidak benar
Bila benar memang demikian, biasanya gimana cara untuk mengatasinya? Diatur agar gantian kirimnya, setelah satu selesai baru yang lain boleh kirim (on behalf sender address yang lain). Atau masing-2x mail agent binding ke IP yang berbeda (1 NIC bisa punya ^ dari atau ke .. 255 IP), sehingga saat kirim mail ke MDaemon akan berbeda sessionnya. Dalam hal kirim ke IP berbeda maka yang pakai multi IP adalah MDaemonnya, karena jarang sekali ada mail agent yang cukup smart untuk mengatur outbound binding IP. Sorry Pak Syafril, saya kurang paham untuk cara mengatasinya. Apakah maksudnya nanti di pc server pengirim kami dipasang 2 ip, lalu masing2 on behalf dipasangkan ke satu IP? Apakah tersedia tutorial untuk kasus saya pak? agar saya lebih gampang mendapat gambarannya. Thanks, Anton. -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 18.5.3, SG 6.0
[mdaemon-l] DMARC untuk email yang di autoforward
Halo Pak Syafril, Beberapa user kami disetting forwarding ke email pribadinya (yahoo or gmail). Tetapi ada beberapa email yang tidak bisa diterima di email pribadi, di keterangan errornya karena DMARC policy. contoh kasusnya: from: booking.com to: michelle...@summarecon.com forwarding: michelle.ling...@gmail.com Biasanya jalan keluar untuk masalah forwarding gimana ya pak? Thanks, Anton pesan errornya: From: MDaemon at dip32.dutaint.com (postmas...@summarecon.com) Date: Mon, Feb 11, 2019 at 5:18 PM Subject: WARNING: Message delivery failed To: = = Greetings from the MDaemon mail system at dip32.dutaint.com = = The following message: Session-ID: 726486 (specific to this delivery attempt) Queue-ID: pd35006941628.msg Message-ID: e1gt6vt-0001z1...@memta-206.lhr4.prod.booking.com could not be delivered to the following recipient(s): michelle.ling...@gmail.com (unrecoverable error) despite one or more unsuccessful attempts to do so. No further delivery attempts will be made and the message has been removed from the queue. The original message headers may follow at the end of this report. For information on DSN messages see http://www.altn.com/dsn/. Please quote the Queue-ID, Session-ID, and Message-ID found above in any inquiries regarding this message. = Session Transcript = [726486] Session 726486; child 0005 [726486] Parsing message [726486] * From: 1893422124-vkmv.uvwx.jrt7.r...@property.booking.com [726486] * To: michelle.ling...@gmail.com [726486] * Subject: Anda mendapat pesan dari Shanghai Lin Yin Holiday Hotel [726486] * Size (bytes): 43256 [726486] * Message-ID: [726486] Resolving MX record for gmail.com (DNS Server: 113.20.31.196)... [726486] * P=005 S=001 D=gmail.com TTL=(16) MX=[gmail-smtp-in.l.google.com] [726486] * P=010 S=002 D=gmail.com TTL=(16) MX=[alt1.gmail-smtp-in.l.google.com] [726486] * P=020 S=000 D=gmail.com TTL=(16) MX=[alt2.gmail-smtp-in.l.google.com] [726486] * P=030 S=004 D=gmail.com TTL=(16) MX=[alt3.gmail-smtp-in.l.google.com] [726486] * P=040 S=003 D=gmail.com TTL=(16) MX=[alt4.gmail-smtp-in.l.google.com] [726486] Attempting SMTP connection to gmail-smtp-in.l.google.com [726486] Resolving A record for gmail-smtp-in.l.google.com (DNS Server: 113.20.31.196)... [726486] * D=gmail-smtp-in.l.google.com TTL=(3) A=[172.217.194.26] [726486] Attempting SMTP connection to 172.217.194.26:25 [726486] Waiting for socket connection... [726486] * Connection established 113.20.31.188:26964 --> 172.217.194.26:25 [726486] Waiting for protocol to start... [726486] <-- 220 mx.google.com ESMTP g1si10037155pld.197 - gsmtp [726486] --> EHLO dip32.dutaint.com [726486] <-- 250-mx.google.com at your service, [113.20.31.188] [726486] <-- 250-SIZE 157286400 [726486] <-- 250-8BITMIME [726486] <-- 250-STARTTLS [726486] <-- 250-ENHANCEDSTATUSCODES [726486] <-- 250-PIPELINING [726486] <-- 250-CHUNKING [726486] <-- 250 SMTPUTF8 [726486] --> STARTTLS [726486] <-- 220 2.0.0 Ready to start TLS [726486] SSL negotiation successful (TLS 1.2, 256 bit key exchange, 128 bit AES encryption) [726486] SSL certificate is valid (matches gmail-smtp-in.l.google.com and is signed by recognized CA) [726486] --> EHLO dip32.dutaint.com [726486] <-- 250-mx.google.com at your service, [113.20.31.188] [726486] <-- 250-SIZE 157286400 [726486] <-- 250-8BITMIME [726486] <-- 250-ENHANCEDSTATUSCODES [726486] <-- 250-PIPELINING [726486] <-- 250-CHUNKING [726486] <-- 250 SMTPUTF8 [726486] --> MAIL From: SIZE=43256 [726486] <-- 250 2.1.0 OK g1si10037155pld.197 - gsmtp [726486] --> RCPT To: [726486] <-- 250 2.1.5 OK g1si10037155pld.197 - gsmtp [726486] --> DATA [726486] <-- 354 Go ahead g1si10037155pld.197 - gsmtp [726486] Sending to [172.217.194.26] [726486] Transfer Complete [726486] <-- 550-5.7.1 Unauthenticated email from property.booking.com is not accepted due to [726486] <-- 550-5.7.1 domain's DMARC policy. Please contact the administrator of [726486] <-- 550-5.7.1 property.booking.com domain if this was a legitimate mail. Please [726486] <-- 550-5.7.1 visit [726486] <-- 550-5.7.1 https://support.google.com/mail/answer/2451690 to learn about the [726486] <-- 550 5.7.1 DMARC initiative. g1si10037155pld.197 - gsmtp [726486] --> QUIT =End Transcript= -- --[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 mdaemon-l-subscr...@dutaint.com Henti L
[mdaemon-l] DMARC untuk email yang di autoforward
Diblock autoforward mail yang aslinya berasal dari domain yang mengaktifkan DMARC dengan policy = reject dan ditujukan (diforward) ke domain yang mengaktifkan DMARC check macam gmail.com, yahoo.com dll. Setidaknya untuk sementara ini, sebelum MDaemon mendukung DMARC forwarding (ARC, Authenticated Received Chain). http://arc-spec.org/ Jadi untuk sekarang ini bila mau forwarding seperti contoh kasus saya apakah ada jalan lain pak? Blocking bisa dilakukan dengan Mail Process Content Filtering. http://mdaemon.dutaint.co.id/mdaemon/18.5/index.html?cf_content_filter_editor.htm Ini maksudnya kita buat rule untuk block email warning akibat gagal forwarding ya pak? -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 18.5.3, SG 6.0
[mdaemon-l] DMARC untuk email yang di autoforward
Mintakan ke altn.com untuk membuatkan DMARC forwarding di http://feedback.altn.com Sebenarnya ada workaroundnya, akan tetapi saya lupa linknya ditaruh dimana dan ribet settingnya. Saya telah isi di feedback pak, kemudian telah dibalas: "Thank you for your suggestion to implement DMARC forwarding. Messages automatically forwarded to users on external domains should be able to pass DMARC as long as your SPF record allows the server doing the forwarding to send email for your domain and you have the option enabled for “Use local address in SMTP envelope when forwarding messages”, which is found under Security / Security Settings / Sender Authentication / SPF Verification. If the message has been DKIM signed, it should also pass after forwarding unless something was altered in the message to break the signature." Apakah yang dimaksud dengan workaround nya Pak Syafril seperti saran dia pak "SPF record allow..." ? -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 18.5.3, SG 6.0
[mdaemon-l] Tanya Feedback Loop
Dear Pak Syafril, Pak saya mau tanya apakah di mdaemon ada support feedback loop, yang dari saya baca2 salah satu gunanya untuk menerima feedback dari penerima email jika mereka menandai email yang masuk dengan "mark as Spam". Jadi nantinya biar penerima tersebut bisa dihapus dari daftar pengiriman. Mohon pencerahannya. Thanks. Anton -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 19.0.3, SG 6.1.0
[mdaemon-l] Tanya Feedback Loop
Daftar pengiriman apa yang akan atau dirasa perlu dihapus? Jadi begini pak, misalnya dari kami ada email blast lumayan banyak kepublic, seperti email tagihan atau promosi. Menurut artikel yang saya baca, jika penerima email menandai email kami "as spam" akan ada feedback loop ke kami/ISP. Jadi nanti email penerima tersebut bisa kami keluarkan dari queue pengiriman berikutnya untuk menjaga agar reputasi domain kami bersih (tidak terblacklist secara domain). Jika user sendiri mark as spam maka mail aslinya akan (otomatis) pindah ke public folder /bayesian learning / Spam. Global Administrator akan bisa melihat isi public folder bayesian learning dan menghapusnya (jika perlu) sebelum proses bayesian learning tengah malam. Apakah di folder bayesian ini bisa tampak user (alamat email) yang "mark as spam" email kami gitu pak? Thanks, Anton. -- --[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 mdaemon-l-subscr...@dutaint.com Henti Langgan: Kirim mail ke mdaemon-l-unsubscr...@dutaint.com Versi terakhir MD 19.0.3, SG 6.1.0
