[mdaemon-l] Lambat / Delay Penerimaan Email

2021-02-02 Terurut Topik Syafril Hermansyah via mdaemon-l
On 03/02/21 14.40, Bonar Gultom via mdaemon-l wrote:
> Pertanyaan berikutnya bagaimana mem bypass spf verification dari sender/domain
> tertentu, karena saya lihat di log cukup memakan waktu juga untuk memproses
> emailnya (+60 detik utk setiap dns response exceeded). berikut ini contoh log
> smtp-in nya
> 
> Wed 2021-02-03 14:15:16.960: [569442] <-- EHLO mail-qt1-f174.google.com
> Wed 2021-02-03 14:15:16.961: [569442] Performing SPF lookup
> (mail-qt1-f174.google.com / 209.85.160.174)
> Wed 2021-02-03 14:16:16.961: [569442] *  DNS: 60 second wait for DNS response
> exceeded (DNS Server: 8.8.8.8)
> Wed 2021-02-03 14:17:16.962: [569442] *  DNS: 60 second wait for DNS response
> exceeded (DNS Server: 8.8.4.4)
> Wed 2021-02-03 14:18:17.055: [569442] *  DNS: 60 second wait for DNS response
> exceeded (DNS Server: 1.1.1.1)


Sender host mail-qt1-f174.google.com memang tidak punya SPF record, jadi sudah
betul hasil resolve nya.

$ host -t txt mail-qt1-f174.google.com
mail-qt1-f174.google.com has no TXT record

> saya sudah mengisi spf exception list dengan isian sbb:
> *@gmail.com
> *@google.com
> *@outlook.com
> apakah sudah sesuai pak?


Tidak benar.
Kalau ingin tidak check SPF sender host maka non aktifkan.

http://mdaemon.dutaint.co.id/mdaemon/20.0/index.html?security--spf__sender_id.htm

[ ] Apply SPF processing to HELO/EHLO value


-- 
syafril

Syafril Hermansyah

MDaemon-L Moderator, run MDaemon 21.0 64bit
Mohon tidak kirim private mail (atau cc:) untuk masalah MDaemon.

We are products of our past, but we don't have to be prisoners of it.
--- Rick Warren



-- 
--[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] Lambat / Delay Penerimaan Email

2021-02-02 Terurut Topik Bonar Gultom via mdaemon-l
Dari hasil test saya barusan, yang bermasalah adalah setting SOA DNS yang tidak
(lagi) terdaftar di internet sehingga internet node (terkadang) kesulitan (lama)
resolve.

$ host -t soa ciputra.co.id
ciputra.co.id has SOA record masterdns.ciputra.co.id. root.ciputra.co.id.
20171206 3600 1800 604800 3600

$ host -t a masterdns.ciputra.co.id
Host masterdns.ciputra.co.id not found: 3(NXDOMAIN)

$ host -t a masterdns.ciputra.co.id ns1.ciputragroup.com
Using domain server:
Name: ns1.ciputragroup.com
Address: 202.51.104.180#53
Aliases:

Host masterdns.ciputra.co.id not found: 3(NXDOMAIN)

Diperbaiki saja setting Name Server, khususnya SOA DNS nya.

Terima kasih bantuannya pak, saya sudah coba perbaiki setting NS nya, dan 
sepertinya sudah ada peningkatan di waktu penerimaan email.

Pertanyaan berikutnya bagaimana mem bypass spf verification dari sender/domain 
tertentu, karena saya lihat di log cukup memakan waktu juga untuk memproses 
emailnya (+60 detik utk setiap dns response exceeded). berikut ini contoh log 
smtp-in nya

Wed 2021-02-03 14:15:16.721: [569442] Session 569442; child 0113
Wed 2021-02-03 14:15:16.721: [569442] Accepting SMTP connection from 
209.85.160.174:41597 to 172.16.10.10:25
Wed 2021-02-03 14:15:16.722: [569442] --> 220 mail.ciputra.co.id ESMTP MDaemon 
17.5.3; Wed, 03 Feb 2021 14:15:16 +0700
Wed 2021-02-03 14:15:16.960: [569442] <-- EHLO mail-qt1-f174.google.com
Wed 2021-02-03 14:15:16.961: [569442] Performing SPF lookup 
(mail-qt1-f174.google.com / 209.85.160.174)
Wed 2021-02-03 14:16:16.961: [569442] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 8.8.8.8)
Wed 2021-02-03 14:17:16.962: [569442] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 8.8.4.4)
Wed 2021-02-03 14:18:17.055: [569442] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 1.1.1.1)
Wed 2021-02-03 14:18:47.072: [569442] *  Result: none; no SPF record in DNS
Wed 2021-02-03 14:18:47.072: [569442]  End SPF results
Wed 2021-02-03 14:18:47.072: [569442] --> 250-mail.ciputra.co.id Hello 
mail-qt1-f174.google.com [209.85.160.174], pleased to meet you
Wed 2021-02-03 14:18:47.072: [569442] --> 250-ETRN
Wed 2021-02-03 14:18:47.072: [569442] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Wed 2021-02-03 14:18:47.072: [569442] --> 250-8BITMIME
Wed 2021-02-03 14:18:47.072: [569442] --> 250-ENHANCEDSTATUSCODES
Wed 2021-02-03 14:18:47.072: [569442] --> 250-STARTTLS
Wed 2021-02-03 14:18:47.072: [569442] --> 250 SIZE 2560
Wed 2021-02-03 14:18:47.311: [569442] <-- STARTTLS
Wed 2021-02-03 14:18:47.311: [569442] --> 220 2.7.0 Ready to start TLS
Wed 2021-02-03 14:18:47.793: [569442] SSL negotiation successful (TLS 1.2, 256 
bit key exchange, 256 bit AES encryption)
Wed 2021-02-03 14:18:48.034: [569442] <-- EHLO mail-qt1-f174.google.com
Wed 2021-02-03 14:18:48.034: [569442] Performing SPF lookup 
(mail-qt1-f174.google.com / 209.85.160.174)
Wed 2021-02-03 14:19:48.034: [569442] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 8.8.8.8)
Wed 2021-02-03 14:19:48.203: [569442] *  Result: none; no SPF record in DNS
Wed 2021-02-03 14:19:48.203: [569442]  End SPF results
Wed 2021-02-03 14:19:48.203: [569442] --> 250-mail.ciputra.co.id Hello 
mail-qt1-f174.google.com [209.85.160.174], pleased to meet you
Wed 2021-02-03 14:19:48.203: [569442] --> 250-ETRN
Wed 2021-02-03 14:19:48.203: [569442] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Wed 2021-02-03 14:19:48.203: [569442] --> 250-8BITMIME
Wed 2021-02-03 14:19:48.203: [569442] --> 250-ENHANCEDSTATUSCODES
Wed 2021-02-03 14:19:48.203: [569442] --> 250 SIZE 2560
Wed 2021-02-03 14:19:48.438: [569442] <-- MAIL FROM: 
SIZE=2710
Wed 2021-02-03 14:19:48.438: [569442] Performing PTR lookup 
(174.160.85.209.IN-ADDR.ARPA)
Wed 2021-02-03 14:19:48.454: [569442] *  D=174.160.85.209.IN-ADDR.ARPA 
TTL=(328) PTR=[mail-qt1-f174.google.com]
Wed 2021-02-03 14:19:48.472: [569442] *  D=mail-qt1-f174.google.com TTL=(285) 
A=[209.85.160.174]
Wed 2021-02-03 14:19:48.472: [569442]  End PTR results
Wed 2021-02-03 14:19:48.472: [569442] Performing IP lookup 
(mail-qt1-f174.google.com)
Wed 2021-02-03 14:19:48.489: [569442] *  D=mail-qt1-f174.google.com TTL=(356) 
A=[209.85.160.174]
Wed 2021-02-03 14:19:48.489: [569442]  End IP lookup results
Wed 2021-02-03 14:19:48.490: [569442] Performing IP lookup (gmail.com)
Wed 2021-02-03 14:19:48.506: [569442] *  D=gmail.com TTL=(2) A=[172.217.194.19]
Wed 2021-02-03 14:19:48.506: [569442] *  D=gmail.com TTL=(2) A=[172.217.194.17]
Wed 2021-02-03 14:19:48.506: [569442] *  D=gmail.com TTL=(2) A=[172.217.194.18]
Wed 2021-02-03 14:19:48.506: [569442] *  D=gmail.com TTL=(2) A=[172.217.194.83]
Wed 2021-02-03 14:19:48.523: [569442] *  P=005 S=004 D=gmail.com TTL=(46) 
MX=[gmail-smtp-in.l.google.com]
Wed 2021-02-03 14:19:48.523: [569442] *  P=010 S=000 D=gmail.com TTL=(46) 
MX=[alt1.gmail-smtp-in.l.google.com]
Wed 2021-02-03 14:19:48.523: [569442] *  P=020 S=001 D=gmail.com TTL=(46) 
MX=[alt2.gmail-smtp-in.l.google.com]
Wed 2021-02-03 14:19:48.523: 

[mdaemon-l] Permanent Delivery Failure

2021-02-02 Terurut Topik Syafril Hermansyah via mdaemon-l
On 02/02/21 16.14, Anto wrote:
> Pak mau tanya ada user kami setiap hari terima email yang sama jumlahnya 
> 200-an
> (contoh email error dari Mdaemon terlampir)
> 
> Padahal user kami merasa tidak  mengirimkan ke email tersebut, mohon bantuan 
> dan
> pencerahannya.


Itu akibat akun ye...@advanceproduct.com terhijack.

Aktifkan Strong Password requirement di MDaemon, setelah itu ganti password akun
yang terhijack dengan strong password.

http://mdaemon.dutaint.co.id/mdaemon/20.0/index.html?passwords.htm

[x] Require strong passwords

Prosedur lengkapnya bisa baca disini

https://www.mail-archive.com/mdaemon-l@dutaint.com/msg44536.html


-- 
syafril

Syafril Hermansyah

MDaemon-L Moderator, run MDaemon 21.0 64bit
Mohon tidak kirim private mail (atau cc:) 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.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] Permanent Delivery Failure

2021-02-02 Terurut Topik Anto
Dear Pak Syafril,

 

Pak mau tanya ada user kami setiap hari terima email yang sama jumlahnya
200-an (contoh email error dari Mdaemon terlampir)

Padahal user kami merasa tidak  mengirimkan ke email tersebut, mohon bantuan
dan pencerahannya.

 

 

Thanks & Best Regards,

 

Anto



This e-mail message (including any attachments) is confidential and for use by 
the addressee only. If the message is received by anyone other than the 
addressee, please return the message to the sender by replying to it and then 
delete the message from your computer. Any unauthorised use or dissemination of 
this message (including any attachments) in whole or in part is strictly 
prohibited.  Internet e-mails are not necessarily secure and are susceptible to 
change. PT. Semangat Sejahtera Bersama does not accept responsibility for 
changes made to this message after it was sent. Whilst all reasonable care has 
been taken to avoid the transmission of viruses, it is the responsibility of 
the recipient to ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its systems or data. No 
responsibility is accepted by PT. Semangat Sejahtera Bersama in this regard and 
the recipient should carry out such virus and other checks as it considers 
appropriate. PT. Semangat Sejahtera Bersama does not also accept responsibility 
for the improper or incomplete transmission of the information contained in 
this communication nor for any delay in its receipt or damage to your system 
and does not guarantee that the integrity of this communication has been 
maintained. Visit our website at www.advanceproduct.com
 
 
 
-Original Message-
From: MDaemon at mail.advanceproduct.com 
Sent: Selasa, 02 Februari 2021 13.46
To: prvs=1667176f04=ye...@advanceproduct.com
Subject: Permanent Delivery Failure

--
MDaemon Delivery Status Notification - http://www.altn.com/dsn/
--

The attached message had PERMANENT fatal delivery errors.

After one or more unsuccessful delivery attempts the attached message has been 
removed from the MDaemon mail queue on this server.  The number and frequency 
of delivery attempts are determined by local configuration.

--
YOUR MESSAGE WAS NOT DELIVERED TO ONE OR MORE RECIPIENTS
--

Failed address: p...@xxballs.com

--- Session Transcript ---
 Tue 2021-02-02 13:45:23: [262794] Session 262794; child 0037  Tue
2021-02-02 13:45:23: [262794] Parsing message 

 Tue 2021-02-02 13:45:23: [262794] *  From: ye...@advanceproduct.com  Tue
2021-02-02 13:45:23: [262794] *  To: p...@xxballs.com  Tue 2021-02-02
13:45:23: [262794] *  Subject: ??:?(OD119055105170267000)  Tue
2021-02-02 13:45:23: [262794] *  Size (bytes): 11503  Tue 2021-02-02
13:45:23: [262794] *  Message-ID:
<20210201223658.9db3888ab2106...@advanceproduct.com>
 Tue 2021-02-02 13:45:23: [262794] Attempting SMTP connection to [xxballs.com]  
Tue 2021-02-02 13:45:23: [262794] Resolving MX records for [xxballs.com] (DNS 
Server: 202.146.255.3)...
 Tue 2021-02-02 13:45:23: [262794] *  P=010 S=000 D=xxballs.com TTL=(51) 
MX=[mx184.cn4e.com]  Tue 2021-02-02 13:45:23: [262794] Attempting SMTP 
connection to [mx184.cn4e.com:25]  Tue 2021-02-02 13:45:23: [262794] Resolving 
A record for [mx184.cn4e.com] (DNS Server: 202.146.255.3)...
 Tue 2021-02-02 13:45:23: [262794] *  D=mx184.cn4e.com TTL=(1) 
A=[118.145.2.185]  Tue 2021-02-02 13:45:23: [262794] Attempting SMTP connection 
to [118.145.2.185:25]  Tue 2021-02-02 13:45:23: [262794] Waiting for socket 
connection...
 Tue 2021-02-02 13:45:26: [262794] *  Connection established
(131.10.1.25:62217 -> 118.145.2.185:25)  Tue 2021-02-02 13:45:26: [262794] 
Waiting for protocol to start...
 Tue 2021-02-02 13:45:33: [262794] <-- 220 smail133.cn4e.com ESMTP
Bordeaux@35(7.3.0.15a)  Tue 2021-02-02 13:45:33: [262794] --> EHLO 
mail.advanceproduct.com  Tue 2021-02-02 13:45:41: [262794] <-- 
250-smail133.cn4e.com  Tue 2021-02-02 13:45:41: [262794] <-- 250-8BITMIME Tue 
2021-02-02 13:45:41: [262794] <-- 250-SIZE 3758096384  Tue 2021-02-02
13:45:41: [262794] <-- 250-STARTTLS  Tue 2021-02-02 13:45:41: [262794] <-- 
250-AUTH LOGIN PLAIN  Tue 2021-02-02 13:45:41: [262794] <-- 250-AUTH=LOGIN 
PLAIN  Tue 2021-02-02 13:45:41: [262794] <-- 250 OK  Tue 2021-02-02
13:45:41: [262794] --> STARTTLS  Tue 2021-02-02 13:45:41: [262794] <-- 220 
STL:RD Ready to start TLS  Tue 2021-02-02 13:45:42: [262794] SSL negotiation 
successful (TLS 1.0, 2048 bit key exchange, 128 bit AES encryption)  Tue
2021-02-02 13:45:42: [262794] --> EHLO mail.advanceproduct.com  Tue
2021-02-02 13:45:43: [262794] <-- 250-smail133.cn4e.com  Tue 2021-02-02
13:45:43: [262794] <-- 250-8BITMIME  Tue 2021-02-02 13:45:43: [262794] <-- 

[mdaemon-l] Lambat / Delay Penerimaan Email

2021-02-02 Terurut Topik Syafril Hermansyah via mdaemon-l
On 02/02/21 14.54, Bonar Gultom via mdaemon-l wrote:
> User kami seringkali terlambat terima email dari domain eksternal (gmail, 
> yahoo,
> dll) , bisa terlambat 30menit s/d berjam-jam. Mohon analisisnya pak. Namun 
> kasus
> ini tidak ditemukan :


> From: "bonar.gul...@gmail.com -- Bonar Gultom" 
> Date: Tue, 2 Feb 2021 08:37:07 +0700

> X-Received: by 2002:a05:620a:10a2:: with SMTP id 
> h2mr19009935qkk.463.1612229840728;
>  Mon, 01 Feb 2021 17:37:20 -0800 (PST)

> Received: by mail-qt1-f169.google.com with SMTP id e15so13917330qte.9
>  for ; Mon, 01 Feb 2021 18:26:48 -0800 (PST)

Ini yang lama proses di internal googlemail.com, butuh waktu 49 menit 41 detik
untuk sampai di outgoing server.

> X-MDArrival-Date: Tue, 02 Feb 2021 09:26:57 +0700


Proses pengiriman mail dari google outgoing mail ke MDameon mail.ciputra.co.id
butuh waktu 9 detik saja.
Dengan demikian masalahnya bukan di bandwidth, tetapi di Name Server
(authoritative DNS server) domain ciputra.co.id yang lambat response atau sibuk.

Dari hasil test saya barusan, yang bermasalah adalah setting SOA DNS yang tidak
(lagi) terdaftar di internet sehingga internet node (terkadang) kesulitan (lama)
resolve.

$ host -t soa ciputra.co.id
ciputra.co.id has SOA record masterdns.ciputra.co.id. root.ciputra.co.id.
20171206 3600 1800 604800 3600

$ host -t a masterdns.ciputra.co.id
Host masterdns.ciputra.co.id not found: 3(NXDOMAIN)

$ host -t a masterdns.ciputra.co.id ns1.ciputragroup.com
Using domain server:
Name: ns1.ciputragroup.com
Address: 202.51.104.180#53
Aliases:

Host masterdns.ciputra.co.id not found: 3(NXDOMAIN)

Diperbaiki saja setting Name Server, khususnya SOA DNS nya.

>  Namun kasus ini tidak ditemukan :
> 
> pada saat kirim email di malam hari / pagi hari
> saat dikirim dari domain kami yang dihosting di office 365.


Itu kebetulan saja sedang beruntung atau karena DNS cache di server yang jadi
acuan server office365 menyimpan lebih lama.


-- 
syafril

Syafril Hermansyah

MDaemon-L Moderator, run MDaemon 21.0 64bit
Mohon tidak kirim private mail (atau cc:) untuk masalah MDaemon.

Never give up on anything.
If you fail, try, try and try again.
You are learning the best ways of doing things.
--- Lailah Gifty Akita



-- 
--[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