-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [email protected] said the following on 25/04/11 13:31:
> I can get it to try and forward with the main.cf below but it will not > look local if not in relay_recipients. I know it has to do with the > local_recipient_maps but I can't seem to find out how to check one then > other. Maybe is not the most elegant solution, but I have a dozen of installations like yours with both all users in Excahnge and some users in Exchange and some on Linux with Postfix, Dovecot and Postfixadmin administrative interface. I set up the environment like this. Let's assume that the domain is the usual example.com, the Exchange server is exchange.example.com 192.168.1.1 and the Linux with Postfix et al. is mail.example.com 172.16.0.1 on DMZ On Exchange Server each user has two SMTP email addresses: [email protected] (primary) and [email protected]. The SMTP connector on Exchange is configured to relay all outbound SMTP messages to Linux, you do this by setting [172.16.0.1] (WITH square brackets) in the smart relay configuration of SMTP connector. On the linux server there is a DNS server with an authoritative zone of example.com with this configuration: example.com. IN NS mail.example.com. example.com. IN MX 10 mail.example.com. exchange.example.com. IN MX 10 exchange.example.com. mail.example.com. IN A 172.16.0.1 exchange.example.com. IN A 192.168.1.1 Of course the /etc/resolv.conf has just one nameserver entry like this: nameserver 127.0.0.1 In Postfix using postfixadmin SQL interface or other method you like, you define the local users (e.g. the mailboxes that do not go to Exchange) as normal local users. You put the exchange users in an alias table like this: [email protected]: [email protected] [email protected]: [email protected] [email protected]: [email protected] {and so on} As I said, this can be done better, but this works. All the rubbish mail (spam, unknown users bombings...) is stopped by Linux frontend and Exchange is pretty safe. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Houston, we've had a problem here. --Jim Lovell, "Apollo 13" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk21cpEACgkQ3kWu7Tfl6ZSWvQCcCbooPgFGhbem1nRKhJaC6j7O o4EAn0+xd55gQSVrmfTDBRb1CPVynLQe =2fV+ -----END PGP SIGNATURE-----
