log nya cuma message creation succesfull tapi tidak masuk ke inbox user
kenapa ya?
From: "Syafril Hermansyah via Mdaemon-L" <Mdaemon-L@dutaint.com>
To: Mdaemon-L@dutaint.com
Date: Sun, 5 Mar 2023 21:22:09 +0700
Subject: [Mdaemon-L] Tidak bisa terima email
On 05/03/23 20.48, Syafril Hermansyah via Mdaemon-L wrote:
> On 05/03/23 19.59, pongky via Mdaemon-L wrote:
>> Mohon dibantu untuk problem tidak bisa terima email verifikasi dari
booking.com
>> sebelumnya bisa terima, namun per maret ini tidak bisa, mohon sarannya.
>
>
> Apakah sudah periksa ke smtp-in di kedua server?
Cara mencari transaksi dari log lihat ke sini
https://mdaemonid.blogspot.com/2020/05/mencari-transaksi-mdaemon-dari-log.html
lihat ke bagian "2. Menggunakan Remote Administration (Webadmin)."
--
syafril
--------
Syafril Hermansyah
MDaemon-L Moderator, run MDaemon 23.0.1 Beta A
Mohon tidak kirim private mail (atau cc:) untuk masalah MDaemon.
In learning you will teach, and in teaching you will learn.
--- Phil Collins
--
--[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.0, SecurityGateway 9.0.1
Pongky
Under Luley
--
--[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.0, SecurityGateway 9.0.1
Sat 2023-03-04 11:23:11.388: ----------
Sat 2023-03-04 11:23:18.762: [926687] Session 926687; child 0001
Sat 2023-03-04 11:23:18.762: [926687] Accepting SMTP connection from
192.254.126.47:14428 to 192.168.0.6:25
Sat 2023-03-04 11:23:18.764: [926687] --> 220 mail.sentosagroup.com ESMTP Sat,
04 Mar 2023 11:23:18 +0700
Sat 2023-03-04 11:23:19.067: [926687] <-- EHLO o8.sg.booking.com
Sat 2023-03-04 11:23:19.067: [926687] --> 250-mail.sentosagroup.com Hello
o8.sg.booking.com [192.254.126.47], pleased to meet you
Sat 2023-03-04 11:23:19.067: [926687] --> 250-ETRN
Sat 2023-03-04 11:23:19.067: [926687] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Sat 2023-03-04 11:23:19.067: [926687] --> 250-8BITMIME
Sat 2023-03-04 11:23:19.067: [926687] --> 250-ENHANCEDSTATUSCODES
Sat 2023-03-04 11:23:19.067: [926687] --> 250-STARTTLS
Sat 2023-03-04 11:23:19.067: [926687] --> 250 SIZE 36700160
Sat 2023-03-04 11:23:19.369: [926687] <-- STARTTLS
Sat 2023-03-04 11:23:19.370: [926687] --> 220 2.7.0 Ready to start TLS
Sat 2023-03-04 11:23:19.986: [926687] SSL negotiation successful (TLS 1.2, 255
bit key exchange, 256 bit AES encryption)
Sat 2023-03-04 11:23:20.288: [926687] <-- EHLO o8.sg.booking.com
Sat 2023-03-04 11:23:20.288: [926687] --> 250-mail.sentosagroup.com Hello
o8.sg.booking.com [192.254.126.47], pleased to meet you
Sat 2023-03-04 11:23:20.288: [926687] --> 250-ETRN
Sat 2023-03-04 11:23:20.288: [926687] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Sat 2023-03-04 11:23:20.288: [926687] --> 250-8BITMIME
Sat 2023-03-04 11:23:20.288: [926687] --> 250-ENHANCEDSTATUSCODES
Sat 2023-03-04 11:23:20.288: [926687] --> 250 SIZE 36700160
Sat 2023-03-04 11:23:20.608: [926687] <-- MAIL
FROM:<bounces+29053625-f55c-reservation-manado=luleyhotels....@sg.booking.com>
BODY=8BITMIME
Sat 2023-03-04 11:23:20.613: [926687] Performing PTR lookup
(47.126.254.192.IN-ADDR.ARPA)
Sat 2023-03-04 11:23:20.839: [926687] * D=47.126.254.192.IN-ADDR.ARPA TTL=(15)
PTR=[o8.sg.booking.com]
Sat 2023-03-04 11:23:20.863: [926687] * D=o8.sg.booking.com TTL=(15)
A=[192.254.126.47]
Sat 2023-03-04 11:23:20.863: [926687] ---- End PTR results
Sat 2023-03-04 11:23:20.868: [926687] Performing IP lookup (o8.sg.booking.com)
Sat 2023-03-04 11:23:20.871: [926687] * D=o8.sg.booking.com TTL=(15)
A=[192.254.126.47]
Sat 2023-03-04 11:23:20.871: [926687] ---- End IP lookup results
Sat 2023-03-04 11:23:20.877: [926687] Performing IP lookup (sg.booking.com)
Sat 2023-03-04 11:23:21.037: [926687] * P=020 S=001
D=u58461.wl212.sendgrid.net TTL=(16) MX=[mx.sendgrid.net] {167.89.123.50}
Sat 2023-03-04 11:23:21.037: [926687] ---- End IP lookup results
Sat 2023-03-04 11:23:21.039: [926687] Performing SPF lookup (o8.sg.booking.com
/ 192.254.126.47)
Sat 2023-03-04 11:23:21.112: [926687] * Result: none; no SPF record in DNS
Sat 2023-03-04 11:23:21.112: [926687] ---- End SPF results
Sat 2023-03-04 11:23:21.112: [926687] Performing SPF lookup (sg.booking.com /
192.254.126.47)
Sat 2023-03-04 11:23:21.119: [926687] * Policy: v=spf1 include:sendgrid.net
~all
Sat 2023-03-04 11:23:21.119: [926687] * Evaluating include:sendgrid.net:
performing lookup
Sat 2023-03-04 11:23:21.125: [926687] * Policy: v=spf1 ip4:167.89.0.0/17
ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21
ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16
include:ab.sendgrid.net ~all
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating ip4:167.89.0.0/17: no
match
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating ip4:208.117.48.0/20: no
match
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating ip4:50.31.32.0/19: no
match
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating ip4:198.37.144.0/20: no
match
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating ip4:198.21.0.0/21: no
match
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating ip4:192.254.112.0/20:
match
Sat 2023-03-04 11:23:21.125: [926687] * Evaluating include:sendgrid.net: match
Sat 2023-03-04 11:23:21.125: [926687] * Result: pass
Sat 2023-03-04 11:23:21.125: [926687] ---- End SPF results
Sat 2023-03-04 11:23:21.126: [926687] --> 250 2.1.0 Sender OK
Sat 2023-03-04 11:23:21.426: [926687] <-- RCPT
TO:<reservation-man...@luleyhotels.com>
Sat 2023-03-04 11:23:21.446: [926687] Performing DNS-BL lookup (192.254.126.47
- connecting IP)
Sat 2023-03-04 11:23:21.468: [926687] * cbl.abuseat.org - passed
Sat 2023-03-04 11:23:21.711: [926687] * b.barracudacentral.org - passed
Sat 2023-03-04 11:23:21.733: [926687] * zen.spamhaus.org - passed
Sat 2023-03-04 11:23:21.733: [926687] ---- End DNS-BL results
Sat 2023-03-04 11:23:21.740: [926687] --> 250 2.1.5 Recipient OK
Sat 2023-03-04 11:23:22.041: [926687] <-- DATA
Sat 2023-03-04 11:23:22.042: [926687] Creating temp file (SMTP):
d:\mdaemon\queues\temp\md50000001974.tmp
Sat 2023-03-04 11:23:22.042: [926687] --> 354 Enter mail, end with <CRLF>.<CRLF>
Sat 2023-03-04 11:23:22.593: [926687] Message size: 17440 bytes
Sat 2023-03-04 11:23:22.597: [926687] Performing DKIM lookup
Sat 2023-03-04 11:23:22.597: [926687] * File:
d:\mdaemon\queues\temp\md50000001974.tmp
Sat 2023-03-04 11:23:22.597: [926687] * Message-ID:
<ZYk_fnSxTVicFSA9wCQ1aw@geopod-ismtpd-10>
Sat 2023-03-04 11:23:22.630: [926687] * DKIM-Signature 1: v=1; a=rsa-sha256;
c=relaxed/relaxed; d=booking.com; s=s1; <some tags are not logged>
Sat 2023-03-04 11:23:22.630: [926687] * Verification result: good signature
Sat 2023-03-04 11:23:22.631: [926687] * Result: pass
Sat 2023-03-04 11:23:22.631: [926687] ---- End DKIM results
Sat 2023-03-04 11:23:22.643: [926687] Performing DMARC processing
Sat 2023-03-04 11:23:22.643: [926687] * File:
d:\mdaemon\queues\temp\md50000001974.tmp
Sat 2023-03-04 11:23:22.643: [926687] * Message-ID:
<ZYk_fnSxTVicFSA9wCQ1aw@geopod-ismtpd-10>
Sat 2023-03-04 11:23:22.643: [926687] * Author domain: booking.com
Sat 2023-03-04 11:23:22.643: [926687] * Organizational domain: booking.com
Sat 2023-03-04 11:23:22.643: [926687] * Query domain: _dmarc.booking.com
Sat 2023-03-04 11:23:22.650: [926687] * Policy record: v=DMARC1; p=reject;
rua=mailto:dmarc_...@emaildefense.proofpoint.com,mailto:book...@dmarc.postmastery.eu;
ruf=mailto:dmarc_...@emaildefense.proofpoint.com
Sat 2023-03-04 11:23:22.658: [926687] * Verifying report recipient:
dmarc_...@emaildefense.proofpoint.com
Sat 2023-03-04 11:23:22.658: [926687] * Query domain:
booking.com._report._dmarc.emaildefense.proofpoint.com
Sat 2023-03-04 11:23:22.738: [926687] * Policy record: v=DMARC1;
Sat 2023-03-04 11:23:22.738: [926687] * Recipient
dmarc_...@emaildefense.proofpoint.com is verified
Sat 2023-03-04 11:23:22.742: [926687] * Verifying report recipient:
book...@dmarc.postmastery.eu
Sat 2023-03-04 11:23:22.742: [926687] * Query domain:
booking.com._report._dmarc.dmarc.postmastery.eu
Sat 2023-03-04 11:23:23.095: [926687] * Policy record: v=DMARC1
Sat 2023-03-04 11:23:23.095: [926687] * Recipient
book...@dmarc.postmastery.eu is verified
Sat 2023-03-04 11:23:23.104: [926687] * Verifying report recipient:
dmarc_...@emaildefense.proofpoint.com
Sat 2023-03-04 11:23:23.104: [926687] * Query domain:
booking.com._report._dmarc.emaildefense.proofpoint.com
Sat 2023-03-04 11:23:23.108: [926687] * Policy record: v=DMARC1;
Sat 2023-03-04 11:23:23.109: [926687] * Recipient
dmarc_...@emaildefense.proofpoint.com is verified
Sat 2023-03-04 11:23:23.109: [926687] * Checking authentication mechanisms for
DMARC alignment
Sat 2023-03-04 11:23:23.118: [926687] * SPF: domain "sg.booking.com" passed
SPF check; and domain is DMARC aligned
Sat 2023-03-04 11:23:23.120: [926687] * DKIM: domain "booking.com" (from d=
of signature #1) verified; and domain is DMARC aligned
Sat 2023-03-04 11:23:23.121: [926687] * Result: pass
Sat 2023-03-04 11:23:23.121: [926687] ---- End DMARC results
Sat 2023-03-04 11:23:23.391: [926687] Message creation successful:
d:\mdaemon\queues\inbound\md50000404413.msg
Sat 2023-03-04 11:23:23.392: [926687] --> 250 2.6.0 Ok, message saved
<Message-ID: <ZYk_fnSxTVicFSA9wCQ1aw@geopod-ismtpd-10>>
Sat 2023-03-04 11:23:23.449: [926687] <-- QUIT
Sat 2023-03-04 11:23:23.449: [926687] --> 221 2.0.0 See ya in cyberspace
Sat 2023-03-04 11:23:23.450: [926687] SMTP session successful (Bytes in/out:
18354/2262)
Sat 2023-03-04 11:23:23.451: ----------
