1

Topic: Cant send to email: all recipient are invalid

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.2
- Linux/BSD distribution name and version: Centos 6.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx):   apache
- Manage mail accounts with iRedAdmin-Pro? no
- Related log if you're reporting an issue:
====
hi guys,

i've created a new iredmail +sogo vmware(domain2.com) and run it to the existing iredmail + sogo vmware(domain1.com.. so i have two vmare running on same server with different ip.
i encountered cant send to email:all recipient are invalid to my domain2.com thats newly created vmware sending email to my domain1.com.. i looked into dns related stuff.. - /var/spool/postfix/etc/resolv.conf exist and same as /etc/resolv.conf?
/var/spool/postfix/etc/hosts exist and same as /etc/hosts? and it fix it no error cant send to email:all reciepients are invalid i can send message but the problem is i cant receive emails going to domain1.com to domain2.com and vice versa..


is this postfix misconfiguration to my newly created iredmail + sogo vmware(domain2.com)  ? thanks for your help

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Cant send to email: all recipient are invalid

also i received this message...

Reporting-MTA: dns; mail.domain2.com.ph
X-Postfix-Queue-ID: XC4XXE0X27
X-Postfix-Sender: rfc822; user2@domain2.com

Final-Recipient: rfc822; user1@domain1.com.ph
Original-Recipient:
rfc822;user1@domain1.com.ph
Action: failed
Status: 4.4.1
Diagnostic-Code: X-Postfix; connect to mail.domain1.com.ph[119.xx.xxx.xx]:25:
    Connection timed out



can find solution to this. very much appreciated for help

3

Re: Cant send to email: all recipient are invalid

*) Do you have correct A/MX DNS records for both mail domain names?
*) What's the original error message?

labyumoo23 wrote:

Diagnostic-Code: X-Postfix; connect to mail.domain1.com.ph[119.xx.xxx.xx]:25:
    Connection timed out

"Connection timed out" means there's a network error, and your server cannot connect to this destination IP address. Please check your firewall and router, make sure it doesn't block it.

4

Re: Cant send to email: all recipient are invalid

how can i know if its correct a/mx dns records for both domain.. i actually new to this .. both domains are bought to the respective isp..





ZhangHuangbin wrote:

*) Do you have correct A/MX DNS records for both mail domain names?
*) What's the original error message?

labyumoo23 wrote:

Diagnostic-Code: X-Postfix; connect to mail.domain1.com.ph[119.xx.xxx.xx]:25:
    Connection timed out

"Connection timed out" means there's a network error, and your server cannot connect to this destination IP address. Please check your firewall and router, make sure it doesn't block it.

5

Re: Cant send to email: all recipient are invalid

i also run intodns both domains has

TLD Parent Check :WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can     be confusing.

Same GLUE: Looks like the A records (the GLUE) got from the parent zone check are different than the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do.I detected some problems as follows: or ns2.domains.ph the parent reported: ['72.XX.XX.XX'] and your nameservers reported: ['203.XX.X.XX']


i am running on same physical server with two vmware iredmail + sogo ..  both of it can send to gmail, yahoo . i test also from both domain1 and domain2 going to the existing squirelmail it can send and receive..

why i cant send and receive messages is due to i am running on the same physical server and it is in same ip block .. dont know the problem is it firewall dns or postfix configuration

6

Re: Cant send to email: all recipient are invalid

labyumoo23 wrote:

how can i know if its correct a/mx dns records for both domain.. i actually new to this .. both domains are bought to the respective isp..

A easy way is, show us your real domain names, so that we can help check it immediately.

7 (edited by labyumoo23 2015-12-08 18:02:46)

Re: Cant send to email: all recipient are invalid

#
# Postfix master process configuration file.  For details on the format
# of the file, see the master(5) manual page (command: "man 5 master" or
# on-line: [url]http://www.postfix.org/master.5.html).[/url]
#
# Do not forget to execute "postfix reload" after editing this file.
#
# ==========================================================================
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       -       -       -       smtpd
#smtp      inet  n       -       n       -       1       postscreen
#smtpd     pass  -       -       n       -       -       smtpd
#dnsblog   unix  -       -       n       -       0       dnsblog
#tlsproxy  unix  -       -       n       -       0       tlsproxy
#submission inet n       -       n       -       -       smtpd
#  -o syslog_name=postfix/submission
#  -o smtpd_tls_security_level=encrypt
#  -o smtpd_sasl_auth_enable=yes
#  -o smtpd_reject_unlisted_recipient=no
#  -o smtpd_client_restrictions=$mua_client_restrictions
#  -o smtpd_helo_restrictions=$mua_helo_restrictions
#  -o smtpd_sender_restrictions=$mua_sender_restrictions
#  -o smtpd_recipient_restrictions=
#  -o smtpd_relay_restrictions=permit_sasl_authenticated,reject
#  -o milter_macro_daemon_name=ORIGINATING
#smtps     inet  n       -       n       -       -       smtpd
#  -o syslog_name=postfix/smtps
#  -o smtpd_tls_wrappermode=yes
#  -o smtpd_sasl_auth_enable=yes
#  -o smtpd_reject_unlisted_recipient=no
#  -o smtpd_client_restrictions=$mua_client_restrictions
#  -o smtpd_helo_restrictions=$mua_helo_restrictions
#  -o smtpd_sender_restrictions=$mua_sender_restrictions
#  -o smtpd_recipient_restrictions=
#  -o smtpd_relay_restrictions=permit_sasl_authenticated,reject
#  -o milter_macro_daemon_name=ORIGINATING
#628       inet  n       -       n       -       -       qmqpd
pickup    unix  n       -       n       60      1       pickup
cleanup   unix  n       -       n       -       0       cleanup
qmgr      unix  n       -       n       300     1       qmgr
#qmgr     unix  n       -       n       300     1       oqmgr
tlsmgr    unix  -       -       n       1000?   1       tlsmgr
rewrite   unix  -       -       n       -       -       trivial-rewrite
bounce    unix  -       -       n       -       0       bounce
defer     unix  -       -       n       -       0       bounce
trace     unix  -       -       n       -       0       bounce
verify    unix  -       -       n       -       1       verify
flush     unix  n       -       n       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
proxywrite unix -       -       n       -       1       proxymap
smtp      unix  -       -       n       -       -       smtp
relay     unix  -       -       n       -       -       smtp
#       -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq     unix  n       -       n       -       -       showq
error     unix  -       -       n       -       -       error
retry     unix  -       -       n       -       -       error
discard   unix  -       -       n       -       -       discard
local     unix  -       n       n       -       -       local
virtual   unix  -       n       n       -       -       virtual
lmtp      unix  -       -       n       -       -       lmtp
anvil     unix  -       -       n       -       1       anvil
scache    unix  -       -       n       -       1       scache
#
# ====================================================================
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# Many of the following services use the Postfix pipe(8) delivery
# agent.  See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
# ====================================================================
#
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
#maildrop  unix  -       n       n       -       -       pipe
#  flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
#
# ====================================================================
#
# Recent Cyrus versions can use the existing "lmtp" master.cf entry.
#
# Specify in cyrus.conf:
#   lmtp    cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4
#
# Specify in main.cf one or more of the following:
#  mailbox_transport = lmtp:inet:localhost
#  virtual_transport = lmtp:inet:localhost
#
# ====================================================================
#
# Cyrus 2.1.5 (Amos Gouaux)
# Also specify in main.cf: cyrus_destination_recipient_limit=1
#
#cyrus     unix  -       n       n       -       -       pipe
#  user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
#
# ====================================================================
#
# Old example of delivery via Cyrus.
#
#old-cyrus unix  -       n       n       -       -       pipe
#  flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
#
# ====================================================================
#
# See the Postfix UUCP_README file for configuration details.
#
#uucp      unix  -       n       n       -       -       pipe
#  flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
#
# ====================================================================
#
# Other external delivery methods.
#
#ifmail    unix  -       n       n       -       -       pipe
#  flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
#
#bsmtp     unix  -       n       n       -       -       pipe
#  flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
#
#scalemail-backend unix -       n       n       -       2       pipe
#  flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store
#  ${nexthop} ${user} ${extension}
#
#mailman   unix  -       n       n       -       -       pipe
#  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
#  ${nexthop} ${user}
submission inet n       -       n       -       -       smtpd
  -o smtpd_tls_security_level=encrypt
  -o smtpd_sasl_auth_enable=yes
  -o smtpd_client_restrictions=permit_mynetworks,permit_sasl_authenticated,reject
#  -o content_filter=smtp-amavis:[127.0.0.1]:10026

# Use dovecot deliver program as LDA.
dovecot unix    -       n       n       -       -      pipe
    flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${user}@${domain} -m ${extension}

smtp-amavis unix -  -   -   -   4  smtp
    -o smtp_data_done_timeout=1200
    -o smtp_send_xforward_command=yes
    -o disable_dns_lookups=yes
    -o max_use=20

127.0.0.1:10025 inet n  -   -   -   -  smtpd
    -o content_filter=
    -o mynetworks_style=host
    -o mynetworks=127.0.0.0/8
    -o local_recipient_maps=
    -o relay_recipient_maps=
    -o strict_rfc821_envelopes=yes
    -o smtp_tls_security_level=none
    -o smtpd_tls_security_level=none
    -o smtpd_restriction_classes=
    -o smtpd_delay_reject=no
    -o smtpd_client_restrictions=permit_mynetworks,reject
    -o smtpd_helo_restrictions=
    -o smtpd_sender_restrictions=
    -o smtpd_recipient_restrictions=permit_mynetworks,reject
    -o smtpd_end_of_data_restrictions=
    -o smtpd_error_sleep_time=0
    -o smtpd_soft_error_limit=1001
    -o smtpd_hard_error_limit=1000
    -o smtpd_client_connection_count_limit=0
    -o smtpd_client_connection_rate_limit=0
    -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_address_mappings


master.cf ... im having a hard time fixing the error.. i can send gmail  yahoo, etc..

8

Re: Cant send to email: all recipient are invalid

I'm lost...

Please tell us what the problem is, and show us related error message, and related log in log files. We don't need Postfix configuration right now, we just want to correctly understand what the issue is.

We need original error message you got, so that we can help troubleshoot.

9

Re: Cant send to email: all recipient are invalid

labyumoo23 wrote:

Diagnostic-Code: X-Postfix; connect to mail.sfs.com.ph[119.92.113.146]:25:
    Connection timed out

Diagnostic-Code: X-Postfix; connect to mail.cvci.com.ph[182.18.255.204]:25:
    Connection timed out

I guess there's some network issue in your local network. Those 2 servers cannot connect to each other. It's not an issue of mail services, but it's a network issue, maybe you have incorrect firewall rules.

10

Re: Cant send to email: all recipient are invalid

ZhangHuangbin wrote:
labyumoo23 wrote:

Diagnostic-Code: X-Postfix; connect to mail.sfs.com.ph[119.92.113.146]:25:
    Connection timed out

Diagnostic-Code: X-Postfix; connect to mail.cvci.com.ph[182.18.255.204]:25:
    Connection timed out

I guess there's some network issue in your local network. Those 2 servers cannot connect to each other. It's not an issue of mail services, but it's a network issue, maybe you have incorrect firewall rules.


is it because i am running both vmware in same physical server with same ip block? as i said i can send receive to squirelmail server on my network using sfs.com.ph and cvci.com.ph.. if it is network issue i cant find difference in firewall rules. dont know what particular thing that i need to troubleshoot..

11

Re: Cant send to email: all recipient are invalid

labyumoo23 wrote:

is it because i am running both vmware in same physical server with same ip block?

No.

Track the network traffic from one VM to sfs.com.ph (or cvci.com.ph), why it cannot reach the destination?

12

Re: Cant send to email: all recipient are invalid

hi ZhangHuangbin

after searching and reading , still dont know the main problem.... so i decided to separate both of it, separate physical server and dmz port. now i can send receive messages from both domains.

running two vmware (iredmail + SOGo ) on same physical server is much better , less dmz port at the same time less hardware.

i am still working with this setup very much appreciated , any suggestion for faster solution for my problem..

13

Re: Cant send to email: all recipient are invalid

i tried this but it doesnt solve my problem.

http://www.iredmail.org/forum/topic979- … ubnet.html


as i go reading found this line to my main.cf

transport_maps = proxy:mysql:/etc/postfix/mysql/transport_maps_user.cf, proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf
virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf
virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql/virtual_mailbox_maps.cf
virtual_alias_maps = proxy:mysql:/etc/postfix/mysql/virtual_alias_maps.cf, proxy:mysql:/etc/postfix/mysql/domain_alias_maps.cf, proxy:mysql:/etc/postfix/mysql/catchall_maps.cf, proxy:mysql:/etc/postfix/mysql/domain_alias_catchall_maps.cf
sender_bcc_maps = proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_user.cf, proxy:mysql:/etc/postfix/mysql/sender_bcc_maps_domain.cf
recipient_bcc_maps = proxy:mysql:/etc/postfix/mysql/recipient_bcc_maps_user.cf, proxy:mysql:/etc/postfix/mysql/recipient_bcc_maps_domain.cf
relay_domains = $mydestination, proxy:mysql:/etc/postfix/mysql/relay_domains.cf
smtpd_sender_login_maps = proxy:mysql:/etc/postfix/mysql/sender_login_maps.cf


is it my main.cf is on right config on the other it says transport_maps = hash:/etc/postfix/transport..

14

Re: Cant send to email: all recipient are invalid

iRedMail default setting is:

transport_maps =
    proxy:mysql:/etc/postfix/mysql/transport_maps_user.cf
    proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf

In you case, you can prepend one file:

transport_maps =
    hash:/etc/postfix/transport
    proxy:mysql:/etc/postfix/mysql/transport_maps_user.cf
    proxy:mysql:/etc/postfix/mysql/transport_maps_domain.cf