[Mdaemon-L] Gagal terima email

2022-11-14 Terurut Topik Syafril Hermansyah via Mdaemon-L 

On 11/15/22 09:42, budi...@geodipa.co.id wrote:

Mohon dapat dibantu, ada email yang tdk bs kami terima, berikut lognya :




Mon 2022-11-14 20:13:55.371: [21513591] <-- MAIL 
FROM: SIZE=7182 BODY=8BITMIME
Mon 2022-11-14 20:13:55.799: [21513591] <-- RCPT TO:
Mon 2022-11-14 20:13:56.313: [21513591] --> 250 2.6.0 Ok, message saved >



Mail ini diterima dengan baik oleh MDaemon mail.geodipa.co.id.

Kalau recipient tidak melihatnya di inbox folder, bisa periksa ke Junk 
Email foldernya, kalau pakai IMAP atau mobile device minta periksa juga 
ke Junk Email folder di webmail.


Kalau tidak ketemua juga, maka Anda perlu periksa ke Routing log 2022-11-14.

--
syafril

Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 22.5.0 Beta RC1
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

Learn from yesterday, live for today, hope for tomorrow. The important 
thing is not to stop questioning.

--- Albert Einstein


--
--[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 22.0.3, SecurityGateway 8.5.3

[Mdaemon-L] Gagal terima email

2022-11-14 Terurut Topik budi_it 
Dear pak Syafril,

 

Mohon dapat dibantu, ada email yang tdk bs kami terima, berikut lognya :

 

Mon 2022-11-14 20:13:54.177: --

Mon 2022-11-14 20:13:55.320: [21513591] Session 21513591; child 0002

Mon 2022-11-14 20:13:55.321: [21513591] Accepting SMTP connection from
103.85.66.120:37310 to 182.23.2.148:25

Mon 2022-11-14 20:13:55.321: [21513591] Location Screen says connection is
from Indonesia, Asia

Mon 2022-11-14 20:13:55.321: [21513591] --> 220 mail.geodipa.co.id ESMTP
MDaemon 22.0.3; Mon, 14 Nov 2022 20:13:55 +0700

Mon 2022-11-14 20:13:55.330: [21513591] <-- EHLO smtp.mayapadahospital.com

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-mail.geodipa.co.id Hello
smtp.mayapadahospital.com [103.85.66.120], pleased to meet you

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-ETRN

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-AUTH LOGIN PLAIN

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-8BITMIME

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-ENHANCEDSTATUSCODES

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-PIPELINING

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-CHUNKING

Mon 2022-11-14 20:13:55.330: [21513591] --> 250-STARTTLS

Mon 2022-11-14 20:13:55.330: [21513591] --> 250 SIZE 31457280

Mon 2022-11-14 20:13:55.335: [21513591] <-- STARTTLS

Mon 2022-11-14 20:13:55.335: [21513591] --> 220 2.7.0 Ready to start TLS

Mon 2022-11-14 20:13:55.360: [21513591] SSL negotiation successful (TLS 1.2,
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521)

Mon 2022-11-14 20:13:55.366: [21513591] <-- EHLO smtp.mayapadahospital.com

Mon 2022-11-14 20:13:55.366: [21513591] --> 250-mail.geodipa.co.id Hello
smtp.mayapadahospital.com [103.85.66.120], pleased to meet you

Mon 2022-11-14 20:13:55.366: [21513591] --> 250-ETRN

Mon 2022-11-14 20:13:55.366: [21513591] --> 250-AUTH LOGIN PLAIN

Mon 2022-11-14 20:13:55.366: [21513591] --> 250-8BITMIME

Mon 2022-11-14 20:13:55.367: [21513591] --> 250-ENHANCEDSTATUSCODES

Mon 2022-11-14 20:13:55.367: [21513591] --> 250-PIPELINING

Mon 2022-11-14 20:13:55.367: [21513591] --> 250-CHUNKING

Mon 2022-11-14 20:13:55.367: [21513591] --> 250 SIZE 31457280

Mon 2022-11-14 20:13:55.371: [21513591] <-- MAIL
FROM: SIZE=7182 BODY=8BITMIME

Mon 2022-11-14 20:13:55.377: [21513591] Performing PTR lookup
(120.66.85.103.IN-ADDR.ARPA)

Mon 2022-11-14 20:13:55.749: [21513591] *  D=120.66.85.103.IN-ADDR.ARPA
TTL=(60) PTR=[mail.mayapadahospital.com]

Mon 2022-11-14 20:13:55.753: [21513591] *  D=mail.mayapadahospital.com
TTL=(228) A=[103.85.66.120]

Mon 2022-11-14 20:13:55.753: [21513591]  End PTR results

Mon 2022-11-14 20:13:55.753: [21513591] Performing IP lookup
(smtp.mayapadahospital.com)

Mon 2022-11-14 20:13:55.760: [21513591] *  D=smtp.mayapadahospital.com
TTL=(240) A=[103.85.66.120]

Mon 2022-11-14 20:13:55.760: [21513591]  End IP lookup results

Mon 2022-11-14 20:13:55.768: [21513591] Performing IP lookup
(mayapadahospital.com)

Mon 2022-11-14 20:13:55.771: [21513591] *  D=mayapadahospital.com TTL=(233)
A=[103.85.66.122]

Mon 2022-11-14 20:13:55.774: [21513591] *  P=010 S=000
D=mayapadahospital.com TTL=(232) MX=[mail.mayapadahospital.com]
{103.85.66.120}

Mon 2022-11-14 20:13:55.774: [21513591] *  P=020 S=001
D=mayapadahospital.com TTL=(232)
MX=[mayapadahospital-com.mail.protection.outlook.com]

Mon 2022-11-14 20:13:55.774: [21513591]  End IP lookup results

Mon 2022-11-14 20:13:55.775: [21513591] Performing SPF lookup
(smtp.mayapadahospital.com / 103.85.66.120)

Mon 2022-11-14 20:13:55.783: [21513591] *  Policy: v=spf1 +a +mx
+a:smtp.mayapadahospital.com +mx:smtp.mayapadahospital.com
+ip4:103.85.66.120 +ip4:103.85.66.119 +ip4:103.85.66.98 +ip4:172.16.0.55
+ip4:172.16.0.56 +ip4:172.16.0.57 +ip4:172.16.0.58 +ip4:172.16.0.59
+ip4:172.16.0.60 ~al

Mon 2022-11-14 20:13:55.786: [21513591] *  Evaluating +a: match

Mon 2022-11-14 20:13:55.786: [21513591] *  Result: pass

Mon 2022-11-14 20:13:55.786: [21513591]  End SPF results

Mon 2022-11-14 20:13:55.786: [21513591] Performing SPF lookup
(mayapadahospital.com / 103.85.66.120)

Mon 2022-11-14 20:13:55.791: [21513591] *  Policy: v=spf1 +a +mx
+a:mail.mayapadahospital.com  +mx:mail.mayapadahospital.com
+ip4:103.85.66.120 +ip4:103.85.66.119 +ip4:103.85.66.98 +ip4:172.16.0.55
+ip4:172.16.0.56 +ip4:172.16.0.57 +ip4:172.16.0.58 +ip4:172.16.0.59
+ip4:172.16.0.60 i

Mon 2022-11-14 20:13:55.794: [21513591] *  Evaluating +a: no match

Mon 2022-11-14 20:13:55.799: [21513591] *  Evaluating +mx: match

Mon 2022-11-14 20:13:55.799: [21513591] *  Result: pass

Mon 2022-11-14 20:13:55.799: [21513591]  End SPF results

Mon 2022-11-14 20:13:55.799: [21513591] --> 250 2.1.0 Sender OK

Mon 2022-11-14 20:13:55.799: [21513591] <-- RCPT TO:

Mon 2022-11-14 20:13:55.802: [21513591] Performing DNS-BL lookup
(103.85.66.120 - connecting IP)

Mon 2022-11-14 20:13:56.051: [21513591] *  b.barracudacentral.org - passed

Mon 2022-11-14 20:13:56.069: [21513591] *  zen.spamhaus.org - passed

Mon 2022-11-14 20:13:56.069: [21513591]  End

[Mdaemon-L] Gagal terima email dari domain willistowerswatson.com

2021-12-23 Terurut Topik Syafril Hermansyah via Mdaemon-L 

On 12/23/21 12:05 PM, budi...@geodipa.co.id 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!"

http://daringfireball.net/2007/07/on_top

The fundamental source of poor email style is the practice of quoting
the entire message you’re replying to. If that’s what you do, then it
doesn’t matter whether you put your response at the top or bottom. In
fact, if you’re going to quote the entire message, top-posting probably
is better. But both are poor form.

Writing an email is like writing an article. Only quote the relevant
parts, interspersing your new remarks between the quoted passages. Don’t
quote anything at all from the original message if you don’t have to.

Does it take more time to edit the portions of quoted text included in
your reply? Yes. So does spell-checking and proofreading. It also takes
time to shower and brush your teeth each day.

Di outlook 2013/2016 sudah ada fitur inline reply, tinggal diaktifkan.

http://www.tech-recipes.com/rx/30892/outlook-2013-disable-the-inline-reply-feature/

kalau masih pakai outlook kuno, maka ubah settingnya seperti ini

https://www.slipstick.com/outlook/email/to-use-internet-style-quoting/

Salin selected text yang akan di quote ulang, yang sesuai contex, ke atas
signature lalu hapus quote text yang mulai dari baris "-Original 
Message-" kebawah.




Berikut hasil telnetnya :

PS C:\> test-netconnection -informationlevel detailed -computername
portquiz.net -port 53


ComputerName: portquiz.net
RemoteAddress   : 52.47.209.216
RemotePort  : 53
NameResolutionResults   : 52.47.209.216
MatchingIPsecRules  :
NetworkIsolationContext : Internet
IsAdmin : False
InterfaceAlias  : GDE
SourceAddress   : 192.168.0.214
NetRoute (NextHop)  : 0.0.0.0
TcpTestSucceeded: True



Telnet tcp port 53 nya sukses, tetapi kenapa NetRoute (NextHop) = 
0.0.0.0 bukan IP gateway address?



Untuk DNS di MDaemonnya coba kami hapus sesuai arahan (terlampir).

Dari tindak lanjut di atas, apakah seharusnya email dr
willistowerswatson.com sudah dapat diterima baik?



Ya, mestinya begitu, dengan assumsi OS sudah mendukung DNS over TCP.


PS C:\cygwin64\home\Syafril> nslookup -q=txt willistowerswatson.com 
129.250.35.251

nslookup -q=txt willistowerswatson.com 129.250.35.251
;; Truncated, retrying in TCP mode.
Server: 129.250.35.251
Address:129.250.35.251#53

Non-authoritative answer:
willistowerswatson.com	text = "v=spf1 
include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all"
willistowerswatson.com	text = 
"wiz-domain-verification=7eb292dcdce945c5a2e3766b76a23588adf56b0c719cd95a84d05cf2f2da446a"
willistowerswatson.com	text = 
"1poEwRRTkNf7MdRYd7tVNZkk+hfOOGAVq7ZaYPIzlaXwycUbpD3S6XlXWt18sKNoSZTtsPy7UhUlIFBwSV8rNQ=="
willistowerswatson.com	text = 
"_globalsign-domain-verification=-4vP5eysbT-3Pjcar2QjyLPSK3_bGIhyShtxuN8HUN"
willistowerswatson.com	text = 
"globalsign-domain-verification=90dad3b27bcdc8e2677e16f29675df19"

willistowerswatson.com  text = "a02e0935-98f9-457a-a94f-f656573535af"
willistowerswatson.com	text = 
"onetrust-domain-verification=2792c3463ffd4cf9940e9ee868eb5908"

willistowerswatson.com  text = "apple-domain-verification=hrNPDuZXs7UOvaml"
willistowerswatson.com  text = "c7465ebivt7cl8gq0eh2n5ohhv"
willistowerswatson.com	text = 
"pardot835203=ed27a9dcc3de58bbdc16c0274ea05ba177699284182dfdd0a2dd54ca58adec14"
willistowerswatson.com	text = 
"docusign=47a7b2c4-8332-4471-902a-7751a15c4d64"
willistowerswatson.com	text = 
"A43FC5C95F26A7697D40DD7960139CCBCA7B174137650D5BD07F903233E98FFC"
willistowerswatson.com	text = 
"adobe-idp-site-verification=4e007039-a465-4e6e-b4c2-b353c8d352ac"
willistowerswatson.com	text = 
"_globalsign-domain-verification=u60LWxuznhU4rCQCzkruG9Xlp8UNrXOL5HLHGjc9ZY"
willistowerswatson.com	text = 
"Zm15FvuXSjBjf1GYEuo/bp0KH0MUZNFMi7+Db1zGabBFb0BwVB4mEcUFeWhMwydYmQjNsMKM7eeCDZ1yqOHoVA=="
willistowerswatson.com	text = 
"webexdomainverification.=452e31f1-b505-4fdd-944d-2feecc533b27"

willistowerswatson.com  text = "GlobalSign - 11962"
willistowerswatson.com	text = 
"google-site-verification=vxRT-g2_-MKo9x8hm2JQWtSEQJ54olF1eE_4z4Drh7g"

willistowerswatson.com  text = "2YGPWNyrDWDqz/WD2SkBOKDhcw/XaJIy7UzUQy41poM="
willistowerswatson.com	text =

[Mdaemon-L] Gagal terima email dari domain willistowerswatson.com

2021-12-22 Terurut Topik budi_it 
Dear Pak Syafril,

Berikut hasil telnetnya :

PS C:\> test-netconnection -informationlevel detailed -computername
portquiz.net -port 53


ComputerName: portquiz.net
RemoteAddress   : 52.47.209.216
RemotePort  : 53
NameResolutionResults   : 52.47.209.216
MatchingIPsecRules  :
NetworkIsolationContext : Internet
IsAdmin : False
InterfaceAlias  : GDE
SourceAddress   : 192.168.0.214
NetRoute (NextHop)  : 0.0.0.0
TcpTestSucceeded: True

Untuk DNS di MDaemonnya coba kami hapus sesuai arahan (terlampir).

Dari tindak lanjut di atas, apakah seharusnya email dr
willistowerswatson.com sudah dapat diterima baik?
Terimakasih.

Regards,
Budi


-Original Message-
From: Mdaemon-L@dutaint.com [mailto:Mdaemon-L@dutaint.com] 
Sent: 23 December 2021 11:19
To: Mdaemon-L@dutaint.com
Subject: [Mdaemon-L] Gagal terima email dari domain willistowerswatson.com

On 12/23/21 10:27 AM, budi...@geodipa.co.id wrote:
> Mohon informasinya, untuk email dgn domain  willistowerswatson.com 
> tidak dapat diterima oleh email dengan domain geodipa.co.id.


> Thu 2021-12-23 00:07:44.934: [10694884] Performing SPF lookup 
> (willistowerswatson.com / 185.132.182.244) Thu 2021-12-23 
> 00:08:44.934: [10694884] *  DNS: 60 second wait for DNS response 
> exceeded (DNS Server: 68.1.18.25) Thu 2021-12-23 00:09:44.934: 
> [10694884] *  DNS: 60 second wait for DNS response exceeded (DNS 
> Server: 129.250.35.251) Thu 2021-12-23 00:10:44.934: [10694884] *  
> DNS: 60 second wait for DNS response exceeded (DNS Server: 
> 202.152.5.36) Thu 2021-12-23 00:11:44.934: [10694884] *  DNS: 60 
> second wait for DNS response exceeded (DNS Server: 202.152.0.2) Thu 
> 2021-12-23 00:12:44.934: [10694884] *  DNS: 60 second wait for DNS 
> response exceeded (DNS Server: 8.8.8.8)


Ini masalah DNS over TCP tidak berjalan dengan baik.
SPF record domain willistowerswatson.com memang panjang, sehingga tidak
mencukupi di resolve pakai DNS resolver standard UDP.

Periksa setting firewall (windows firewall dan external firewall) dan proxy
(antivirus), pastikan outbound tcp port 53 dari MDaemon ke Internet di
allow/open.

Test untuk memastikan sudah open sbb:

c:\ telnet portquiz.net 53


BTW. DNS IP  68.1.18.25 tidak mendukung DNS over TCP, dihapus saja dari
daftar.

$ host -t txt willistowerswatson.com 129.250.35.251 Using domain server:
Name: 129.250.35.251
Address: 129.250.35.251#53
Aliases:

willistowerswatson.com descriptive text
"Zm15FvuXSjBjf1GYEuo/bp0KH0MUZNFMi7+Db1zGabBFb0BwVB4mEcUFeWhMwydYmQjNsMKM7ee
CDZ1yqOHoVA=="
willistowerswatson.com descriptive text
"docusign=47a7b2c4-8332-4471-902a-7751a15c4d64"
willistowerswatson.com descriptive text
"apple-domain-verification=hrNPDuZXs7UOvaml"
willistowerswatson.com descriptive text
"1poEwRRTkNf7MdRYd7tVNZkk+hfOOGAVq7ZaYPIzlaXwycUbpD3S6XlXWt18sKNoSZTtsPy7UhU
lIFBwSV8rNQ=="
willistowerswatson.com descriptive text
"onetrust-domain-verification=e5e0e669515e483da48254d17d24344c"
willistowerswatson.com descriptive text
"pardot835203=ed27a9dcc3de58bbdc16c0274ea05ba177699284182dfdd0a2dd54ca58adec
14"
willistowerswatson.com descriptive text "rfl43qm47ovffj99jg5u7hn9vc"
willistowerswatson.com descriptive text
"google-site-verification=vhkdR90bxH4f4QQmTrcy7Wrb2CC6a1R2iO7jZ1NV51Q"
willistowerswatson.com descriptive text
"google-site-verification=vxRT-g2_-MKo9x8hm2JQWtSEQJ54olF1eE_4z4Drh7g"
willistowerswatson.com descriptive text "MS=ms27322890"
willistowerswatson.com descriptive text
"webexdomainverification.=452e31f1-b505-4fdd-944d-2feecc533b27"
willistowerswatson.com descriptive text
"2YGPWNyrDWDqz/WD2SkBOKDhcw/XaJIy7UzUQy41poM="
willistowerswatson.com descriptive text
"fxVd+7P8FiiFSFzkg3CmK8+Cac8tKOTSUPrxrNqO2xI="
willistowerswatson.com descriptive text
"_globalsign-domain-verification=u60LWxuznhU4rCQCzkruG9Xlp8UNrXOL5HLHGjc9ZY"
willistowerswatson.com descriptive text
"onetrust-domain-verification=2792c3463ffd4cf9940e9ee868eb5908"
willistowerswatson.com descriptive text
"A43FC5C95F26A7697D40DD7960139CCBCA7B174137650D5BD07F903233E98FFC"
willistowerswatson.com descriptive text
"a02e0935-98f9-457a-a94f-f656573535af"
willistowerswatson.com descriptive text
"_globalsign-domain-verification=C1LxQ8hwBjG8ZO2ULJJ7T713OT_9m7Megf_6D4DT1-"
willistowerswatson.com descriptive text "c7465ebivt7cl8gq0eh2n5ohhv"
willistowerswatson.com descriptive text
"_globalsign-domain-verification=-4vP5eysbT-3Pjcar2QjyLPSK3_bGIhyShtxuN8HUN"
willistowerswatson.com descriptive text
"adobe-idp-site-verification=4e007039-a465-4e6e-b4c2-b353c8d352ac"
willistowerswatson.com descriptive text "GlobalSign - 11962"
willistowerswatson.com descriptive text
"wiz-domain-verification=7eb292dcdce945c5a2e3766b76a23588adf56b0c71

[Mdaemon-L] Gagal terima email dari domain willistowerswatson.com

2021-12-22 Terurut Topik Syafril Hermansyah via Mdaemon-L 

On 12/23/21 10:27 AM, budi...@geodipa.co.id wrote:
Mohon informasinya, untuk email dgn domain  willistowerswatson.com tidak 
dapat diterima oleh email dengan domain geodipa.co.id.




Thu 2021-12-23 00:07:44.934: [10694884] Performing SPF lookup 
(willistowerswatson.com / 185.132.182.244)
Thu 2021-12-23 00:08:44.934: [10694884] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 68.1.18.25)
Thu 2021-12-23 00:09:44.934: [10694884] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 129.250.35.251)
Thu 2021-12-23 00:10:44.934: [10694884] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 202.152.5.36)
Thu 2021-12-23 00:11:44.934: [10694884] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 202.152.0.2)
Thu 2021-12-23 00:12:44.934: [10694884] *  DNS: 60 second wait for DNS response 
exceeded (DNS Server: 8.8.8.8)



Ini masalah DNS over TCP tidak berjalan dengan baik.
SPF record domain willistowerswatson.com memang panjang, sehingga tidak 
mencukupi di resolve pakai DNS resolver standard UDP.


Periksa setting firewall (windows firewall dan external firewall) dan 
proxy (antivirus), pastikan outbound tcp port 53 dari MDaemon ke 
Internet di allow/open.


Test untuk memastikan sudah open sbb:

c:\ telnet portquiz.net 53


BTW. DNS IP  68.1.18.25 tidak mendukung DNS over TCP, dihapus saja dari 
daftar.


$ host -t txt willistowerswatson.com 129.250.35.251
Using domain server:
Name: 129.250.35.251
Address: 129.250.35.251#53
Aliases:

willistowerswatson.com descriptive text 
"Zm15FvuXSjBjf1GYEuo/bp0KH0MUZNFMi7+Db1zGabBFb0BwVB4mEcUFeWhMwydYmQjNsMKM7eeCDZ1yqOHoVA=="
willistowerswatson.com descriptive text 
"docusign=47a7b2c4-8332-4471-902a-7751a15c4d64"
willistowerswatson.com descriptive text 
"apple-domain-verification=hrNPDuZXs7UOvaml"
willistowerswatson.com descriptive text 
"1poEwRRTkNf7MdRYd7tVNZkk+hfOOGAVq7ZaYPIzlaXwycUbpD3S6XlXWt18sKNoSZTtsPy7UhUlIFBwSV8rNQ=="
willistowerswatson.com descriptive text 
"onetrust-domain-verification=e5e0e669515e483da48254d17d24344c"
willistowerswatson.com descriptive text 
"pardot835203=ed27a9dcc3de58bbdc16c0274ea05ba177699284182dfdd0a2dd54ca58adec14"

willistowerswatson.com descriptive text "rfl43qm47ovffj99jg5u7hn9vc"
willistowerswatson.com descriptive text 
"google-site-verification=vhkdR90bxH4f4QQmTrcy7Wrb2CC6a1R2iO7jZ1NV51Q"
willistowerswatson.com descriptive text 
"google-site-verification=vxRT-g2_-MKo9x8hm2JQWtSEQJ54olF1eE_4z4Drh7g"

willistowerswatson.com descriptive text "MS=ms27322890"
willistowerswatson.com descriptive text 
"webexdomainverification.=452e31f1-b505-4fdd-944d-2feecc533b27"
willistowerswatson.com descriptive text 
"2YGPWNyrDWDqz/WD2SkBOKDhcw/XaJIy7UzUQy41poM="
willistowerswatson.com descriptive text 
"fxVd+7P8FiiFSFzkg3CmK8+Cac8tKOTSUPrxrNqO2xI="
willistowerswatson.com descriptive text 
"_globalsign-domain-verification=u60LWxuznhU4rCQCzkruG9Xlp8UNrXOL5HLHGjc9ZY"
willistowerswatson.com descriptive text 
"onetrust-domain-verification=2792c3463ffd4cf9940e9ee868eb5908"
willistowerswatson.com descriptive text 
"A43FC5C95F26A7697D40DD7960139CCBCA7B174137650D5BD07F903233E98FFC"
willistowerswatson.com descriptive text 
"a02e0935-98f9-457a-a94f-f656573535af"
willistowerswatson.com descriptive text 
"_globalsign-domain-verification=C1LxQ8hwBjG8ZO2ULJJ7T713OT_9m7Megf_6D4DT1-"

willistowerswatson.com descriptive text "c7465ebivt7cl8gq0eh2n5ohhv"
willistowerswatson.com descriptive text 
"_globalsign-domain-verification=-4vP5eysbT-3Pjcar2QjyLPSK3_bGIhyShtxuN8HUN"
willistowerswatson.com descriptive text 
"adobe-idp-site-verification=4e007039-a465-4e6e-b4c2-b353c8d352ac"

willistowerswatson.com descriptive text "GlobalSign - 11962"
willistowerswatson.com descriptive text 
"wiz-domain-verification=7eb292dcdce945c5a2e3766b76a23588adf56b0c719cd95a84d05cf2f2da446a"
willistowerswatson.com descriptive text "v=spf1 
include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all"
willistowerswatson.com descriptive text 
"globalsign-domain-verification=90dad3b27bcdc8e2677e16f29675df19"


$ host -t txt willistowerswatson.com 68.1.18.25
;; Connection to 68.1.18.25#53(68.1.18.25) for willistowerswatson.com 
failed: timed out.

;; connection timed out; no servers could be reached

;; Connection to 68.1.18.25#53(68.1.18.25) for willistowerswatson.com 
failed: timed out.

--
syafril

Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 21.5.1 64 bit
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

[Mdaemon-L] Gagal terima email dari domain willistowerswatson.com

2021-12-22 Terurut Topik budi_it 
Dear tim support,

 

Mohon informasinya, untuk email dgn domain  willistowerswatson.com tidak
dapat diterima oleh email dengan domain geodipa.co.id.

Berikut disampaikan log-nya :

 

Thu 2021-12-23 00:07:43.116: [10694884] Session 10694884; child 0001

Thu 2021-12-23 00:07:43.117: [10694884] Accepting SMTP connection from
185.132.182.244:60120 to 182.23.2.148:25

Thu 2021-12-23 00:07:43.117: [10694884] Location Screen says connection is
from United Kingdom, Europe

Thu 2021-12-23 00:07:43.117: [10694884] --> 220 mail.geodipa.co.id ESMTP
MDaemon 21.5.1; Thu, 23 Dec 2021 00:07:43 +0700

Thu 2021-12-23 00:07:43.304: [10694884] <-- EHLO mx07-00260c03.pphosted.com

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-mail.geodipa.co.id Hello
mx07-00260c03.pphosted.com [185.132.182.244], pleased to meet you

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-ETRN

Thu 2021-12-23 00:07:43.304: [10694884] Location Screening hiding AUTH from
country United Kingdom, Europe

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-8BITMIME

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-ENHANCEDSTATUSCODES

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-PIPELINING

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-CHUNKING

Thu 2021-12-23 00:07:43.304: [10694884] --> 250-STARTTLS

Thu 2021-12-23 00:07:43.304: [10694884] --> 250 SIZE 31457280

Thu 2021-12-23 00:07:43.491: [10694884] <-- STARTTLS

Thu 2021-12-23 00:07:43.491: [10694884] --> 220 2.7.0 Ready to start TLS

Thu 2021-12-23 00:07:44.071: [10694884] SSL negotiation successful (TLS 1.2,
521 bit key exchange, 256 bit AES encryption)

Thu 2021-12-23 00:07:44.257: [10694884] <-- EHLO mx07-00260c03.pphosted.com

Thu 2021-12-23 00:07:44.257: [10694884] --> 250-mail.geodipa.co.id Hello
mx07-00260c03.pphosted.com [185.132.182.244], pleased to meet you

Thu 2021-12-23 00:07:44.257: [10694884] --> 250-ETRN

Thu 2021-12-23 00:07:44.257: [10694884] Location Screening hiding AUTH from
country United Kingdom, Europe

Thu 2021-12-23 00:07:44.257: [10694884] --> 250-8BITMIME

Thu 2021-12-23 00:07:44.257: [10694884] --> 250-ENHANCEDSTATUSCODES

Thu 2021-12-23 00:07:44.257: [10694884] --> 250-PIPELINING

Thu 2021-12-23 00:07:44.257: [10694884] --> 250-CHUNKING

Thu 2021-12-23 00:07:44.257: [10694884] --> 250 SIZE 31457280

Thu 2021-12-23 00:07:44.443: [10694884] <-- MAIL
From: SIZE=76536

Thu 2021-12-23 00:07:44.448: [10694884] Performing PTR lookup
(244.182.132.185.IN-ADDR.ARPA)

Thu 2021-12-23 00:07:44.451: [10694884] *  D=244.182.132.185.IN-ADDR.ARPA
TTL=(1) PTR=[mx07-00260c03.pphosted.com]

Thu 2021-12-23 00:07:44.471: [10694884] *  D=mx07-00260c03.pphosted.com
TTL=(5) A=[185.132.182.244]

Thu 2021-12-23 00:07:44.471: [10694884]  End PTR results

Thu 2021-12-23 00:07:44.473: [10694884] Performing IP lookup
(mx07-00260c03.pphosted.com)

Thu 2021-12-23 00:07:44.477: [10694884] *  D=mx07-00260c03.pphosted.com
TTL=(5) A=[185.132.182.244]

Thu 2021-12-23 00:07:44.477: [10694884]  End IP lookup results

Thu 2021-12-23 00:07:44.479: [10694884] Performing IP lookup
(willistowerswatson.com)

Thu 2021-12-23 00:07:44.495: [10694884] *  D=willistowerswatson.com TTL=(5)
A=[52.251.42.90]

Thu 2021-12-23 00:07:44.514: [10694884] *  P=010 S=000
D=willistowerswatson.com TTL=(5) MX=[mxb-00260c02.gslb.pphosted.com]

Thu 2021-12-23 00:07:44.514: [10694884] *  P=010 S=001
D=willistowerswatson.com TTL=(5) MX=[mxa-00260c02.gslb.pphosted.com]

Thu 2021-12-23 00:07:44.709: [10694884] *  D=mxb-00260c02.gslb.pphosted.com
TTL=(0) A=[185.132.180.172]

Thu 2021-12-23 00:07:44.904: [10694884] *  D=mxa-00260c02.gslb.pphosted.com
TTL=(0) A=[185.183.28.129]

Thu 2021-12-23 00:07:44.904: [10694884]  End IP lookup results

Thu 2021-12-23 00:07:44.905: [10694884] Performing SPF lookup
(mx07-00260c03.pphosted.com / 185.132.182.244)

Thu 2021-12-23 00:07:44.934: [10694884] *  Result: none; no SPF record in
DNS

Thu 2021-12-23 00:07:44.934: [10694884]  End SPF results

Thu 2021-12-23 00:07:44.934: [10694884] Performing SPF lookup
(willistowerswatson.com / 185.132.182.244)

Thu 2021-12-23 00:08:44.934: [10694884] *  DNS: 60 second wait for DNS
response exceeded (DNS Server: 68.1.18.25)

Thu 2021-12-23 00:09:44.934: [10694884] *  DNS: 60 second wait for DNS
response exceeded (DNS Server: 129.250.35.251)

Thu 2021-12-23 00:10:44.934: [10694884] *  DNS: 60 second wait for DNS
response exceeded (DNS Server: 202.152.5.36)

Thu 2021-12-23 00:11:44.934: [10694884] *  DNS: 60 second wait for DNS
response exceeded (DNS Server: 202.152.0.2)

Thu 2021-12-23 00:12:44.934: [10694884] *  DNS: 60 second wait for DNS
response exceeded (DNS Server: 8.8.8.8)

Thu 2021-12-23 00:12:44.934: [10694884] *  Result: none; no SPF record in
DNS

Thu 2021-12-23 00:12:44.934: [10694884]  End SPF results

Thu 2021-12-23 00:12:44.934: [10694884] --> 250 2.1.0 Sender OK

Thu 2021-12-23 00:12:45.121: [10694884] *  Socket error 10054 - Connection
was reset by the other side!

Thu 2021-12-23 00:12:45.122: [10694884] SMTP session terminated

[MDaemon-L] gagal terima email dari domain yang sama

2016-10-06 Terurut Topik Syafril Hermansyah 
On 06/10/16 14:48, Thariq Basyir wrote:
> server email kami menolak email dari domain yang sama. karena salah
> satu email terlihat dari log dianggap spam scorenya (4), namun salah
> satunya berhasil spam scorenya (1)
> 
> apakah ini karena salah satu email tersebut memakai office365. dan
> sedang bermasalah?

Bukan, masalahnya ada 2

> Thu 2016-10-06 11:43:51.163: [749060] --> 550 5.7.1 Sorry, message
> looks like spam or phish to me (OP)

Yang ini karena belum mengubah setting outbreak protection mengikuti
tips berikut

http://www.mail-archive.com/mdaemon-l@dutaint.com/msg37676.html

http://www.mail-archive.com/mdaemon-l@dutaint.com/msg37916.html

yang kedua

> Thu 2016-10-06 11:43:50.126: [749060] Accepting SMTP connection from
> 10.0.0.5:39559 to 10.0.0.6:25

Setting firewallnya tidak benar, masih pakai NAT (Source Network Address
Translation, SNAT).
Harusnya seting firewall pakai Port Address Translation (PAT alias Port
Forwarding alias Port Mapping alias Destination NAT, DNAT).

http://blog.boson.com/bid/53313/NAT-and-PAT-What-s-the-Difference

NAT itu untuk proxy (share public IP for LAN user) sementara PAT untuk
peletakkan internet server dibelakang firewall.

-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, MDaemon 16.5.1-64 Beta A, SP 5.0.1-64
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

Orang menilai org lain berdasarkan apa yg dikatakannya dan apa yg
diperbuatnya, org menilai diri sendiriberdasarkan apa yg dipikirkannya
dan apa yg hendak dicobanya
-- Comtesse Diane, 1829-1899


-- 
--MDaemon-L--
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: https://wiki.openstack.org/wiki/MailingListEtiquette
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 16.5.0, SP 5.0.1, OC 4.0, SG 4.0.1

[MDaemon-L] gagal terima email dari domain yang sama

2016-10-06 Terurut Topik Thariq Basyir 
Dear pak syafril,

server email kami menolak email dari domain yang sama. karena salah
satu email terlihat dari log dianggap spam scorenya (4), namun salah
satunya berhasil spam scorenya (1)

apakah ini karena salah satu email tersebut memakai office365. dan
sedang bermasalah?

berikut log yang gagal:

Thu 2016-10-06 11:43:50.126: [749060] Session 749060; child 0004
Thu 2016-10-06 11:43:50.126: [749060] Accepting SMTP connection from
10.0.0.5:39559 to 10.0.0.6:25
Thu 2016-10-06 11:43:50.128: [749060] --> 220 mail.kompas.tv ESMTP
MDaemon 15.5.0; Thu, 06 Oct 2016 11:43:50 +0700
Thu 2016-10-06 11:43:50.153: [749060] <-- EHLO
APC01-SG2-obe.outbound.protection.outlook.com
Thu 2016-10-06 11:43:50.153: [749060] --> 250-mail.kompas.tv Hello
APC01-SG2-obe.outbound.protection.outlook.com, pleased to meet you
Thu 2016-10-06 11:43:50.153: [749060] --> 250-ETRN
Thu 2016-10-06 11:43:50.153: [749060] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Thu 2016-10-06 11:43:50.153: [749060] --> 250-8BITMIME
Thu 2016-10-06 11:43:50.153: [749060] --> 250-ENHANCEDSTATUSCODES
Thu 2016-10-06 11:43:50.154: [749060] --> 250 SIZE 2048
Thu 2016-10-06 11:43:50.209: [749060] <-- MAIL FROM: SIZE=67005
Thu 2016-10-06 11:43:50.211: [749060] --> 250 2.1.0 Sender OK
Thu 2016-10-06 11:43:50.267: [749060] <-- RCPT
TO:
Thu 2016-10-06 11:43:50.268: [749060] --> 250 2.1.5 Recipient OK
Thu 2016-10-06 11:43:50.323: [749060] <-- RCPT TO:
Thu 2016-10-06 11:43:50.324: [749060] --> 250 2.1.5 Recipient OK
Thu 2016-10-06 11:43:50.384: [749060] <-- DATA
Thu 2016-10-06 11:43:50.384: [749060] Creating temp file (SMTP):
c:\mdaemon\queues\temp\md5174869.tmp
Thu 2016-10-06 11:43:50.384: [749060] --> 354 Enter mail, end with .
Thu 2016-10-06 11:43:50.978: [749060] Message size: 60274 bytes
Thu 2016-10-06 11:43:50.981: [749060] Passing message through
AntiVirus (Size: 60274)...
Thu 2016-10-06 11:43:50.996: [749060] *  Message is clean (no viruses found)
Thu 2016-10-06 11:43:50.996: [749060]  End AntiVirus results
Thu 2016-10-06 11:43:51.162: [749060] Passing message through Outbreak
Protection...
Thu 2016-10-06 11:43:51.162: [749060] *  Message-ID:

Thu 2016-10-06 11:43:51.162: [749060] *  Reference-ID:
str=0001.0A150203.57F5D339.010C,ss=4,sh,re=0.000,recu=0.000,reip=0.000,cl=4,cld=1,fgs=12
Thu 2016-10-06 11:43:51.162: [749060] *  Virus result: 0 - Clean
Thu 2016-10-06 11:43:51.162: [749060] *  Spam result: 4 - Spam (confirmed)
Thu 2016-10-06 11:43:51.162: [749060] *  IWF result: 0 - Clean
Thu 2016-10-06 11:43:51.162: [749060]  End Outbreak Protection results
Thu 2016-10-06 11:43:51.163: [749060] --> 550 5.7.1 Sorry, message
looks like spam or phish to me (OP)
Thu 2016-10-06 11:43:51.163: [749060] SMTP session terminated (Bytes
in/out: 60456/437)

log yang berhasil:

Thu 2016-10-06 14:20:40.568: [762394] Session 762394; child 0003
Thu 2016-10-06 14:20:40.568: [762394] Accepting SMTP connection from
10.0.0.5:37229 to 10.0.0.6:25
Thu 2016-10-06 14:20:40.570: [762394] --> 220 mail.kompas.tv ESMTP
MDaemon 15.5.0; Thu, 06 Oct 2016 14:20:40 +0700
Thu 2016-10-06 14:20:40.622: [762394] <-- EHLO mail1.xl.co.id
Thu 2016-10-06 14:20:40.622: [762394] --> 250-mail.kompas.tv Hello
mail1.xl.co.id, pleased to meet you
Thu 2016-10-06 14:20:40.622: [762394] --> 250-ETRN
Thu 2016-10-06 14:20:40.622: [762394] --> 250-AUTH LOGIN CRAM-MD5 PLAIN
Thu 2016-10-06 14:20:40.622: [762394] --> 250-8BITMIME
Thu 2016-10-06 14:20:40.622: [762394] --> 250-ENHANCEDSTATUSCODES
Thu 2016-10-06 14:20:40.622: [762394] --> 250 SIZE 2048
Thu 2016-10-06 14:20:40.862: [762394] <-- MAIL FROM: SIZE=5342
Thu 2016-10-06 14:20:40.863: [762394] --> 250 2.1.0 Sender OK
Thu 2016-10-06 14:20:40.918: [762394] <-- RCPT TO:
Thu 2016-10-06 14:20:40.965: [762394] --> 250 2.1.5 Recipient OK
Thu 2016-10-06 14:20:41.003: [762394] <-- DATA
Thu 2016-10-06 14:20:47.258: [762394] Creating temp file (SMTP):
c:\mdaemon\queues\temp\md5177188.tmp
Thu 2016-10-06 14:20:47.258: [762394] --> 354 Enter mail, end with .
Thu 2016-10-06 14:20:47.425: [762394] Message size: 5098 bytes
Thu 2016-10-06 14:20:47.488: [762394] Passing message through
AntiVirus (Size: 5098)...
Thu 2016-10-06 14:20:47.517: [762394] *  Message is clean (no viruses found)
Thu 2016-10-06 14:20:47.517: [762394]  End AntiVirus results
Thu 2016-10-06 14:20:47.974: [762394] Passing message through Outbreak
Protection...
Thu 2016-10-06 14:20:47.974: [762394] *  Message-ID:

Thu 2016-10-06 14:20:47.974: [762394] *  Reference-ID:
str=0001.0A15020A.57F5FB5D.0110,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0
Thu 2016-10-06 14:20:47.974: [762394] *  Virus result: 0 - Clean
Thu 2016-10-06 14:20:47.974: [762394] *  Spam result: 1 - Clean
Thu 2016-10-06 14:20:47.974: [762394] *  IWF result: 0 - Clean
Thu

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-10 Terurut Topik alien 
2014-09-10 11:38 GMT+07:00 Syafril Hermansyah syaf...@dutaint.co.id:

 On 2014-09-10 11:30, alien wrote:
   Ya bisa kalau routernya mampu melakukan reroute traffic dan
 pengelolanya
   mampu mengoperasikan.
   Caranya hampir mirip dengan reroute outbound traffic port 25 ke
 smtp
   tertentu (biasanya local smtp server mereka).
  ^^
  ... untuk koneksi dari
  dynamic IP user.
 
 
  Saya pakai IP Statis Pak, kebetulan pakai koneksi internet dedicated.

 Untuk DNS query blocking ini nampaknya berlaku untuk semua pelanggan
 dynamic maupun static IP yang digunakan untuk browsing user.
 Bisa dikonsultasikan ke ISP, mnngkin bisa dikecualikan kalau yang query
 dari internet mail server.

 Saya sudah kroscek ke Telkom, menurut mereka tidak ada kebijakan untuk
melakukan reroute atau lainnya.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-10 Terurut Topik alien 
2014-09-10 11:40 GMT+07:00 Syafril Hermansyah syaf...@dutaint.co.id:

 On 2014-09-10 11:29, alien wrote:
  Sekedar informasi, saya pakai 1 MX dengan multiple A record dengan
  menggunakan IP publik statis dari Telkom dan CBN.

 Kenapa perlu banyak MX host begitu, memangnya server Anda loyo karena
 diletakkan di DMZ?

 Sebenarnya saya pakaikan MX dengan 2 ISP itu bukan karena loyo, tapi
supaya ketika salah satu ISP down, masih ada ISP lainnya sebagai backup
(round robin) dan supaya seluruh user saya tidak perlu melakukan perubahan
utk incoming atau outgoing, jadi tetap bisa pakai mail.indokemika.co.id
seperti MX utama.  Dan untuk backup skenarionya masih seputar koneksi saja,
belum sampai punya server fisik yang ke-2 sebagai backup.

yang terpikirkan saat ini adalah seperti itu, apakah bisa minta pencerahaan
apabila ada skenario lebih baik lagi?

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-10 Terurut Topik Syafril Hermansyah 
On 2014-09-10 18:01, alien wrote:
 Saya sudah kroscek ke Telkom, menurut mereka tidak ada kebijakan untuk
 melakukan reroute atau lainnya. 

Baguslah, karena DNS query blocking bikin susah internet mail server
(termasuk MDaemon) :-)

-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-10 Terurut Topik Syafril Hermansyah 
On 2014-09-10 18:05, alien wrote:
 Sebenarnya saya pakaikan MX dengan 2 ISP itu bukan karena loyo, tapi
 supaya ketika salah satu ISP down, masih ada ISP lainnya sebagai backup
 (round robin) dan supaya seluruh user saya tidak perlu melakukan
 perubahan utk incoming atau outgoing, jadi tetap bisa pakai
 mail.indokemika.co.id http://mail.indokemika.co.id seperti MX utama.
  Dan untuk backup skenarionya masih seputar koneksi saja, belum sampai
 punya server fisik yang ke-2 sebagai backup.
 
 yang terpikirkan saat ini adalah seperti itu, apakah bisa minta
 pencerahaan apabila ada skenario lebih baik lagi?

Bukankah sudah pernah didiskusikan?

http://www.mail-archive.com/mdaemon-l%40dutaint.com/msg33173.html

Server kami tidak punya MX backup secara fisik, tetapi kami punya ribuan
virtual MX backup berupa sender host.

Aplikasi internet mail server itu tidak kritis sehingga butuh realtime
backup, yang kritis itu DNS (authoritative DNS).
Kalau domain Anda tidak dikenal karena authoritative DNS domain Anda
tidak bisa dihubungi (any reason), maka sender host akan segera
menggagalkan kiriman mail dan generate DSN ke original sender.

-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik alien 
Dear Pak Syafril dan rekan2 milis,

Mohon bantuan dan pencerahannya, tiap kali email dari Yahoo selalu gagal
diterima.  Dibawah ini adalah log dari smtp(in) :

Tue 2014-09-09 16:27:30: [832021] Session 832021; child 0030
Tue 2014-09-09 16:27:30: [832021] Accepting SMTP connection from [
98.138.91.118:45723] to [118.97.92.178:25]
Tue 2014-09-09 16:27:30: [832021] -- 220 mail.indokemika.co.id ESMTP
MDaemon 14.0.3; Tue, 09 Sep 2014 16:27:30 +0700
Tue 2014-09-09 16:27:31: [832021] -- EHLO
nm25-vm6.bullet.mail.ne1.yahoo.com
Tue 2014-09-09 16:27:31: [832021] -- 250-mail.indokemika.co.id Hello
nm25-vm6.bullet.mail.ne1.yahoo.com, pleased to meet you
Tue 2014-09-09 16:27:31: [832021] -- 250-ETRN
Tue 2014-09-09 16:27:31: [832021] -- 250-AUTH LOGIN CRAM-MD5 PLAIN
Tue 2014-09-09 16:27:31: [832021] -- 250-8BITMIME
Tue 2014-09-09 16:27:31: [832021] -- 250 SIZE 1536
Tue 2014-09-09 16:27:31: [832021] -- MAIL FROM:rusdi...@yahoo.com
Tue 2014-09-09 16:27:31: [832021] Performing PTR lookup
(118.91.138.98.IN-ADDR.ARPA)
Tue 2014-09-09 16:27:31: [832021] *  D=118.91.138.98.IN-ADDR.ARPA TTL=(5)
PTR=[nm25-vm6.bullet.mail.ne1.yahoo.com]
Tue 2014-09-09 16:27:31: [832021] *  Gathering A records...
Tue 2014-09-09 16:27:31: [832021] *  D=nm25-vm6.bullet.mail.ne1.yahoo.com
TTL=(29) A=[98.138.91.118]
Tue 2014-09-09 16:27:31: [832021]  End PTR results
Tue 2014-09-09 16:27:31: [832021] Performing IP lookup (
nm25-vm6.bullet.mail.ne1.yahoo.com)
Tue 2014-09-09 16:27:31: [832021] *  D=nm25-vm6.bullet.mail.ne1.yahoo.com
TTL=(29) A=[98.138.91.118]
Tue 2014-09-09 16:27:31: [832021]  End IP lookup results
Tue 2014-09-09 16:27:31: [832021] Performing IP lookup (yahoo.com)
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.138.253.109]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.139.183.24]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[206.190.36.45]
Tue 2014-09-09 16:27:31: [832021] *  P=001 S=000 D=yahoo.com TTL=(7) MX=[
mta6.am0.yahoodns.net]
Tue 2014-09-09 16:27:31: [832021] *  P=001 S=001 D=yahoo.com TTL=(7) MX=[
mta7.am0.yahoodns.net]
Tue 2014-09-09 16:27:31: [832021] *  P=001 S=002 D=yahoo.com TTL=(7) MX=[
mta5.am0.yahoodns.net]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.138.253.109]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.138.253.109]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[206.190.36.45]
Tue 2014-09-09 16:27:31: [832021]  End IP lookup results
Tue 2014-09-09 16:27:31: [832021] -- 250 rusdi...@yahoo.com, Sender ok
Tue 2014-09-09 16:27:32: [832021] -- RCPT TO:ru...@indokemika.co.id
Tue 2014-09-09 16:27:32: [832021] Performing DNS-BL lookup (98.138.91.118 -
connecting IP)
Tue 2014-09-09 16:27:32: [832021] *  zen.spamhaus.org - passed
Tue 2014-09-09 16:27:32: [832021] *  bl.spamcop.net - passed
Tue 2014-09-09 16:27:33: [832021] *  cbl.abuseat.org - passed
Tue 2014-09-09 16:27:33: [832021]  End DNS-BL results
Tue 2014-09-09 16:27:33: [832021] -- 250 ru...@indokemika.co.id,
Recipient ok
Tue 2014-09-09 16:27:33: [832021] -- DATA
Tue 2014-09-09 16:27:33: [832021] Creating temp file (SMTP):
d:\mdaemon\queues\temp\md5024659.tmp
Tue 2014-09-09 16:27:33: [832021] -- 354 Enter mail, end with CRLF.CRLF
Tue 2014-09-09 16:27:33: [832021] Message size: 2572 bytes
Tue 2014-09-09 16:27:33: [832021] Performing DKIM lookup
Tue 2014-09-09 16:27:33: [832021] *  File:
d:\mdaemon\queues\temp\md5024659.tmp
Tue 2014-09-09 16:27:33: [832021] *  Message-ID:
1410254849.58507.yahoomail...@web121005.mail.ne1.yahoo.com
Tue 2014-09-09 16:27:33: [832021] * Signature (1):
;v=1;a=rsa-sha256;c=relaxed/relaxed;d=yahoo.com;s=s1024;t=1410254849;b
h=not logged;
Tue 2014-09-09 16:27:33: [832021] *Verification result: [0] good
Tue 2014-09-09 16:27:33: [832021] *  Result: pass
Tue 2014-09-09 16:27:33: [832021]  End DKIM results
Tue 2014-09-09 16:27:33: [832021] Performing VBR certification (Domain:
yahoo.com, Auth: DKIM)
Tue 2014-09-09 16:27:33: [832021] *  File:
d:\mdaemon\queues\temp\md5024659.tmp
Tue 2014-09-09 16:27:33: [832021] *  Message-ID:
1410254849.58507.yahoomail...@web121005.mail.ne1.yahoo.com
Tue 2014-09-09 16:27:33: [832021] *  Certifier (trusted):
vbr.emailcertification.org ...
Tue 2014-09-09 16:27:33: [832021] *Querying: yahoo.com._
vouch.vbr.emailcertification.org ...
Tue 2014-09-09 16:31:35: [832021] *  DNS: 240 second wait for DNS response
exceeded (DNS Server: 202.134.0.155)
Tue 2014-09-09 16:35:36: [832021] *  DNS: 240 second wait for DNS response
exceeded (DNS Server: 203.130.193.74)
Tue 2014-09-09 16:35:36: [832021] *Certifier does not recognize that
domain
Tue 2014-09-09 16:35:36: [832021] *  Certification result: message not
certified
Tue 2014-09-09 16:35:36: [832021]  End VBR results
Tue 2014-09-09 16:35:36: [832021] Passing message through AntiVirus (Size:
2572)...
Tue 2014-09-09 16:35:36: [832021] *  Message is clean (no viruses found)
Tue 2014-09-09 16:35:36: [832021]  End AntiVirus

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik tri . wahyudijanto 
Turut menambahkan... Kami-pun memiliki hal yang sama saat ini.. Ada apakah 
gerangan?

Sent from BlackBerry® on 3

-Original Message-
From: alien rusdi...@gmail.com
Sender: MDaemon-L@dutaint.com
Date: Tue, 9 Sep 2014 18:32:20 
To: Milis Komunitas MDaemon IndonesiaMDaemon-L@dutaint.com
Reply-To: Milis Komunitas MDaemon Indonesia mdaemon-l@dutaint.com
Subject: [MDaemon-L] Gagal terima email dari Yahoo

Dear Pak Syafril dan rekan2 milis,

Mohon bantuan dan pencerahannya, tiap kali email dari Yahoo selalu gagal
diterima.  Dibawah ini adalah log dari smtp(in) :

Tue 2014-09-09 16:27:30: [832021] Session 832021; child 0030
Tue 2014-09-09 16:27:30: [832021] Accepting SMTP connection from [
98.138.91.118:45723] to [118.97.92.178:25]
Tue 2014-09-09 16:27:30: [832021] -- 220 mail.indokemika.co.id ESMTP
MDaemon 14.0.3; Tue, 09 Sep 2014 16:27:30 +0700
Tue 2014-09-09 16:27:31: [832021] -- EHLO
nm25-vm6.bullet.mail.ne1.yahoo.com
Tue 2014-09-09 16:27:31: [832021] -- 250-mail.indokemika.co.id Hello
nm25-vm6.bullet.mail.ne1.yahoo.com, pleased to meet you
Tue 2014-09-09 16:27:31: [832021] -- 250-ETRN
Tue 2014-09-09 16:27:31: [832021] -- 250-AUTH LOGIN CRAM-MD5 PLAIN
Tue 2014-09-09 16:27:31: [832021] -- 250-8BITMIME
Tue 2014-09-09 16:27:31: [832021] -- 250 SIZE 1536
Tue 2014-09-09 16:27:31: [832021] -- MAIL FROM:rusdi...@yahoo.com
Tue 2014-09-09 16:27:31: [832021] Performing PTR lookup
(118.91.138.98.IN-ADDR.ARPA)
Tue 2014-09-09 16:27:31: [832021] *  D=118.91.138.98.IN-ADDR.ARPA TTL=(5)
PTR=[nm25-vm6.bullet.mail.ne1.yahoo.com]
Tue 2014-09-09 16:27:31: [832021] *  Gathering A records...
Tue 2014-09-09 16:27:31: [832021] *  D=nm25-vm6.bullet.mail.ne1.yahoo.com
TTL=(29) A=[98.138.91.118]
Tue 2014-09-09 16:27:31: [832021]  End PTR results
Tue 2014-09-09 16:27:31: [832021] Performing IP lookup (
nm25-vm6.bullet.mail.ne1.yahoo.com)
Tue 2014-09-09 16:27:31: [832021] *  D=nm25-vm6.bullet.mail.ne1.yahoo.com
TTL=(29) A=[98.138.91.118]
Tue 2014-09-09 16:27:31: [832021]  End IP lookup results
Tue 2014-09-09 16:27:31: [832021] Performing IP lookup (yahoo.com)
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.138.253.109]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.139.183.24]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[206.190.36.45]
Tue 2014-09-09 16:27:31: [832021] *  P=001 S=000 D=yahoo.com TTL=(7) MX=[
mta6.am0.yahoodns.net]
Tue 2014-09-09 16:27:31: [832021] *  P=001 S=001 D=yahoo.com TTL=(7) MX=[
mta7.am0.yahoodns.net]
Tue 2014-09-09 16:27:31: [832021] *  P=001 S=002 D=yahoo.com TTL=(7) MX=[
mta5.am0.yahoodns.net]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.138.253.109]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[98.138.253.109]
Tue 2014-09-09 16:27:31: [832021] *  D=yahoo.com TTL=(27) A=[206.190.36.45]
Tue 2014-09-09 16:27:31: [832021]  End IP lookup results
Tue 2014-09-09 16:27:31: [832021] -- 250 rusdi...@yahoo.com, Sender ok
Tue 2014-09-09 16:27:32: [832021] -- RCPT TO:ru...@indokemika.co.id
Tue 2014-09-09 16:27:32: [832021] Performing DNS-BL lookup (98.138.91.118 -
connecting IP)
Tue 2014-09-09 16:27:32: [832021] *  zen.spamhaus.org - passed
Tue 2014-09-09 16:27:32: [832021] *  bl.spamcop.net - passed
Tue 2014-09-09 16:27:33: [832021] *  cbl.abuseat.org - passed
Tue 2014-09-09 16:27:33: [832021]  End DNS-BL results
Tue 2014-09-09 16:27:33: [832021] -- 250 ru...@indokemika.co.id,
Recipient ok
Tue 2014-09-09 16:27:33: [832021] -- DATA
Tue 2014-09-09 16:27:33: [832021] Creating temp file (SMTP):
d:\mdaemon\queues\temp\md5024659.tmp
Tue 2014-09-09 16:27:33: [832021] -- 354 Enter mail, end with CRLF.CRLF
Tue 2014-09-09 16:27:33: [832021] Message size: 2572 bytes
Tue 2014-09-09 16:27:33: [832021] Performing DKIM lookup
Tue 2014-09-09 16:27:33: [832021] *  File:
d:\mdaemon\queues\temp\md5024659.tmp
Tue 2014-09-09 16:27:33: [832021] *  Message-ID:
1410254849.58507.yahoomail...@web121005.mail.ne1.yahoo.com
Tue 2014-09-09 16:27:33: [832021] * Signature (1):
;v=1;a=rsa-sha256;c=relaxed/relaxed;d=yahoo.com;s=s1024;t=1410254849;b
h=not logged;
Tue 2014-09-09 16:27:33: [832021] *Verification result: [0] good
Tue 2014-09-09 16:27:33: [832021] *  Result: pass
Tue 2014-09-09 16:27:33: [832021]  End DKIM results
Tue 2014-09-09 16:27:33: [832021] Performing VBR certification (Domain:
yahoo.com, Auth: DKIM)
Tue 2014-09-09 16:27:33: [832021] *  File:
d:\mdaemon\queues\temp\md5024659.tmp
Tue 2014-09-09 16:27:33: [832021] *  Message-ID:
1410254849.58507.yahoomail...@web121005.mail.ne1.yahoo.com
Tue 2014-09-09 16:27:33: [832021] *  Certifier (trusted):
vbr.emailcertification.org ...
Tue 2014-09-09 16:27:33: [832021] *Querying: yahoo.com._
vouch.vbr.emailcertification.org ...
Tue 2014-09-09 16:31:35: [832021] *  DNS: 240 second wait for DNS response
exceeded (DNS Server: 202.134.0.155)
Tue 2014-09-09 16:35:36: [832021] *  DNS: 240 second wait for DNS response
exceeded (DNS Server: 203.130.193.74)
Tue 2014-09-09 16

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik alien 
On Tue, Sep 9, 2014 at 5:58 PM, tri.wahyudija...@gmail.com wrote:

 Turut menambahkan... Kami-pun memiliki hal yang sama saat ini.. Ada apakah
 gerangan?


Pak Tri, kejadiannya sejak kapan ya? kalau saya rasanya sejak kemarin atau
2 hari yang lalu

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik tri . wahyudijanto 
Pak/Bu Alien,

Benar.. Sejak kemarin atau dua hari kebelakang ini.. Apakah rekan-rekan lainnya 
disini-pun merasakan kegalauan yang sama dengan kami? Atau mungkin hanya kami 
saja yang kurang beruntung?

Sent from BlackBerry® on 3

-Original Message-
From: alien rusdi...@gmail.com
Sender: MDaemon-L@dutaint.com
Date: Tue, 9 Sep 2014 18:53:23 
To: Milis Komunitas MDaemon Indonesiamdaemon-l@dutaint.com
Reply-To: Milis Komunitas MDaemon Indonesia mdaemon-l@dutaint.com
Subject: [MDaemon-L] Gagal terima email dari Yahoo

On Tue, Sep 9, 2014 at 5:58 PM, tri.wahyudija...@gmail.com wrote:

 Turut menambahkan... Kami-pun memiliki hal yang sama saat ini.. Ada apakah
 gerangan?


Pak Tri, kejadiannya sejak kapan ya? kalau saya rasanya sejak kemarin atau
2 hari yang lalu

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-09 18:32, alien wrote:
 Di Log tersebut selalu gagal di DNS 202.134.0.155 dan 203.130.193.74,
 padahal di MDaemon saya pakai DNS google 8.8.8.8 dan 8.8.4.4, bahkan
 saya coba pakai DNS yang ada di Windows Server yang pakai DNS google
 tersebut juga selalu saja hasil log nya seperti itu.

Ada router/firewall yang membelokkan DNS query ke public DNS ke local
DNS ISP.
Coba kalau MDaemonnya bypass firewall, apakah masih terjadi seperti itu?


 Tue 2014-09-09 16:31:35: [832021] *  DNS: 240 second wait for DNS response 
 exceeded (DNS Server: 202.134.0.155)

Yang bikin gagal terima sebenarnya bukan masalah DNS resolver itu,
tetapi idle time out yang Anda set sudah kelewat gede.
Standar internet DNS query maksimum 60 seconds saja, lebih besar dari
itu lebih besar problem daripada manfaatnya :-)


-- 
syafril
---
Syafril Hermansyah
Running MDaemon 14.5 Beta C, SP 4.5.0 Beta B

Kehabisan tenaga mengancam kehidupan bangsa dan tiap warganya; ia adalah
kesakitan selagi mengantuk, kematian selagi tidur.
-- Kahlil Gibran

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik alien 
2014-09-09 21:47 GMT+07:00 Syafril Hermansyah syaf...@dutaint.co.id:

 On 2014-09-09 18:32, alien wrote:
  Di Log tersebut selalu gagal di DNS 202.134.0.155 dan 203.130.193.74,
  padahal di MDaemon saya pakai DNS google 8.8.8.8 dan 8.8.4.4, bahkan
  saya coba pakai DNS yang ada di Windows Server yang pakai DNS google
  tersebut juga selalu saja hasil log nya seperti itu.

 Ada router/firewall yang membelokkan DNS query ke public DNS ke local
 DNS ISP.
 Coba kalau MDaemonnya bypass firewall, apakah masih terjadi seperti itu?


Koneksi MDaemon tidak melewati firewall atau router melainkan IP publik
langsung dipasang pada NIC fisik server.
Kira2 apa yang menyebabkan hal ini ya Pak?



  Tue 2014-09-09 16:31:35: [832021] *  DNS: 240 second wait for DNS
 response exceeded (DNS Server: 202.134.0.155)

 Yang bikin gagal terima sebenarnya bukan masalah DNS resolver itu,
 tetapi idle time out yang Anda set sudah kelewat gede.
 Standar internet DNS query maksimum 60 seconds saja, lebih besar dari
 itu lebih besar problem daripada manfaatnya :-)

 Akan saya coba kroscek kembali utk idle time out tersebut.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-09 23:05, alien wrote:
 Ada router/firewall yang membelokkan DNS query ke public DNS ke local
 DNS ISP.
 Coba kalau MDaemonnya bypass firewall, apakah masih terjadi seperti itu?
 
 
 Koneksi MDaemon tidak melewati firewall atau router melainkan IP publik
 langsung dipasang pada NIC fisik server.
 Kira2 apa yang menyebabkan hal ini ya Pak?  

Router di ISP Anda yang membelokannya.
Coba tanyakan ke ISP.


-- 
syafril
---
Syafril Hermansyah
Running MDaemon 14.5 Beta C, SP 4.5.0 Beta B

Anda dapat mencapai apapun dalam hidup, asalkan Anda tidak keberatan
siapa yang mendapat nama.
-- Harry S. Truman

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik alien 


 Router di ISP Anda yang membelokannya.
 Coba tanyakan ke ISP.

 Saat ini saya sedang kroscek dengan ISP mengenai hal ini.  Sebagai
tambahan berikut error message dari Yahoo yang gagal kami terima :

Sorry, we were unable to deliver your message to the following address.

ru...@indokemika.co.id:
Remote host said:
550 We don't handle mail for yahoo.com
[RCPT_TO]

--- Below this line is a copy of the message.

Received: from [98.138.100.112] by nm25.bullet.mail.ne1.yahoo.com with
NNFMP; 09 Sep 2014 09:27:29 -
Received: from [98.138.89.163] by tm103.bullet.mail.ne1.yahoo.com with
NNFMP; 09 Sep 2014 09:27:29 -
Received: from [127.0.0.1] by omp1019.mail.ne1.yahoo.com with NNFMP; 09 Sep
2014 09:27:29 -
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 453780.50515...@omp1019.mail.ne1.yahoo.com
Received: (qmail 38312 invoked by uid 60001); 9 Sep 2014 09:27:29 -
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024;
t=1410254849; bh=0sGON+TXV5vl0BUPb0gJfHsUO2EM+ouDNApCBlRc8v4=;
h=Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
b=zEHjU6tLMbe0f94Y0RhhHKs7vuzsgGQE0WZjHlFKvoL4SuYrjrECMM17U9+YllfIUqD/rmkZIfOucGYYlH9TI8VamKfzI+QPyYDXpxJmpZrTa2ll9+k4z0wPQ+PVF3gEu/JA0sxdmUAThHeFWq6vow4ZWMwr9BQNQHiVmfm5CPM=
X-YMail-OSG: oqepv_cVM1mwAdM3CDrhJYlEJgPPuZf_JBX5VmTmgnCtavN
txdNYuekYykCjMi18E8rfVA3YBKePJvMMzNpFhB7vyfffnma9vIBgfe2MU6c
gD_y8iU.0dkeJRTz3lvlvYcPttRlfBYrUZSZcGiCvSdMjXMsP.vCMUGD7vUW
jJ0SrJ5SEPknYzxE7WJFThRLOZ9_2C0pJMQmEXaICsCsFUH.VCYSeI_uk.E0
n3LE90MJlax0BHPdz0u_RVUXqw45Zv.nu3hd2rxATzgA0BEWaVvILS5HUSwc
GgFlxxH8c79VbsdWyFu5WF08NGcaoRoTr6WwiSQX2TDfobnsMBfWHTdi4qGT
le_ADxw4Pl2lnGvjEPztp0VQFTpCBRpV_Q.EsCtsnUGAqkJ5jOzYY7tMFlAl
_Pz1m6fOW9BfEiYR6iLWPK2aM8CzpU4vu76Lrojh.NKw8XDQYB2LppLZmUEe
X1x381cVR0hyTA.X5UXMRAgtTZSaET9hVXDLZXb2vUd8coN0YOD2IzBdrAHV
UInMVX5U6yA3Ye.Re.OP1vJ2GN8dl8XHE7N33kB5UIRmYCoWDxDm8EVmLHFJ
t
Received: from [36.78.31.37] by web121005.mail.ne1.yahoo.com via HTTP; Tue,
09 Sep 2014 02:27:29 PDT
X-Rocket-MIMEInfo: 002.001,VGVzdAEwAQEBAQ--
X-Mailer: YahooMailWebService/0.8.203.696
Message-ID: 1410254849.58507.yahoomail...@web121005.mail.ne1.yahoo.com
Date: Tue, 9 Sep 2014 02:27:29 -0700
From: Rusdi rusdi...@yahoo.com
Reply-To: Rusdi rusdi...@yahoo.com
Subject: Test 2
To: ru...@indokemika.co.id ru...@indokemika.co.id
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=-406315465-2130799877-1410254849=:58507

---406315465-2130799877-1410254849=:58507
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Test
---406315465-2130799877-1410254849=:58507
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

htmlbodydiv style=3Dcolor:#000; background-color:#fff; font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo=
nt-size:12ptdivTest/div/div/body/html
---406315465-2130799877-1410254849=:58507--

Pagi ini saya coba test kembali dari Yahoo, ternyata sukses diterima.

Pertanyaan saya, apakah ISP bisa melakukan otomatis direct DNS ke mereka
walaupun saya sudah set baik di MDaemon maupun di Windows dengan DNS lain?

Terima kasih
Rusdi

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-10 10:28, alien wrote:
 Sebagai tambahan berikut error message dari Yahoo yang gagal kami
 terima :
 
 Sorry, we were unable to deliver your message to the following
 address.
 
 ru...@indokemika.co.id mailto:ru...@indokemika.co.id: Remote host
 said: 550 We don't handle mail for yahoo.com http://yahoo.com 
 [RCPT_TO]

Carikan transkrip log transaksinya di smtp-in server mail.indokemika.co.id

 Pertanyaan saya, apakah ISP bisa melakukan otomatis direct DNS ke
 mereka walaupun saya sudah set baik di MDaemon maupun di Windows
 dengan DNS lain?

Ya bisa kalau routernya mampu melakukan reroute traffic dan pengelolanya
mampu mengoperasikan.
Caranya hampir mirip dengan reroute outbound traffic port 25 ke smtp
tertentu (biasanya local smtp server mereka).

Sejak bulan lalu ISP biznet menyampaikan ke pelanggan-2x nya agar pakai
local DNS server mereka, tidak lagi pakai public DNS dan sejak awal
September 2014 ini semua koneksi ke public DNS diblock.
Kemungkinan Telkom melakukan hal yang sama, tetapi dengan cara yang
lebih elegan dengan reroute dns query traffic ke local DNS server mereka
sehingga tidak perlu melakukan pengumuman secara resmi seperti Biznet.

Nampaknya ini permintaan dari Kominfo melalui APJII (Asosiasi
Penyelenggara Jasa Internet Indonesia) untuk dilakukan semua ISP di
Indonesia dalam rangka pencegahan akses ke situs pornografi.

Menurut saya yang diblock mestinya cukup http/ftp/chat/news query ke
situs tertentu saja bukan DNS query keseluruhan, dalam hal ini cukup
pakai transprent atau keharusan proxy di pelanggan cascade lewat parent
proxynya ISP.
Handling DNS resolver itu task yang berat, aplikasi ini idle time outnya
singkat jadi response dari DNS server harus cepat, kalau mau seandal
google/Level3 DNS harus pakai multi DNS di banyak titik secara multicast.


-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-10 11:10, Syafril Hermansyah wrote:
 Pertanyaan saya, apakah ISP bisa melakukan otomatis direct DNS ke
  mereka walaupun saya sudah set baik di MDaemon maupun di Windows
  dengan DNS lain?
 Ya bisa kalau routernya mampu melakukan reroute traffic dan pengelolanya
 mampu mengoperasikan.
 Caranya hampir mirip dengan reroute outbound traffic port 25 ke smtp
 tertentu (biasanya local smtp server mereka).
^^
... untuk koneksi dari dynamic IP user.



 Sejak bulan lalu ISP biznet menyampaikan ke pelanggan-2x nya agar pakai
 local DNS server mereka, tidak lagi pakai public DNS dan sejak awal
 September 2014 ini semua koneksi ke public DNS diblock.
 Kemungkinan Telkom melakukan hal yang sama, tetapi dengan cara yang
 lebih elegan dengan reroute dns query traffic ke local DNS server mereka
 sehingga tidak perlu melakukan pengumuman secara resmi seperti Biznet.
 
 Nampaknya ini permintaan dari Kominfo melalui APJII (Asosiasi
 Penyelenggara Jasa Internet Indonesia) untuk dilakukan semua ISP di
 Indonesia dalam rangka pencegahan akses ke situs pornografi.
 
 Menurut saya yang diblock mestinya cukup http/ftp/chat/news query ke
 situs tertentu saja bukan DNS query keseluruhan, dalam hal ini cukup
 pakai transprent atau keharusan proxy di pelanggan cascade lewat parent
 proxynya ISP.
 Handling DNS resolver itu task yang berat, aplikasi ini idle time outnya
 singkat jadi response dari DNS server harus cepat, kalau mau seandal
 google/Level3 DNS harus pakai multi DNS di banyak titik secara multicast.


-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.


-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik alien 
2014-09-10 11:10 GMT+07:00 Syafril Hermansyah syaf...@dutaint.co.id:

 On 2014-09-10 10:28, alien wrote:
  Sebagai tambahan berikut error message dari Yahoo yang gagal kami
  terima :
 
  Sorry, we were unable to deliver your message to the following
  address.
 
  ru...@indokemika.co.id mailto:ru...@indokemika.co.id: Remote host
  said: 550 We don't handle mail for yahoo.com http://yahoo.com
  [RCPT_TO]

 Carikan transkrip log transaksinya di smtp-in server mail.indokemika.co.id


Log transaksi smtp-in dari server mail.indokemika.co.id adalah log yang
paling pertama saya kirimkan pada awal posting.
Sedangkan yang ini dari Yahoo saya setelah gagal kirim.




 Pertanyaan saya, apakah ISP bisa melakukan otomatis direct DNS ke
  mereka walaupun saya sudah set baik di MDaemon maupun di Windows
  dengan DNS lain?

 Ya bisa kalau routernya mampu melakukan reroute traffic dan pengelolanya
 mampu mengoperasikan.
 Caranya hampir mirip dengan reroute outbound traffic port 25 ke smtp
 tertentu (biasanya local smtp server mereka).

 Sejak bulan lalu ISP biznet menyampaikan ke pelanggan-2x nya agar pakai
 local DNS server mereka, tidak lagi pakai public DNS dan sejak awal
 September 2014 ini semua koneksi ke public DNS diblock.
 Kemungkinan Telkom melakukan hal yang sama, tetapi dengan cara yang
 lebih elegan dengan reroute dns query traffic ke local DNS server mereka
 sehingga tidak perlu melakukan pengumuman secara resmi seperti Biznet.

 Nampaknya ini permintaan dari Kominfo melalui APJII (Asosiasi
 Penyelenggara Jasa Internet Indonesia) untuk dilakukan semua ISP di
 Indonesia dalam rangka pencegahan akses ke situs pornografi.

 Menurut saya yang diblock mestinya cukup http/ftp/chat/news query ke
 situs tertentu saja bukan DNS query keseluruhan, dalam hal ini cukup
 pakai transprent atau keharusan proxy di pelanggan cascade lewat parent
 proxynya ISP.
 Handling DNS resolver itu task yang berat, aplikasi ini idle time outnya
 singkat jadi response dari DNS server harus cepat, kalau mau seandal
 google/Level3 DNS harus pakai multi DNS di banyak titik secara multicast.


Hari ini saya test kirim beberapa email dari Yahoo dan sukses bisa masuk.
 Untuk masalah reroute traffic sedang ditanyakan ke Telkom.  Sekedar
informasi, saya pakai 1 MX dengan multiple A record dengan menggunakan IP
publik statis dari Telkom dan CBN.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik alien 
2014-09-10 11:14 GMT+07:00 Syafril Hermansyah syaf...@dutaint.co.id:

 On 2014-09-10 11:10, Syafril Hermansyah wrote:
  Pertanyaan saya, apakah ISP bisa melakukan otomatis direct DNS ke
   mereka walaupun saya sudah set baik di MDaemon maupun di Windows
   dengan DNS lain?
  Ya bisa kalau routernya mampu melakukan reroute traffic dan pengelolanya
  mampu mengoperasikan.
  Caranya hampir mirip dengan reroute outbound traffic port 25 ke smtp
  tertentu (biasanya local smtp server mereka).
 ^^
 ... untuk koneksi dari dynamic IP
 user.


Saya pakai IP Statis Pak, kebetulan pakai koneksi internet dedicated.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-10 11:29, alien wrote:
  Sorry, we were unable to deliver your message to the following
  address.
 
  ru...@indokemika.co.id mailto:ru...@indokemika.co.id
 mailto:ru...@indokemika.co.id mailto:ru...@indokemika.co.id:
 Remote host
  said: 550 We don't handle mail for yahoo.com http://yahoo.com
 http://yahoo.com
  [RCPT_TO]
 
 Carikan transkrip log transaksinya di smtp-in server
 mail.indokemika.co.id http://mail.indokemika.co.id
 
 
 Log transaksi smtp-in dari server mail.indokemika.co.id
 http://mail.indokemika.co.id adalah log yang paling pertama saya
 kirimkan pada awal posting.

Mestinya bukan itu, server yahoo retry to send dan mungkin yang menolak
adalah salah satu MX backup domain Anda.

-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-10 11:30, alien wrote:
  Ya bisa kalau routernya mampu melakukan reroute traffic dan pengelolanya
  mampu mengoperasikan.
  Caranya hampir mirip dengan reroute outbound traffic port 25 ke smtp
  tertentu (biasanya local smtp server mereka).
 ^^
 ... untuk koneksi dari
 dynamic IP user.
 
 
 Saya pakai IP Statis Pak, kebetulan pakai koneksi internet dedicated. 

Untuk DNS query blocking ini nampaknya berlaku untuk semua pelanggan
dynamic maupun static IP yang digunakan untuk browsing user.
Bisa dikonsultasikan ke ISP, mnngkin bisa dikecualikan kalau yang query
dari internet mail server.


-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email dari Yahoo

2014-09-09 Terurut Topik Syafril Hermansyah 
On 2014-09-10 11:29, alien wrote:
 Sekedar informasi, saya pakai 1 MX dengan multiple A record dengan
 menggunakan IP publik statis dari Telkom dan CBN. 

Kenapa perlu banyak MX host begitu, memangnya server Anda loyo karena
diletakkan di DMZ?


-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 14.5.0 Beta RC1 SP 4.5.0 Beta B
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Netiket: http://www.netmeister.org/news/learn2quote
Arsip: http://mdaemon-l.dutaint.com
Dokumentasi : http://mdaemon.dutaint.co.id
Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi terakhir MD 14.0.3, SP 4.1.5, BES 2.0.2, OC 2.3.3, SG 3.0.1

[MDaemon-L] Gagal terima email

2009-01-15 Terurut Topik A RAMOS IDJKT IT STAFF 
 Kalau koneksi ke primary MX gagal mestinya sender host akan kirim ke MX
backup.
 Coba tanyakan ke mail hoster Anda (yg host MX backup) apakah mail  masuk
lewat sana akan tetapi gagal diteruskan ke mail.mscid.com.

Maaf Pa, 
untuk lain kali akan saya buat posting baru.

Terima kasih, saya coba contact mail hoster dulu.

Rgds,
Albri


-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.
Mohon tidak posting dengan format HTML atau Rich Text, 
pastikan selalu menggunakan Format Plain-text.

Arsip  : http://mdaemon-l.dutaint.com
Henti Langgan  : Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan   : kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi Terakhir : MD 10.0.3, SP 4.0.2, OC 2.2.1, SG 1.1.1, PP 1.1.0

[MDaemon-L] Gagal terima email

2009-01-14 Terurut Topik A RAMOS IDJKT IT STAFF 
Dear Pa Syafril,

Beberapa hari yang lalu, kami mulai tidak bisa menerima email dari domain
mscmal.com.my. Tapi kami bisa mengirim ke domain tsb tanpa masalah.
Berikut adalah log dari smpt-in mail server kami:
---
Wed 2009-01-14 08:03:27: Session 3040; child 1; thread 2988
Wed 2009-01-14 07:33:27: Accepting SMTP connection from
[202.71.104.106:14322]
Wed 2009-01-14 07:33:27: -- 220 mail.mscid.com ESMTP MDaemon 10.0.1; Wed,
14 Jan 2009 07:33:27 +0700
Wed 2009-01-14 07:33:28: -- EHLO hs3.internetnow.com.my
Wed 2009-01-14 07:33:28: -- 250-mail.mscid.com Hello
hs3.internetnow.com.my, pleased to meet you
Wed 2009-01-14 07:33:28: -- 250-ETRN
Wed 2009-01-14 07:33:28: -- 250-AUTH=LOGIN
Wed 2009-01-14 07:33:28: -- 250-AUTH LOGIN CRAM-MD5
Wed 2009-01-14 07:33:28: -- 250-8BITMIME
Wed 2009-01-14 07:33:28: -- 250-STARTTLS
Wed 2009-01-14 07:33:28: -- 250 SIZE 0
Wed 2009-01-14 07:33:28: -- MAIL FROM:elaine@mscmal.com.my SIZE=3113
Wed 2009-01-14 07:33:28: Performing SPF lookup (mscmal.com.my /
202.71.104.106)
Wed 2009-01-14 07:33:29: *  Result: none; no SPF record in DNS
Wed 2009-01-14 07:33:29:  End SPF results
Wed 2009-01-14 07:33:29: -- 250 elaine@mscmal.com.my, Sender ok
Wed 2009-01-14 07:33:29: -- RCPT TO:reffe...@mscid.com
Wed 2009-01-14 07:33:29: Performing DNS-BL lookup (202.71.104.106 -
connecting IP)
Wed 2009-01-14 07:33:29: *  zen.spamhaus.org - passed
Wed 2009-01-14 07:33:29:  End DNS-BL results
Wed 2009-01-14 07:33:29: -- 250 reffe...@mscid.com, Recipient ok
Wed 2009-01-14 07:33:30: -- DATA
Wed 2009-01-14 07:33:30: Creating temp file (SMTP):
f:\msc\mdaemon\temp\md5340697.tmp
Wed 2009-01-14 07:33:30: -- 354 Enter mail, end with CRLF.CRLF
Wed 2009-01-14 08:03:27: Connection timed out!
Wed 2009-01-14 08:03:27: SMTP session terminated (Bytes in/out: 250/358)
Wed 2009-01-14 08:03:27: --
---

Mohon pencerahannya, terima kasih sebelumnya.

Regards,
 
Albri Ramos
IT Staff


-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.
Mohon tidak posting dengan format HTML atau Rich Text, 
pastikan selalu menggunakan Format Plain-text.

Arsip  : http://mdaemon-l.dutaint.com
Henti Langgan  : Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan   : kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi Terakhir : MD 10.0.3, SP 4.0.2, OC 2.2.1, SG 1.1.1, PP 1.1.0

[MDaemon-L] Gagal terima email

2009-01-14 Terurut Topik Syafril Hermansyah 
A RAMOS IDJKT IT STAFF said the following on 15/01/09 11:52 +07:00:

/ moderator node
Kalau posting topik baru jangan dengan cara mencuri topik/thread orang
lain (mereply mail yg berasal dari milis), disamping tidak etis cara itu
juga merusak struktur arsip dan threading mode, menyulitkan pembacaan
alur diskusi.

Selalu gunakan menu new compose di email client saat posting topik baru.

/ end note.

 Beberapa hari yang lalu, kami mulai tidak bisa menerima email dari
 domain mscmal.com.my.

 Wed 2009-01-14 07:33:28: -- EHLO hs3.internetnow.com.my
 Wed 2009-01-14 07:33:28: -- 250-mail.mscid.com Hello
 hs3.internetnow.com.my, pleased to meet you

 Wed 2009-01-14 07:33:30: Creating temp file (SMTP):
 f:\msc\mdaemon\temp\md5340697.tmp
 Wed 2009-01-14 07:33:30: -- 354 Enter mail, end with CRLF.CRLF
 Wed 2009-01-14 08:03:27: Connection timed out!

Kalau koneksi ke primary MX gagal mestinya sender host akan kirim ke MX
backup.
Coba tanyakan ke mail hoster Anda (yg host MX backup) apakah mail masuk
lewat sana akan tetapi gagal diteruskan ke mail.mscid.com.


-- 
syafril
---
Syafril Hermansyah
MDaemon-L Moderators, running MDaemon 10.0.3
Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon.

-- 
--[MDaemon-L]
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.
Mohon tidak posting dengan format HTML atau Rich Text, 
pastikan selalu menggunakan Format Plain-text.

Arsip  : http://mdaemon-l.dutaint.com
Henti Langgan  : Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com
Berlangganan   : kirim mail ke MDaemon-L-subscribe [at] dutaint.com
Versi Terakhir : MD 10.0.3, SP 4.0.2, OC 2.2.1, SG 1.1.1, PP 1.1.0