[Mdaemon-L] Email tidak diterima recipient
On 5/2/23 10:17, Bambang Setiawan via Mdaemon-L wrote: transfernya complete tapi menurut sender recipient belum menerima emailnya. Tue 2023-05-02 09:49:20.129: [39735662] <-- 250 2.0.0 Ok: queued as 4Q9Pf55fzCzGVpFf. elapsed time 14.940s Kalau semua recipient tidak menerimanya di Inbox foldernya, minta ditanyakan ke pengelola mail domain @huawei.com. -- syafril Syafril Hermansyah MDaemon-L Moderators, running MDaemon 23.0.2 Beta A Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. I have not failed. I've just found 10,000 ways that won't work. --- Thomas A. Edison -- --[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 23.0.1, SecurityGateway 9.0.2
[Mdaemon-L] Email tidak diterima recipient
Dear Pak Syafril, Mohon bantuannya untuk log terlampir apakah ada masalah pak ?, transfernya complete tapi menurut sender recipient belum menerima emailnya. Terima kasih. Tue 2023-05-02 09:49:17.944: -- Tue 2023-05-02 09:48:55.419: [39735662] REMOTE message: pd35001491623.msg Tue 2023-05-02 09:48:55.419: [39735662] * Session 39735662; child 0001 Tue 2023-05-02 09:48:55.420: [39735662] * From: andi.faturokh...@persada.id Tue 2023-05-02 09:48:55.420: [39735662] * To: irwan.p...@huawei.com Tue 2023-05-02 09:48:55.420: [39735662] * Subject: Battery Tycoon Implementation PERSADA-EJBN Tue 2023-05-02 09:48:55.420: [39735662] * Message-ID: <002b01d97ca0$65af7730$310e6590$@persada.id> Tue 2023-05-02 09:48:55.420: [39735662] * Size: 486275; Tue 2023-05-02 09:48:55.420: [39735662] * Route slip host: huawei.com Tue 2023-05-02 09:48:55.421: [39735662] * Route slip port: 25 Tue 2023-05-02 09:48:55.430: [39735662] Resolving MX record for huawei.com (DNS Server: 203.119.13.77)... Tue 2023-05-02 09:48:55.481: [39735662] * P=010 S=001 D=huawei.com TTL=(10) MX=[mx5.huawei.com] Tue 2023-05-02 09:48:55.481: [39735662] * P=020 S=002 D=huawei.com TTL=(10) MX=[mx8.his.huawei.com] Tue 2023-05-02 09:48:55.481: [39735662] * P=030 S=000 D=huawei.com TTL=(10) MX=[mx7.huawei.com] Tue 2023-05-02 09:48:55.481: [39735662] * P=030 S=003 D=huawei.com TTL=(10) MX=[mx9.his.huawei.com] Tue 2023-05-02 09:48:55.482: [39735662] Attempting SMTP connection to mx5.huawei.com Tue 2023-05-02 09:48:55.482: [39735662] Resolving A record for mx5.huawei.com (DNS Server: 203.119.13.77)... Tue 2023-05-02 09:48:55.484: [39735662] * D=mx5.huawei.com TTL=(10) A=[124.71.93.234] Tue 2023-05-02 09:48:55.484: [39735662] Attempting SMTP connection to 124.71.93.234:25 Tue 2023-05-02 09:48:55.484: [39735662] Waiting for socket connection... Tue 2023-05-02 09:48:55.725: [39735662] * Connection established 103.150.114.155:63167 --> 124.71.93.234:25 Tue 2023-05-02 09:48:55.726: [39735662] Waiting for protocol to start... Tue 2023-05-02 09:49:00.285: [39735662] <-- 220 Welcome to access Huawei SMTP service! Tue 2023-05-02 09:49:00.288: [39735662] --> EHLO mail.persada.id Tue 2023-05-02 09:49:00.529: [39735662] <-- 250-canpmsg-in Tue 2023-05-02 09:49:00.529: [39735662] <-- 250-SIZE 41943040 Tue 2023-05-02 09:49:00.529: [39735662] <-- 250-STARTTLS Tue 2023-05-02 09:49:00.529: [39735662] <-- 250-AUTH PLAIN LOGIN Tue 2023-05-02 09:49:00.529: [39735662] <-- 250-ENHANCEDSTATUSCODES Tue 2023-05-02 09:49:00.529: [39735662] <-- 250-8BITMIME Tue 2023-05-02 09:49:00.529: [39735662] <-- 250 SMTPUTF8 Tue 2023-05-02 09:49:00.529: [39735662] --> STARTTLS Tue 2023-05-02 09:49:00.774: [39735662] <-- 220 2.0.0 Ready to start TLS Tue 2023-05-02 09:49:01.703: [39735662] SSL negotiation successful (TLS 1.2, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) Tue 2023-05-02 09:49:01.705: [39735662] SSL certificate is not valid (not signed by recognized CA) Tue 2023-05-02 09:49:01.705: [39735662] --> EHLO mail.persada.id Tue 2023-05-02 09:49:01.946: [39735662] <-- 250-canpmsg-in Tue 2023-05-02 09:49:01.946: [39735662] <-- 250-SIZE 41943040 Tue 2023-05-02 09:49:01.946: [39735662] <-- 250-AUTH PLAIN LOGIN Tue 2023-05-02 09:49:01.946: [39735662] <-- 250-ENHANCEDSTATUSCODES Tue 2023-05-02 09:49:01.946: [39735662] <-- 250-8BITMIME Tue 2023-05-02 09:49:01.946: [39735662] <-- 250 SMTPUTF8 Tue 2023-05-02 09:49:01.946: [39735662] --> MAIL From: SIZE=486275 Tue 2023-05-02 09:49:03.188: [39735662] <-- 250 2.1.0 Ok Tue 2023-05-02 09:49:03.189: [39735662] --> RCPT To: Tue 2023-05-02 09:49:03.431: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:03.431: [39735662] --> RCPT To: Tue 2023-05-02 09:49:05.673: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:05.673: [39735662] --> RCPT To: Tue 2023-05-02 09:49:05.915: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:05.915: [39735662] --> RCPT To: Tue 2023-05-02 09:49:08.156: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:08.156: [39735662] --> RCPT To: Tue 2023-05-02 09:49:08.398: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:08.398: [39735662] --> RCPT To: Tue 2023-05-02 09:49:10.640: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:10.640: [39735662] --> RCPT To: Tue 2023-05-02 09:49:10.883: [39735662] <-- 250 2.1.5 Ok Tue 2023-05-02 09:49:10.883: [39735662] --> DATA Tue 2023-05-02 09:49:13.173: [39735662] <-- 354 End data with . Tue 2023-05-02 09:49:13.173: [39735662] Sending to [124.71.93.234] Tue 2023-05-02 09:49:17.494: [39735662] Transfer Complete Tue 2023-05-02 09:49:20.129: [39735662] <-- 250 2.0.0 Ok: queued as 4Q9Pf55fzCzGVpFf. elapsed time 14.940s Tue 2023-05-02 09:49:20.132: [39735662] --> QUIT Tue 2023-05-02 09:49:21.374: [39735662] <-- 221 2.0.0 Bye Tue 2023-05-02 09:49:21.374: [39735662] SMTP session successful (Bytes in/out: 2989/490938) Tue 2023-05-02 09:49:21.374: -- -- --[mdaemon-l]-- Milis ini untuk Diskusi antar
[Mdaemon-L] DMARC Report Sehubungan DKIM
On 5/2/23 10:01, Ivan Leonardo wrote: Itu mail forwarding, bukan dari direct delivery. Yang pass itu dkim milik domain yang melakukan forwarding mail dari pttdp.com. Ohhh DKIM sender yg melakukan Fwd, jadi kalau mau aman tidak bisa fwd harus set DMARC p=reject ya ? Ya. Tapi kalau DKIM milik sender kenapa tulisan selectornya benar punya saya ya Pak ? Kalau server domain itu tidak mendukung DKIM signing maka saat forward tidak di overwrite, diteruskan DKIM sign dari original sender apa adanya. -- syafril Syafril Hermansyah MDaemon-L Moderators, running MDaemon 23.0.2 Beta A Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. A good scientist is a person with original ideas. A good engineer is a person who makes a design that works with as few original ideas as possible. There are no prima donnas in engineering. --- Freeman Dyson -- --[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 23.0.1, SecurityGateway 9.0.2
[Mdaemon-L] DMARC Report Sehubungan DKIM
On 02/05/2023 09:54, Syafril Hermansyah via Mdaemon-L wrote: Itu mail forwarding, bukan dari direct delivery. Yang pass itu dkim milik domain yang melakukan forwarding mail dari pttdp.com. Ohhh DKIM sender yg melakukan Fwd, jadi kalau mau aman tidak bisa fwd harus set DMARC p=reject ya ? Tapi kalau DKIM milik sender kenapa tulisan selectornya benar punya saya ya Pak ? Rgds, -- --[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 23.0.1, SecurityGateway 9.0.2
[Mdaemon-L] DMARC Report Sehubungan DKIM
On 5/2/23 08:06, Ivan Leonardo wrote: Kalau dilihat status DKIM nya Pass dan SPF failed karena bukan server MD kami yg mengirim, kalau benar dari server kami pasti DKIM dan SPF Pass spt yg tanda centang merah. IP yg kuning bukan IP kami utk transaksi yg bukan dari IP kami itu kenapa status DKIM nya bisa pass ya ? apakah mereka bisa signing message memakai key MD kami ? Itu mail forwarding, bukan dari direct delivery. Yang pass itu dkim milik domain yang melakukan forwarding mail dari pttdp.com. -- syafril Syafril Hermansyah MDaemon-L Moderators, running MDaemon 23.0.2 Beta A Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. Education is the power to think clearly, the power to act well in the world's work, and the power to appreciate life. --- Brigham Young -- --[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 23.0.1, SecurityGateway 9.0.2
[Mdaemon-L] DMARC Report Sehubungan DKIM
Pak, saya terima DMARC report dari Google. Kalau dilihat status DKIM nya Pass dan SPF failed karena bukan server MD kami yg mengirim, kalau benar dari server kami pasti DKIM dan SPF Pass spt yg tanda centang merah. IP yg kuning bukan IP kami utk transaksi yg bukan dari IP kami itu kenapa status DKIM nya bisa pass ya ? apakah mereka bisa signing message memakai key MD kami ? Rgds, -- --[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 23.0.1, SecurityGateway 9.0.2
