-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 19 Jan 00, at 9:37, Jennifer Tippens wrote:
> Hello,
> I need ideas on what to do in my situation:
> Our company's web server is on the other side of the country. We get
> mail at our domain here because I have the zone file set up that way.
> So mail comes to our firewall, no problem. What we would like to do
> is have all mail forwarded through the firewall to an internal
> machine. I understand that I could do this with .forward or
> fastforward, but I thought that if I did that and the internal mail
> server went down for any weird reason that the mail would bounce.
> What I would like is for the mail to spool up on the firewall if the
> internal server is down. I thought about fetchmail, but I didn't
> really want everyone to have to maintain a .fetchmailrc and launch
> fetchmail -- and I have no idea what everyone's passwords are either.
> The user names on both the firewall and the internal machine are the
> same in every case. What is the best way to handle this? We have a
> lot of users.
Don't deliver the mail at the firewall host - route it to the internal
host by the means of smtproutes. Don't worry about outages of
internal servers unless they are longer than a week. qmail will
accept the mail for the domain, keep it in queue, and forward to the
internal server when it's online.
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBOIXsNlMwP8g7qbw/EQJ5LwCfY8nrdZCLbhcEM9nJPD/iXv5nojwAn0JH
bU6gRrbityhGgx7cAqxJF4wV
=B4F+
-----END PGP SIGNATURE-----
--
Petr Novotny, ANTEK CS
[EMAIL PROTECTED]
http://www.antek.cz
PGP key ID: 0x3BA9BC3F
-- Don't you know there ain't no devil there's just God when he's drunk.
[Tom Waits]
