
 Things to do:   M 1).  When doing a REPLY, the "To" line you get from MAIL is empty.  Currently K      this causes a blank X-VMS-Mail-To: field.  Should I check for this and !      chuck that field completely? "   *  Done... (consider it chucked)  I 2).  Need to use ARPA RFC-822 standardized dates.  Yuck!  Only problem is (      how do I make up the time zone?????H   *  Done....  Needed system wide logical name for time-zone. Should getI                an algorithm to calculate savings versus daylight time for                 a given zone.  K 3).  Obviously this whole thing needs testing.  There have to be some nasty )      bugs lurking around in it somewhere! &   *  Looks pretty good after 6 months!  H 4).  Need to test in conjunction with DECnet.  Can I get mail from otherI      DECnet nodes to/from UUCP cleanly?  How about caveats and addressing       issues??   *  Done...  At least I know what I have to do.  See number 6.   G 5).  Need to do error handling, etc...  Maybe return undeliverable mail *      and other nasty stuff.  This is hard.  H 6).  Need to convert DECnet addresses into another form.  Will need file1      of reachable systems and how to get to them:    	fvax	decnet
 	ymir	uucp
 	cit-vax	uucp 
 	scgvaxd	smtp   E      then:  when building from, convert anything like host::user into E      host!user.  When making to, convert host!user and host::user and       user@host into one of:    	smtp%"user@host"  	uucp%"host!user"  	host::user         or error "unknown system".   G 7).  Once having sent a UUCP message, MAIL cannot get SYSPRV to deliver D      local messages.   grrrrrrrrrrr!   Have to exit mail and reenterH      to send local mail.  This is simple.  Just need to NOT modify privsI      if process already has the priv.  Exactly what MAIL does internally.       Will hack this in tonight.    *  Done...  E 8).  When sending to a list of users, if the list begins with a local C      (or DECnet) address, then MAIL may use BLOCK_IO on the message C      file.  UUCP then breaks in GET_LINE with an "operation invalid E      for record type..." error from RMS.  This is because I only ever F      use record I/O.   Have to, need to read records to parse headers.B      I think this is a bug in MAIL.  After all, if the list begins5      with a UUCP address, it opens it for record I/O. D   *  Fixed, thanks to Ned Freed.  We just reconnect the RAB allowing      either block or record IO.   O 9).  Need to rethink the way the _OUT_bound code decides if mail is originating K      here or routing through so it knows whether to make up headers or not. E      Currently it says "if the message has headers, it's probably not L      originating here so act like it's routing.  If not then make up headersI      like it came from here".   This is too stupid.  It gets confused too I      easily.  One thing I'm thinking about is in the _OUT_ code I get the M      address of who the message is FROM.  If it's from someone like UUCP%".." N      then it's obviously being routed.  If not then it needs headers.  I think*      that'll be a smarter way of doing it.M   -  Have rethought this one.  Now that MAIL isn't mapping the code in twice, N      I can use a global flag to indicate if the message going out also came inM      and hence needs header-munging, not header-making.  Not implemented yet.   K 10). Lines starting with "$" screw up incoming mail messages.  Something to G      do with the fact that that stupid subprocess that RMAIL spawns has G      the message coming from SYS$COMMAND.  Everything from the "$" line       on is missing. L    * Done...  I wanted input from SYS$INPUT instead of SYS$COMMAND.  ProblemM               was that SYS$INPUT was only a user mode logical, so was getting K               trashed by the SET PROC/PRIV command.  I now save P1 by doing J               an F$PARSE of it into itself.  This uncovered a bug in whichL               UUCP_MAIL.PAS was not opening the file READONLY, so I got fileI               locked errors.  Fixed that and now everything is just fine.   G 11). Had all sorts of problems with messages getting bounced because of $      long lines confusing Pascal IO.E    * Fixed.  Added very large max record lengths to WRITE statements. < 	     Also made debug informational writes ignore IO errors.  H 12). Made the code use the RFC-822 "From:" field preferentially over theF      UUCP "From ... remote from ..." line because more and more peopleG      support reasonable message headers and they tend to ignore getting <      the UUCP header lines to work.  Can't say I blame them.