On Tue, 14 Sep 2010 18:51:35 -0500, Stan Hoeppner <[email protected]> wrote: > Kaz Kylheku put forth on 9/14/2010 5:35 PM: > >> One solution would be to set up a mail server in the CS department; >> maybe the University IT would go for that, depending on the >> rapport between them and the CS dept. > > This is technically feasible. > >> Give this mailo server its own mail domain (MX record). > > This is probably not politically feasible. > >> Then install whatever mail handling software you want for >> you and your colleagues. >> >> The only missing piece would be to forward your University >> e-mail (going to y...@university) to your CS mail server >> ([email protected]). > > This is properly done with mail _routing_ not forwarding. You don't > want to use forwarding in this scenario.
In this scenario, there is mail coming in which is directed to "per...@university". Whether or not it goes to "[email protected]" is determined strictly on the identity of "person" and nothing else. Moreover, the address has to be rewritten to "[email protected]" (the proper mail domain of the target server). This is functionally indistinguishable from forwarding. The admins probably don't want to maintain such a mapping themselves, if it can be achieved by a self-serve forwarding configuration. Correct my misunderstanding, but mail routing would be if the "university" mail server also accepted mail for the "cs.university" domain, and passed it on to the right server, no? _______________________________________________ List info: http://lists.roundcube.net/users/ BT/8f4f07cd
