1 Topic by craig

  • craig
  • Member
  • Offline
  • From: Canada
  • Registered: 2013-09-04
  • Posts: 271

Topic: Mail transport unavailable

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.8
- Linux/BSD distribution name and version: CentOS 7.5
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL/MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro?: Yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

I'm seeing a bunch of messages to only one domain on the server in the queue that look like this:

CEF33C61438    10113 Tue Jun 12 09:32:40  sender@example.com
                                                  (mail transport unavailable)
                                         recipient@domainonourserver.com

I found references to Amavis in the archives, but why is this affecting only one domain?

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,792

Re: Mail transport unavailable

Usually it means you set a wrong transport program for this domain.
You need to check Postfix log file to find more details and figure it out.

3 Reply by craig

  • craig
  • Member
  • Offline
  • From: Canada
  • Registered: 2013-09-04
  • Posts: 271

Re: Mail transport unavailable

ZhangHuangbin wrote:

Usually it means you set a wrong transport program for this domain.

All I did was add it through iRedAdmin-Pro, just as I do any other domain.

I guess I will just delete it and re-add it and see if that fixes the problem.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,792

Re: Mail transport unavailable

If you need assistance, please extract (FULL + ORIGINAL) related log from Postfix log file and paste here for troubleshooting.