In article <[EMAIL PROTECTED]>, Ron Bickers wrote:
>> This looks benign to me, but I don't use RECIPIENT_HEADER myself.
>> Could someone who does comment on the proposed change? Would it break
>> anything in your current setup?
>
> I use RECIPIENT_HEADER to get the original recipient for putting in the
> confirmation messages. When the delivery takes place, my incoming rules are
> built based on the final address that is used for delivery.
[...]
> How about making this extraction happen only if EXT/EXTENSION isn't set.
I don't have any objection to this. Reworked patch (untested as of
yet, I'll test tomorrow and report back) attached below.
Ed
--- bin/tmda-rfilter.ext_from_header Thu Feb 20 19:09:40 2003
+++ bin/tmda-rfilter Sun Mar 2 01:49:24 2003
@@ -184,6 +184,12 @@
# EXT is the recipient address extension.
address_extension = (os.environ.get('EXT') # qmail
or os.environ.get('EXTENSION')) # Postfix
+if not address_extension and (Defaults.RECIPIENT_HEADER and recipient_header):
+ recip = recipient_header.split('@')[0] # remove domain
+ if recip:
+ pieces = recip.split(Defaults.RECIPIENT_DELIMITER, 1)
+ if len(pieces) > 1:
+ address_extension = pieces[1]
# If SENDER exists but its value is empty, the message has an empty
# envelope sender. Set it to the string '<>' so it can be matched as
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
