On 9/12/24 15:37, mauritz devis 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!"
Gunakan fitur di webmail gmail untuk kemudahan melakukan bottom posting
dan pemangkasan (trimming) teks.
http://webapps.stackexchange.com/questions/49884/how-to-insert-a-reply-inline-in-gmail
---
Masih belum berhasil mengirimkan email, walaupun hasil test pengiriman
ke gmail sukses dan DNS DMARC sudah dirubah sesuai petunjuk.
Perlihatkan DSN/Bounce lengkap yang terakhir diterima kesini.
Sekarang ada account selain [email protected]
<mailto:[email protected]> yg mengalami error yg sama yaitu
account [email protected]
<mailto:[email protected]>
Saya lampirkan error pengiriman email..
Your message wasn't delivered because the recipient's email provider rejected
it.
Generating server: AM9PR06MB8179.eurprd06.prod.outlook.com
[email protected]
Remote server returned '550 5.7.509 Access denied, sending domain musica-st=
udios.co.id does not pass DMARC verification and has a DMARC policy of reje=
ct.'
From: [email protected]
To: [email protected]
Return-Path:
326HiZg4UAOYgWcbcJM_UcaQKIUcaQKI-abcLQWa.KW.QL@youtube-partner-fe.b=
ounces.google.com
Mail ini tidak di reject dengan alasan DKIM verification failed, tetapi
DMARC failed.
Penyebab DMARC failed karena sender menggunakan isian reply to address
<326hizg4uaoygwcbcjm_ucaqkiucaqki-abclqwa.kw...@youtube-partner-fe.bounces.google.com>.
DSN/bounce itu aslinya ditujukan ke
326hizg4uaoygwcbcjm_ucaqkiucaqki-abclqwa.kw...@youtube-partner-fe.bounces.google.com
dari alamat itu autoforward ke [email protected].
From: <[email protected]>
To:
<326hizg4uaoygwcbcjm_ucaqkiucaqki-abclqwa.kw...@youtube-partner-fe.bounces.google.com>
Date: Thu, 12 Sep 2024 08:10:08 +0000
X-Forwarded-Encrypted: i=3;
AJvYcCXjdJGyOE/NJbfVUOX4pu/jdQjPBagJ8yrinrsciIQ/4+iiAbErGSdK9fhyRmUDkkrpGQFqrO8QMLW+y3h4Ag==@musica-studios.co.id
Di kasus ini akan lebih baik jika DMARC di set align dengan DKIM.
Dan karena sekarang DKIM domain musica-studios.co.id sudah baik/benar,
maka bisa dikembalikan DNS DMARC nya ke semula
_dmarc.musica-studios.co.id descriptive text "v=DMARC1; p=reject;
sp=none; rua=mailto:[email protected]";
atau
"v=DMARC1; p=reject; aspf=s; adkim=s; sp=none;
rua=mailto:[email protected]";
alasannya, agar DKIM success -> DMARC juga sukses.
https://postmarkapp.com/blog/forwarding-emails-dmarc-failure
What can you, as a sender, do about this?#
There isn’t a surefire way to prevent this, but the good news is that
DMARC only requires that either DKIM or SPF pass, not both. This is why
it’s important (where possible) to have both DKIM and SPF set up: if one
breaks due to a forward, the message still passes DMARC.
------------------------------------------------------------------------
--
syafril
--------
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 24.5.0 Beta RC1
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.
Don’t worry about failures, worry about the chances you miss when you
don’t even try.
--- Jack Canfield
--
--[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 [email protected]
Henti Langgan: Kirim mail ke [email protected]
Versi terakhir: MDaemon 24.0.2, SecurityGateway 10.0.3
