This file lists any known problems at time of release.

As at 5 Oct 1998

We only make literal matches when checking sites listed in the conf file
i.e. name OR IP address so if you have any doubt specify both.
(See INSTALL for more comments on this.)

Startup can be 'slow' and the whole configuration file is read each time a
connection is made  (see TODO re: making blackmail a daemon)

No malloc calls are error checked (yet), so if you run out of virtual memory
weird things could happen.

Normally, the connecting host is written to the command line buffer so
that it will appear in ps/top etc. Apparently this code doesn't work on NEXT,
so it is #ifdef'd out. If any NEXT users can fix this - please send me a
patch. 

Headers are not processed strictly to RFC822 : it allows some bizarre multi-
line whitespaced fields that I have never seen in normal mail. I don't
think we are fully compliant now (1 Feb 98) but the code handles normal
examples of wrapped lines.

It has been reported that when senders use very large numbers of addresses
on the To: line the mail can be rejected although it doesn't exceed the
line length.
Very long lines have caused segfaults, increasing the buffer sizes in 0.28pre17
should help, but is the root cause fixed?

Some (well hidden) spam still gets through!


If you find any bugs or misfeatures in Blackmail, please let me
know - I'll do my best to fix them.
