namshi / docker-smtp

SMTP docker container
MIT License
548 stars 199 forks source link

Problem sending email #49

Open gilbertobr opened 5 years ago

gilbertobr commented 5 years ago

I have the following problem.

Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM PRDR OCSP
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
  278 delivering 1gwqzr-00004T-MX
  278 R: dnslookup for test@gmail.com
  278 LOG: MAIN
  278   == test@gmail.com R=dnslookup defer (-1): host lookup did not complete
  341 LOG: MAIN
  341   <= z@z170.us-east1098-b.c.windy-marker-216605.internal H=(z10.localdomain) [172.17.0.1] P=esmtp S=1031 id=201902211625.x1LGPGjL015425@zabbix10.us-east1-b.c.windy-marker-216605.internal
  341 LOG: smtp_connection MAIN
  341   SMTP connection from (z.localdomain) [172.17.0.1] closed by QUIT
  343 Exim version 4.84_2 uid=104 gid=109 pid=343 D=40001
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM PRDR OCSP
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Size of off_t: 8
  343 delivering 1gwrA7-00005V-Tr
  343 R: dnslookup for test@gmail.com
  343 LOG: MAIN
  343   == test@gmail.com R=dnslookup defer (-1): host lookup did not complete

I executed the following commands

docker run -p 2587:25 namshi/smtp

Soon after I released port 2587 from my internal network so that my other server could see.

Then I executed the command below to check the problem.

docker exec -i -t fe6e205955e1 /bin/bash

I tried pinging out ... Ex: ping 8.8.8.8 He can not even drip ...

Should we do anything else to solve this problem?