1

Topic: Unable to Send mails to particular domain

==== Required information ====
- iRedMail version: 7.04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):MySQL
- Linux/BSD distribution name and version: Centos 6.0
- Related log if you're reporting an issue:  Server postfix log attached.
====

Hi,

When i send emails to particular domain i get the attached error message.but i can send mails to that domain from other mail server like yahoo.com,gmail. etc. can you tell me how can i resolve this issue. please check the attached message and revert.

Regards
Hariesh

Sep  6 16:02:36 koc postfix/smtp[14400]: 34E8164019C: lost connection with primary.ashimagroup.com[203.88.135.146] while sending RCPT TO
Sep  6 16:02:36 koc postfix/smtp[14403]: D56996400F5: lost connection with primary.ashimagroup.com[203.88.135.146] while sending RCPT TO
Sep  6 16:02:36 koc postfix/smtp[14402]: D06386400C0: lost connection with primary.ashimagroup.com[203.88.135.146] while sending RCPT TO
Sep  6 16:02:36 koc postfix/smtp[14404]: E7BE86400B4: lost connection with primary.ashimagroup.com[203.88.135.146] while sending RCPT TO
Sep  6 16:02:36 koc postfix/smtp[14405]: 2406C6400F4: lost connection with primary.ashimagroup.com[203.88.135.146] while sending RCPT TO
Sep  6 16:02:37 koc postfix/smtp[14400]: 34E8164019C: to=<rakesh.shrivastav@ashimagroup.com>, relay=sec.ashimagroup.com[124.247.213.213]:25, delay=85706, delays=85704/0.03/1.6/0.23, dsn=4.4.2, status=deferred (lost connection with sec.ashimagroup.com[124.247.213.213] while sending RCPT TO)
Sep  6 16:02:37 koc postfix/smtp[14402]: D06386400C0: to=<amit.thakkar@ashimagroup.com>, relay=sec.ashimagroup.com[124.247.213.213]:25, delay=20770, delays=20768/0.02/1.6/0.23, dsn=4.4.2, status=deferred (lost connection with sec.ashimagroup.com[124.

----

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

2

Re: Unable to Send mails to particular domain

Please always paste log directly, not attached the log file.

Looks like a network issue between your server and primary.ashimagroup.com. Not sure it's a temporary or permanent issue. For example, your firewall, network router.