Infrastruktur

Pada 26 Desember 2025 pukul 16.04 UTC, saya mendapat surel dengan header from berasal dari domain nawan.my.id. Saya 100% yakin bahwa surel tersebut bukan berasal dari server yang diotorisasi untuk mengirimkan surel dengan domain tersebut.

Return-Path: <>
Delivered-To: saya@nawan.my.id
Received: from dasg1.hostypanel.com
        by dasg1.hostypanel.com with LMTP
        id oQfWIguyTmm6SCwAyKa16w
        (envelope-from <>)
        for <saya@nawan.my.id>; Fri, 26 Dec 2025 16:04:27 +0000
Return-path: <>
Envelope-to: saya@nawan.my.id
Delivery-date: Fri, 26 Dec 2025 16:04:27 +0000
Received: from 126.213.198.35.bc.googleusercontent.com ([35.198.213.126] helo=[10.88.0.4])
        by dasg1.hostypanel.com with esmtp (Exim 4.98.2)
        id 1vZAIl-0000000CHY8-2JgC
        for saya@nawan.my.id;
        Fri, 26 Dec 2025 16:04:27 +0000
Content-Type: multipart/related; boundary="===============8232434614055157391=="
MIME-Version: 1.0
From: Agency Info <saya@nawan.my.id>
To: saya@nawan.my.id
Subject: =?utf-8?b?UmU6?=
Reply-To: your-email@yourdomain.com
X-Priority: 2
Message-ID: <GENERATED-WASMISSING-1vZAIl-0000000CHY8-2JgC@dasg1.hostypanel.com>
X-ACL-Warn: Adding Message-ID header because it is missing!

--===============8232434614055157391==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64

SGVsbG8u

--===============8232434614055157391==--

Sepertinya harus merombak DMARC. Aturan DMARC saat ini sangat permisif.

; <<>> DiG 9.20.15-1~deb13u1-Debian <<>> TXT _dmarc.nawan.my.id
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36166
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;_dmarc.nawan.my.id.		IN	TXT

;; ANSWER SECTION:
_dmarc.nawan.my.id.	3600	IN	TXT	"v=DMARC1;p=none"

;; Query time: 322 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Fri Dec 26 23:20:53 WIB 2025
;; MSG SIZE  rcvd: 75