aduh sorry nih, tadinya ngga pengen ngomentarin, tapi
bener2 konsep *timeout* ini menurut saya sudah mulai bias.

>Pertama, RFC (1123) jelas membedakan session timeout dengan
>inactivity timeout (idle timeout) seperti yang dimaksud Bung Dani.

silahkan baca lagi posting2 dari saya sebelumnya. *timeout* selalu saya
hubungkan
dengan "delay antara 1 pengiriman data dengan pengiriman selanjutnya".
terus terang saya ngga ngerti apa yg anda maksud dgn "perbedaan antara
session timeout dan inactivity timeout" . statement anda menerangkan
seolah olah ada 2 jenis timeout (session dan idle).
bagi saya, timeout itu - dimanapun berada, di session itu sendiri 
(istilah rfc adalah "per-command timeout") ataupun di *antar session* -
selalu berhubungan dengan *inactivity state* (baca:delay). 
jadi, kalau nilai delay=nilai timeout, maka aktivitas itu harus dihentikan.

ok deh, daripada saya dibilang st...saya quote sebagian isi rfc 1123 yah
biar jelas 
persepsi masing2 ttg *timeout* itu:

source:http://www.cis.ohio-state.edu/htbin/rfc/rfc1123.html

....
....
Based on extensive experience with busy mail-relay hosts, the
minimum per-command timeout values SHOULD be as follows:
            
 o    Initial 220 Message: 5 minutes
      A Sender-SMTP process needs to distinguish between a
      failed TCP connection and a delay in receiving the initial
                                  ^^^^^             
      220 greeting message.  Many receiver-SMTPs will accept a
      TCP connection but delay delivery of the 220 message until
                         ^^^^^
              their system load will permit more mail to be processed.

         o    MAIL Command: 5 minutes
         o    RCPT Command: 5 minutes
              A longer timeout would be required if processing of
              mailing lists and aliases were not deferred until after
              the message was accepted.
         o    DATA Initiation: 2 minutes
              This is while awaiting the "354 Start Input" reply to a
                      ^^^^^^^^^^^^^^
              DATA command.
         o    Data Block: 3 minutes 
              This is while awaiting the completion of each TCP SEND
                         ^^^^^^^^^^^^^^
              call transmitting a chunk of data.
 
         o    DATA Termination: 10 minutes. 
              This is while awaiting the "250 OK" reply. When the
                      ^^^^^^^^^^^^^^
              receiver gets the final period terminating the message
              data, it typically performs processing to deliver the
              message to a user mailbox.  A spurious timeout at this
              point would be very wasteful, since the message has been
              successfully sent.
 
         A receiver-SMTP SHOULD have a timeout of at least 5 minutes
         while it is awaiting the next command from the sender.
                     ^^^^^^^^^^^^^^^^^^^^^^^^^ 

semua yg saya tandai itu (kata2 "while awaiting") artinya "selagi menunggu
(yg berikutnya datang)" alias "delay". entah kalau penerjemahan anda berbeda.
bagaimanapun, saya tidak menutup kemungkinan kalau penerjemahan saya salah.
so, cmiiw.

-DM-

-- 
--MDaemon-L----------------------------------------------------------
Milis ini untuk Diskusi antar pengguna MDaemon Mail Server.

Untuk menghubungi moderator/List Owner double click link dibawah ini:
   <mailto:[EMAIL PROTECTED]>
Untuk Unsubscribe, double click link dibawah ini langsung kirim
   <mailto:[EMAIL PROTECTED]>
Untuk Subscribe, double click link dibawah ini langsung kirim
  <mailto:[EMAIL PROTECTED]>
--POWERED BY MDAEMON!------------------------------------------------


Anda terdaftar di List ini dg alamat : [email protected]


Kirim email ke