I tested postfix -- they simply strip spurious Return-path headers, which is entirely reasonable and suitable.
If I write a patch that changes Courier to act the same way, will you include it in future releases? This small change would a) break nothing, and b) make Novell GroupWise compatible with Courier.
Ok, I'll agree to that.
Thanks. :-)
best, Jeff
Index: courier/submit.C =================================================================== --- courier/submit.C Sun May 9 11:04:40 2004 +++ courier/submit.C Sun May 9 11:03:34 2004 @@ -1250,7 +1250,7 @@ // Rewrite every RFC822 header we can find.
- if (headername == "bcc")
+ if (headername == "bcc" || headername == "return-path")
{
- // ... except this one
+ // ... except these two headerlimit += headerl;
@@ -1302,9 +1302,4 @@
else if (headername == "date") has_date=1;- // Quote Return-Path:'s at this point
-
- if (headername == "return-path")
- headernameorig=">"+headernameorig;
-
my_rcptinfo.submitfile.Message(headernameorig);
my_rcptinfo.submitfile.Message(":");
Index: ChangeLog
===================================================================
--- ChangeLog Sun May 9 14:51:51 2004
+++ ChangeLog Sun May 9 14:55:50 2004
@@ -1,2 +1,7 @@
+2004-05-09 Jeff Potter <[EMAIL PROTECTED]>
+
+ * courier/submit.C: Remove extraneous return-path headers, instead
+ of quoting them.
+
2004-05-01 Brian Candler <[EMAIL PROTECTED]>
-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
