Bug 6617 - FreeMail rule description shows email addresses from previous messages
Summary: FreeMail rule description shows email addresses from previous messages
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Plugins (show other bugs)
Version: 3.3.2
Hardware: All All
: P2 blocker
Target Milestone: 3.4.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
: 7577 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-14 12:54 UTC by Henrik Krohns
Modified: 2018-10-04 07:51 UTC (History)
5 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Henrik Krohns 2011-06-14 13:11:28 UTC 
We could use sa-update to change default to

freemail_add_describe_email 0

To prevent any possible privacy issues.
Comment 2 D. Stussy 2011-08-25 01:52:14 UTC 
I'm seeing this too - with SA 3.3.2.  Since I use MimeDefang to call SA as as subroutine, maybe it's something to do with the invocation, or is this being seen on standalone SA instances too?

Affected rules' (descriptions):
FREEMAIL_FROM
FREEMAIL_REPLYTO_END_DIGIT
FREEMAIL_ENVFROM_END_DIGIT

This is getting really annoying when the accumulated list of freemail addresses exceeds 20.
Comment 3 Mark Martinec 2011-10-04 17:43:54 UTC 
This should probably be fixed for 3.4.0.
Comment 4 Kevin A. McGrail 2011-10-04 18:16:19 UTC 
(In reply to comment #3)
> This should probably be fixed for 3.4.0.

Agree.  It's a privacy issue.  I'll plan to take a look at it.
Comment 5 Darxus 2012-01-23 17:22:10 UTC 
Changed summary to be more clear.
Comment 6 Henrik Krohns 2012-04-01 18:43:54 UTC 
Fixed in trunk:
Sending        FreeMail.pm
Transmitting file data .
Committed revision 1308173.

Probably pointless but 3.3 also:
Sending        FreeMail.pm
Transmitting file data .
Committed revision 1308175.
Comment 7 Henrik Krohns 2018-10-04 07:51:05 UTC 
*** Bug 7577 has been marked as a duplicate of this bug. ***