--- 00TODO 2001/08/20 14:11:30 1.13
+++ 00TODO 2001/08/23 07:57:08 1.14
@@ -1,108 +1,34 @@
-test auf mail.de.cw.net
whatsup draufleiten
-----------
dmalloc
-
FIXMEs
-//
DEBUGs
RFC1891 ENVID
RFC1891 6.2
FALSE, TRUE vs. == FALSE, == TRUE, != FALSE, != TRUE
--h needs to understand multiple hosts as commaseparated list
+-h needs to understand multiple hosts as comma separated list
+NUL statt '\0'
+ID logging problem
+
+lmtp_response segfaults when a physical line ('\n' terminated) of the logical
+line input exceeds LMTP_LINE_MAXLEN.
**** LMTP REDESIGN ****
RESULT:
- robust checking and handling of NNTP protocol errors
- - logging into a single file -> write(2) !fwrite(3)
+- logging into a single file -> write(2) !fwrite(3), (optional) syslog
- invoked as mailer using LMTP, providing useful return status
- invoked as command line (lowpri)
- queuing is not supported for command line and a client issue for LMTP
- remove To: and Cc: headers
- allow crosspostings only through command line
- new manpage
- - (optional) syslog
-- command line choice for sending "exactly once" or "at least once" (default)
-
- **** SMTP ENGINE ****
-
-[RFC821, 4.5.1. MINIMUM IMPLEMENTATION]
-In order to make SMTP workable, the following minimum implementation is required for all receivers:
-[RFC821, 4.1.2. COMMAND SYNTAX]
-
-Verb Parameter Buffer
-----+---------------------------------+-------------------
-HELO <SP> <domain> <CRLF>
-MAIL <SP> FROM:<reverse-path> <CRLF> (char *)sender
-RCPT <SP> TO:<forward-path> <CRLF> (char **)recipients
-DATA <CRLF> (char *)message
-RSET <CRLF>
-NOOP <CRLF>
-QUIT <CRLF>
-
-
-rfc822 header parsing from petidomo
-o posting@news.de.cw.net
- Newsgroup: cw.alert
-
-o posting+cw.alert@news.de.cw.net
-
-o cw.alert@news.de.cw.net
- cw.alert: "|lmtp2nntp ..."
-
-o cw.alert@news.de.cw.net
- cw.alert: "|lmtp2nntp ... -d cw.alert"
-
-ID logging problem
+ **** DEVELOPMENT INFORMATION ****
news-muc1.de.cw.net Feeder
news-ffm2.de.cw.net Feeder
news-dus2.de.cw.net Feeder
news.ecrc.de Feeder/Reader
- *************
- **** SMTP ***
- *************
-
---- RFC2800 ----
-2800 Internet Official Protocol Standards. J. Reynolds, R. Braden, S.
- Ginoza. May 2001. (Format: TXT=101648 bytes) (Obsoletes RFC2700)
- (Also STD1) (Status: STANDARD)
- RFC STD
-SMTP-Pipe SMTP Service Extension for Command Pipelining 2920 60*
-SMTP [Reserved for Simple Mail Transfer Protocol (SMTP). 10*
- See RFC 2821.]
-MAIL [Reserved for Internet Message Format. See RFC 11*
- See RFC 2822.]
-
---- RFC2821 ---
-2821 Simple Mail Transfer Protocol. J. Klensin, Editor. April 2001.
- (Format: TXT=192504 bytes) (Obsoletes RFC0821, RFC0974, RFC1869)
- (Status: PROPOSED STANDARD)
-
---- RFC2822 ---
-2822 Internet Message Format. P. Resnick, Editor. April 2001. (Format:
- TXT=110695 bytes) (Obsoletes RFC0822) (Status: PROPOSED STANDARD)
-
---- RFC2920 ---
-2920 SMTP Service Extension for Command Pipelining. N. Freed.
- September 2000. (Format: TXT=17065 bytes) (Obsoletes RFC2197) (Also
- STD0060) (Status: STANDARD)
-
- *************
- **** NNTP ***
- *************
-
-0977 Network News Transfer Protocol. B. Kantor, P. Lapsley.
- Feb-01-1986. (Format: TXT=55062 bytes) (Status: PROPOSED STANDARD)
-
-1036 Standard for interchange of USENET messages. M.R. Horton, R.
- Adams. Dec-01-1987. (Format: TXT=46891 bytes) (Obsoletes RFC0850)
- (Status: UNKNOWN)
-
-2980 Common NNTP Extensions. S. Barber. October 2000. (Format:
- TXT=57165 bytes) (Status: INFORMATIONAL)
-
|
