From 557516f6ff6fad3a6039af99903916aafdac0979 Mon Sep 17 00:00:00 2001
From: ajt <>
Date: Sun, 6 Jan 2002 12:06:19 -0800
Subject: [PATCH] [project @ 2002-01-06 12:06:19 by ajt] don't complain about
 missing Subject: headers, which *isn't* an rfc822 violation...

---
 scripts/process.in | 21 +++++++++++++--------
 1 file changed, 13 insertions(+), 8 deletions(-)

diff --git a/scripts/process.in b/scripts/process.in
index df163239..af5b68d0 100755
--- a/scripts/process.in
+++ b/scripts/process.in
@@ -1,5 +1,5 @@
 #!/usr/bin/perl
-# $Id: process.in,v 1.42 2002/01/06 10:46:24 ajt Exp $
+# $Id: process.in,v 1.43 2002/01/06 12:06:19 ajt Exp $
 #
 # Usage: process nn
 # Temps:  incoming/Pnn
@@ -126,14 +126,19 @@ $replytocompare= $_;
 print DEBUG "replytocompare >$replytocompare<\n";
     
 if (!defined($header{'subject'})) 
-{	$brokenness.= <<END;
+{
+#	$brokenness.= <<END;
+
+#
+#Your message did not contain a Subject field.  This is broken, I am
+#afraid - the Subject: line is a Required Header according to RFC822.
+#Please remember to include a Subject field in your messages in future.
+#If you did so the fact that it got lost probably indicates a poorly
+#configured mail system at your site or an intervening one.
+#END
+#
+# RFC822 actually lists it as an `optional-field'.
 
-Your message did not contain a Subject field.  This is broken, I am
-afraid - the Subject: line is a Required Header according to RFC822.
-Please remember to include a Subject field in your messages in future.
-If you did so the fact that it got lost probably indicates a poorly
-configured mail system at your site or an intervening one.
-END
     $subject= '(no subject)';
 } else { $subject= $header{'subject'}; }
 
-- 
2.39.5