Jonathan Tripathy a écrit : > Hi Everyone, > > My question isn't directly a Postfix issue, however postfix will be a > fundamental element, and any advice would be appreciated. > > I need to set up an infrastructure which uses a mixture of Linux, and > Windows (exchange server). > > Basically, for a single domain, I wish got some users to have accounts > on a Linux mail server (Something similar to > http://workaround.org/ispmail/lenny), and some to have accounts on an > Exchange server. The level of interaction between the 2 machines should > be such that users on each machine can send email to the users on the > other (As well as external mx servers of course). > > The users who have their account on the Linux server, will access their > email via IMAP (and send via SMTP). The users of have their account on > the exchange server will access their email via "Outlook Anywhere" - > this is where Exchange encapsulates RPC inside HTTPS packets, and runs > the connection on a single port (443). > > My current train on through is this: Have all incoming email terminate > on the Linux (Postfix) box. For users who have their account on the > Linux box itself, this will automatically work. For users who have their > account on the exchange server, I can use Postfix Virtual Aliases to > "forward" the mail to the account on the exchange box. The exchange box > would have to be set up with accounts that are non-accessible from > outside (e.g. us...@domain.local). Regarding access from outside, I'm > thinking of just placing the 2 servers in a DMZ, and using a single > static IP address, port forward 25 (SMTP), 110 (IMAP) to the Linux box > and and 443 (Outlook Anywhere) to the exchange box. > > Does this sound like an acceptable solution? >
yes. it is. for delivery, you can use virtual aliases: j...@example.com j...@exchange.example.com if the exchange box wants j...@example.com, you can add smtp_generic_maops entries to rewrite the address back: j...@exchange.example.com j...@example.com (This only works if the transport to exchange is "smtp", as the prefix of smtp_generic_maps suggests!). This approach is better than per user transports, because transport_maps imply performance overhead (and also: transport_maps are global inside a postfix instance, so you have less flexibility).
