Zimbra transport maps

Issue #700 invalid
Randy created an issue

Hi!

I just want to know if someone encountered the error Host or domain name not found. Type=A: Host found but no data record of requested type

How can we bypass Zimbra server to directly archive emails to mail piler with unknown domain?

Comments (8)

  1. eXtremeSHOK

    Zimbra uses postfix, so it's possible

    basically you can set postfix to directly and forward a copy of all emails to piler, or place a copy of every email into a folder.

  2. Janos SUTO repo owner

    Please don't open issues which are not issues at all. Howtos, things not related to piler itself are much better suited to the mailing list.

  3. eXtremeSHOK

    Virtually every postfix server I have encountered is setup differently.

    It depends if the the piler is on the zimbra host or a separate host, If you are running amavisd, etc.

    Usually I would configure the forward for postfix port 10025 in the /etc/postfix/master.cf and not the main.cf like most guides.

    You might want to use 25, 10025 or 10026, refer to http://www.postfix.org/SMTPD_PROXY_README.html

    If you want to store the messages locally, create a local user/mailbox on the postfix machine, Piler can import via imap/pop3 or ssh/rsync

  4. Janos SUTO repo owner

    Please check out the official piler site, you'll find several stuff worth to read. For starters I suggest you to check the piler host FQDN has a valid DNS entry (not in /etc/hosts file, but in the DNS).

  5. Randy reporter

    Hi Janos,

    I can ping the piler host FQDN from my Zimbra server, I think it is a valid DNS entry. I read about

    /etc/postfix/main.cf:

    smtpd_recipient_restrictions = reject_non_fqdn_recipient, ..., \ check_recipient_access pcre:$config_directory/x-add-envelope-to, ... Should I just add the line check_recipient_access pcre:$config_directory/x-add-envelope-to into my Zimbra server.

  6. Janos SUTO repo owner

    I didn't ask whether you can ping it. I asked whether it had a valid DNS entry, so check your domain records, and find the fqdn of the piler host. If you read the error message you posted carefully, then you can see, it's a DNS issue. Make sure to fix it.

  7. Log in to comment