Message5498
Tom Ekberg added the comment:
> Yes, this is still important to me. We don't use the email gateway
because
> of concern regarding spam and redundant Re:/Re:/Re: clutter. Having a
> configuration option so replies go to either the author or to the email
> gateway makes sense to me.
In your patched file
http://issues.roundup-tracker.org/file1496/roundupdb.py
you removed the following lines:
526 # set reply-to to the tracker
527 message['Reply-To'] = tracker_name
I propose something like this instead:
# fetch reply-to:-config:
replyto_config = self.db.config.MAIL_REPLYTO_ADR
...
if replyto_config:
if replyto_config == "AUTHOR":
replyto_adr = authaddr
else:
replyto_adr = replyto_config
else:
replyto_adr = tracker_name
message['Reply-To'] = replyto_adr
This would allow three possibilities for the new configuration option:
If not set it would use the tracker_name as it was intended in the
original Roundup design. If set to "AUTHOR" it would use the address
of the author and if set to some fixed address like "noreply@example.com"
or "moderator@example.com" it would put this in.
What do you think?
Further in file1496 you added a modification of the In-Reply-To:-header
instead. Do you remember and can explain to me why you wanted to
manipulate the In-Reply-To:-header?
I currently don't understand what you wanted to achieve by this change.
Best Regards, Peter Funk
--
Peter Funk, home: ✉Oldenburger Str.86, D-27777 Ganderkesee
mobile:+49-179-640-8878 <http://www.artcom-gmbh.de/>
office: ArtCom GmbH, ✉Haferwende 2, D-28357 Bremen, Germany |
|
Date |
User |
Action |
Args |
2016-03-21 15:55:21 | pefu | set | messageid: <1458575721.89.0.522692285731.issue2550803@psf.upfronthosting.co.za> |
2016-03-21 15:55:21 | pefu | set | recipients:
+ pefu, admin, schlatterbeck, ber, rouilj, tekberg |
2016-03-21 15:55:21 | pefu | link | issue2550803 messages |
2016-03-21 15:55:20 | pefu | create | |
|