This may not be specific to Red Hat only, but I figured I'd post here before I dive into sendmail's news group. Normally, we don't have any problems at all with our mail, however today we were faced with an unpredictable scenario which caught my attention immediately. Our internal (private) network relays outgoing mail through one of our servers that is connected directly to our T1 line (with a public IP). That mail server does not run any DNS, it relies on servers next to it which are in the same subnet.
Today one of the city's main fiber backbones was cut for about 3 hours time and I was faced with problems I couldn't solve: internal computers trying to send mail could no longer do so. The mail client just sat there trying to send the message and in some cases would eventually time out (mail not send), and in others it would just sit there forever (Netscape 7.02 being one of those).
So I wonder if there isn't a way where mail would just spool up on the outgoing server, so that these internal clients would still be able to (seemingly) send mail. And when the T1 link comes back up, sendmail would just spool everything out. What specifically do I need to check and/or enable in my sendmail cf to allow this behavior? Mail relays fine otherwise.
-- W | I haven't lost my mind; it's backed up on tape somewhere. +-------------------------------------------------------------------- Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130 IT Director / SysAdmin / WebSmith . 800.441.3873 x130 Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
smime.p7s
Description: S/MIME Cryptographic Signature
