David Hrbáč wrote: > thorsten napsal(a): >>> domain1.tld has: >>> 20 server.domain2.tld >>> 10 server.domain1.tld >>> >>> domain2.tld has: >>> 20 server.domain1.tld >>> 10 server.domain2.tld >>> >>> on server.domain1.tld we need to have: >>> domain1.tld within virtual domains or local domain >>> domain2.tld within transport >>> >>> on server.domain2.tld we need to have: >>> domain2.tld within virtual domains or local domain >>> domain1.tld within transport > > So > what does return postmap -q domain2.tld mysql:/etc/postfix/sql/transport > on server.domain1.tld? > what does return postmap -q domain1.tld mysql:/etc/postfix/sql/transport > on server.domain2.tld? > That brings something to mind that I ran up against a while back. In your transport map the destination needs to be enclosed in square brackets. If not, then any MX records for it are used to determine the destination. On server.domain1.tld, the map entry for domain2.tld needs to contain 'smtp:[server.domain2.tld]' instead of 'smtp:server.domain2.tld'. The brackets tell Postfix (and Sendmail, for that matter) NOT to look up the MX records. Hope that helps! -- Jay Leafey - Memphis, TN jay.leafey at mindless.com -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5177 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20060923/e8b0add6/attachment-0005.bin>