Dear Pak Syafril,

 

Bisa minta tolong analisa log error kami dari ticketing system dimana ada
setting untuk SMTP.

Sebelumnya berjalan normal hingga ketika akun infra.supp...@dima.co.id
<mailto:infra.supp...@dima.co.id>  terjadi pergantian password saat kami
sesuaikan settingan di aplikasi ticketing kami terdapat error  "Failed
connect to the SMTP server" padahal jika akun tersebut digunaan untuk
setting POP3 pada aplikasi ticketing tersebut sukses dan login dari webmail
juga bisa.

 

Berikut SMTP config pada aplikasi ticketing kami:

Server: mail.dima.co.id <http://mail.dima.co.id> 

Email Address: infra.supp...@dima.co.id <mailto:infra.supp...@dima.co.id> 

Display Name: Default SMTP account

Encryption: None (sudah test SSL & TLS)

Server Port: 25 (sudah test pakai 465 & 587)

SMTP Auth Username: infra.supp...@dima.co.id
<mailto:infra.supp...@dima.co.id>  

SMTP Auth Password: xxxxxxxx 

 

Berikut POP3 config pada aplikasi ticketing kami:

Server: mail.dima.co.id <http://mail.dima.co.id> 

Encryption: none

Server Port: POP3

Login Username: infra.supp...@dima.co.id <mailto:infra.supp...@dima.co.id> 

Login Password: xxxxxxxx

 

Kami tes SMTP auth dengan user yg lain tapi ternyata errornya sama yakni
"Failed connect to the SMTP server"

 

Selanjutnya test dengan SMTP auth ke server selain Mail server kami yakni
relay SMTP ke ISP kami & gmail ternyata sukses dengan atau tanpa username &
pass SMTP Auth.

 

Kemudian kami test juga dengan menambahkan IP public server aplikasi
ticketing di MDaemon pada trusted IP, dynamic whitelist, SMTP authentication
whitelist kemudian mengosongkan kolom SMTP Auth Username &  SMTP Auth
Password pada aplikasi ticketing kami dan test config ternyata sukses "The
SMTP connection was successful"

 

Setelah itu outgoing email dari ticketing kami normal, namun ternyata tidak
100% normal, kendalanya disini ada sebagian email yang bisa terkirim &
sebagian yang tidak dengan mailbounce sbb:

 

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  tgr.control...@dima.co.id <mailto:tgr.control...@dima.co.id> 
    host mx1.dima.co.id <http://mx1.dima.co.id>  [116.254.100.37]
    SMTP error from remote mail server after MAIL
FROM:<infra.supp...@dima.co.id <mailto:infra.supp...@dima.co.id> >
SIZE=5898:
    530 5.7.0 Authentication required

  _____  

Reporting-MTA: dns; mx37.antispamcloud.com <http://mx37.antispamcloud.com> 

Action: failed
Final-Recipient: rfc822;tgr.control...@dima.co.id
Status: 5.0.0
Remote-MTA: dns; mx1.dima.co.id <http://mx1.dima.co.id> 
Diagnostic-Code: smtp; 530 5.7.0 Authentication required

 

---

 

Ini ada error log juga yg sempat kami capture ketika menggunakan SMTP server
antispam ISP kami dimana sebagian ada yg sukses terkirim & sebagian tidak:

 

Mon 2018-06-25 11:08:56.417: ----------

Mon 2018-06-25 11:08:56.026: [351867] Session 351867; child 0005

Mon 2018-06-25 11:08:56.026: [351867] Accepting SMTP connection from
46.165.233.176:34692 <http://46.165.233.176:34692>  to 116.254.100.37:25
<http://116.254.100.37:25> 

Mon 2018-06-25 11:08:56.027: [351867] --> 220-edm.ed-dima.com
<http://220-edm.ed-dima.com>  ESMTP Mon, 25 Jun 2018 11:08:56 +0700

Mon 2018-06-25 11:08:56.027: [351867] --> 220-"PT. Esham Dima Mandiri Mail
Server"

Mon 2018-06-25 11:08:56.027: [351867] --> 220-"All transactions and IP
addresses are logged"

Mon 2018-06-25 11:08:56.027: [351867] --> 220-"By IT-DIMA Dept."

Mon 2018-06-25 11:08:56.027: [351867] --> 220 "2012-2013"

Mon 2018-06-25 11:08:56.412: [351867] <-- EHLO port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com> 

Mon 2018-06-25 11:08:56.413: [351867] Performing SPF lookup
(port25.smtp.antispamcloud.com <http://port25.smtp.antispamcloud.com>  /
46.165.233.176)

Mon 2018-06-25 11:08:56.608: [351867] *  Result: none; no SPF record in DNS

Mon 2018-06-25 11:08:56.608: [351867] ---- End SPF results

Mon 2018-06-25 11:08:56.608: [351867] --> 250-edm.ed-dima.com
<http://250-edm.ed-dima.com>  Hello port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  [46.165.233.176], pleased to meet
you

Mon 2018-06-25 11:08:56.608: [351867] --> 250-ETRN

Mon 2018-06-25 11:08:56.608: [351867] Location Screening hiding AUTH from
country Germany

Mon 2018-06-25 11:08:56.608: [351867] --> 250-8BITMIME

Mon 2018-06-25 11:08:56.608: [351867] --> 250-ENHANCEDSTATUSCODES

Mon 2018-06-25 11:08:56.608: [351867] --> 250-STARTTLS

Mon 2018-06-25 11:08:56.608: [351867] --> 250 SIZE 15360000

Mon 2018-06-25 11:08:56.886: [351867] <-- STARTTLS

Mon 2018-06-25 11:08:56.886: [351867] --> 220 2.7.0 Ready to start TLS

Mon 2018-06-25 11:08:57.453: [351867] SSL negotiation successful (TLS 1.2,
2048 bit key exchange, 128 bit AES encryption)

Mon 2018-06-25 11:08:57.730: [351867] <-- EHLO port25.smtp.antispamcloud.com

Mon 2018-06-25 11:08:57.731: [351867] Performing SPF lookup
(port25.smtp.antispamcloud.com <http://port25.smtp.antispamcloud.com>  /
46.165.233.176)

Mon 2018-06-25 11:08:57.755: [351867] *  Result: none; no SPF record in DNS

Mon 2018-06-25 11:08:57.755: [351867] ---- End SPF results

Mon 2018-06-25 11:08:57.755: [351867] --> 250-edm.ed-dima.com
<http://250-edm.ed-dima.com>  Hello port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  [46.165.233.176], pleased to meet
you

Mon 2018-06-25 11:08:57.755: [351867] --> 250-ETRN

Mon 2018-06-25 11:08:57.755: [351867] Location Screening hiding AUTH from
country Germany

Mon 2018-06-25 11:08:57.755: [351867] --> 250-8BITMIME

Mon 2018-06-25 11:08:57.755: [351867] --> 250-ENHANCEDSTATUSCODES

Mon 2018-06-25 11:08:57.755: [351867] --> 250 SIZE 15360000

Mon 2018-06-25 11:08:58.033: [351867] <-- MAIL
FROM:<infra.supp...@dima.co.id <mailto:infra.supp...@dima.co.id> >
SIZE=803790

Mon 2018-06-25 11:08:58.038: [351867] Performing PTR lookup
(176.233.165.46.IN-ADDR.ARPA)

Mon 2018-06-25 11:08:58.040: [351867] *  D=176.233.165.46.IN-ADDR.ARPA
TTL=(174) PTR=[port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com> ]

Mon 2018-06-25 11:08:58.208: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[95.211.233.209]

Mon 2018-06-25 11:08:58.208: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[138.201.61.184]

Mon 2018-06-25 11:08:58.208: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[192.96.201.230]

Mon 2018-06-25 11:08:58.208: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[46.165.233.176]

Mon 2018-06-25 11:08:58.208: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[46.165.247.198]

Mon 2018-06-25 11:08:58.208: [351867] ---- End PTR results

Mon 2018-06-25 11:08:58.212: [351867] Performing IP lookup
(port25.smtp.antispamcloud.com <http://port25.smtp.antispamcloud.com> )

Mon 2018-06-25 11:08:58.214: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[46.165.247.198]

Mon 2018-06-25 11:08:58.214: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[95.211.233.209]

Mon 2018-06-25 11:08:58.214: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[138.201.61.184]

Mon 2018-06-25 11:08:58.214: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[192.96.201.230]

Mon 2018-06-25 11:08:58.214: [351867] *  D=port25.smtp.antispamcloud.com
<http://port25.smtp.antispamcloud.com>  TTL=(1) A=[46.165.233.176]

Mon 2018-06-25 11:08:58.214: [351867] ---- End IP lookup results

Mon 2018-06-25 11:08:58.214: [351867] --> 530 5.7.0 Authentication required

Mon 2018-06-25 11:08:58.214: [351867] infra.supp...@dima.co.id
<mailto:infra.supp...@dima.co.id>  may not send mail from 46.165.233.176 (IP
Shield)

Mon 2018-06-25 11:08:58.503: [351867] <-- QUIT

Mon 2018-06-25 11:08:58.503: [351867] --> 221 2.0.0 See ya in cyberspace

Mon 2018-06-25 11:08:58.504: [351867] SMTP session terminated (Bytes in/out:
1044/5894)

Mon 2018-06-25 11:08:58.504: ----------

 

---

 

 

Kemudian kami coba test SMTP setting di aplikasi ticketing kami dengan salah
user auth m...@dima.co.id <mailto:m...@dima.co.id>  dan diisikan passwordnya
ternyata bisa, namun ini juga tidak 100% normal karena ada sebagian yang
terkirim & sebagian yang tidak dengan error log sbb:

 

Fri 2018-06-29 13:07:00.979: [701052] Session 701052; child 0003

Fri 2018-06-29 13:07:00.979: [701052] Accepting SMTP connection from
116.254.100.33:60694 <http://116.254.100.33:60694>  to 116.254.100.37:25
<http://116.254.100.37:25> 

Fri 2018-06-29 13:07:00.980: [701052] --> 220-edm.ed-dima.com
<http://220-edm.ed-dima.com>  ESMTP Fri, 29 Jun 2018 13:07:00 +0700

Fri 2018-06-29 13:07:00.980: [701052] --> 220-"PT. Esham Dima Mandiri Mail
Server"

Fri 2018-06-29 13:07:00.980: [701052] --> 220-"All transactions and IP
addresses are logged"

Fri 2018-06-29 13:07:00.980: [701052] --> 220-"By IT-DIMA Dept."

Fri 2018-06-29 13:07:00.980: [701052] --> 220 "2012-2013"

Fri 2018-06-29 13:07:00.987: [701052] <-- EHLO PT-SLK5RCLVNEQ9

Fri 2018-06-29 13:07:00.987: [701052] --> 250-edm.ed-dima.com
<http://250-edm.ed-dima.com>  Hello PT-SLK5RCLVNEQ9 [116.254.100.33],
pleased to meet you

Fri 2018-06-29 13:07:00.987: [701052] --> 250-ETRN

Fri 2018-06-29 13:07:00.987: [701052] --> 250-AUTH LOGIN CRAM-MD5 PLAIN

Fri 2018-06-29 13:07:00.987: [701052] --> 250-8BITMIME

Fri 2018-06-29 13:07:00.987: [701052] --> 250-ENHANCEDSTATUSCODES

Fri 2018-06-29 13:07:00.987: [701052] --> 250-STARTTLS

Fri 2018-06-29 13:07:00.987: [701052] --> 250 SIZE 15360000

Fri 2018-06-29 13:07:01.017: [701052] <-- AUTH CRAM-MD5

Fri 2018-06-29 13:07:01.017: [701052] --> 334
PE1EQUVNT04tRjIwMTgwNjI5MTMwNy5BQTA3MDExN01EMjgxN0BlZG0uZWQtZGltYS5jb20+

Fri 2018-06-29 13:07:01.048: [701052] <--
bWRtQGRpbWEuY28uaWQgZDhlOTdjYzI3YjI0ZTJiNmUzM2Y4YTdlZmY2YmNhNTI=

Fri 2018-06-29 13:07:01.048: [701052] Authenticating m...@dima.co.id
<mailto:m...@dima.co.id> ...

Fri 2018-06-29 13:07:01.050: [701052] Authenticated as m...@dima.co.id
<mailto:m...@dima.co.id> 

Fri 2018-06-29 13:07:01.050: [701052] --> 235 2.7.0 Authentication
successful

Fri 2018-06-29 13:07:01.080: [701052] <-- MAIL
FROM:<infra.supp...@dima.co.id <mailto:infra.supp...@dima.co.id> >

Fri 2018-06-29 13:07:01.081: [701052] --> 530 5.7.0 Authentication required

Fri 2018-06-29 13:07:01.111: [701052] <-- QUIT

Fri 2018-06-29 13:07:01.111: [701052] --> 221 2.0.0 See ya in cyberspace

Fri 2018-06-29 13:07:01.111: [701052] SMTP session terminated (Bytes in/out:
147/570)

---

 

 

Mohon bantuannya dari Pak Syafril terkait error log 530 5.7.0 Authentication
required yang sering terjadi, dimana kami mengarahkan SMTP server ke mail
server kami sendiri, terimakasih.

==================== 

 

Thank's

 

 

Heryanto

 


-- 
--[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 MD 18.0.2, SG 5.5.0

Kirim email ke