|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: John Walker (john
jsw4.net)Date: Fri Sep 07 2001 - 19:18:06 CDT
> > Disclaimer: I haven't done this in a while. If I have
> missed something, I'm
> > sure someone will point it out.
> whereby a client ("sender-SMTP") may request that the server
In this case the client is an SMTP server, and the queue essentially gets
passed to the primary mail exchanger when it comes "on-line". The inside
(primary MX) mail server knows what to do for user
whereas the DMZ
(secondary MX) does not, the queue on the remote (DMZ host) is processed,
and delivery is accomplished for local users on the inside smtp server... I
think.
Sorry if this is not clear... (Did I mention I did this a few years ago...)
Not to mention what a great job the RFC does of explaining it. <G>
AND I COULD BE TOTALLY WRONG.
> ("receiver-SMTP") start the processing of its mail queues for
> messages that are waiting at the server for the client machine. If
> any messages are at the server for the client, then the
which is an SMTP server ^^^^^^
> server should
> create a new SMTP session and send the messages at that time.
But will the firewall let it? (I don't know.)
John
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]