Kevin Fitzgerald wrote:
I want to set it up so that scalix.company.dyndns.org periodically goes to
mail.company.com.au, gets the mail and puts it in the appropriate mailboxes.
I know that one way to do this would be set up forwarders at
mail.company.com.au but this does not actually clear the mailboxes there and
they will max out over time.
I wouldn't do that.
I would simply have the server use postfix transport mapslike so:
company.com.au :company.dyndns.org:2525
that is, if port 25 is not reachable.
if port 25 is reachable and you use dyndns.org, then you can simply do
it in DNS:
MX 10 mail.company.com.au
MX 20 your.server
mail.company.com.au CNAME company.dyndns.org
it does work. You do risk losing mail if their dyndns is particularly
dynnamic, and whoever happens to get their IP next is an open relay. In
the years I have been doing this for multiple customers, I haven't ever
had that happen. Dyndns has been rock solid. They also have a few tricks
to help out with hosting mail on a dyndns account - check out their
pages for more info.
So basically, I am suggesting hosting their mail directly on their
connection. Alot less dicking around with fetchmail and forwarding etc -
basically, when you add a user to the scalix setup, it just works as an
email address straight away.
dave
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
