Bug 1380862 - spamassassin service in master.cf should default to flags=R
Summary: spamassassin service in master.cf should default to flags=R
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: postfix
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-30 20:11 UTC by Brian J. Murrell
Modified: 2017-07-13 16:04 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-13 16:04:31 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Brian J. Murrell 2016-09-30 20:11:26 UTC 
Description of problem:
When configuring postfix to deliver with a content filter of the spamassassin service, rules based on Envelope Sender are not triggered.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Set up a mail server with spamassasin as the content filter for the smtp delivery service

Actual results:
No SA rules that require the Envelope Sender are run

Expected results:
Should see SA running rules against Envelope Sender

Additional info:
The spamassassin service in /etc/postfix/master.cf needs to have the flags=R added to it.
Comment 2 Jaroslav Škarvada 2016-10-25 13:11:19 UTC 
What is the request about? AFAIK postfix package doesn't provide spamassassin entry in master.cf thus we cannot add the R flag to the default configuration to support return-path. Isn't it more about documentation? E.g. KB article about this topic?
Comment 3 Brian J. Murrell 2016-10-26 11:55:12 UTC 
I guess I don't remember adding that line.  Maybe I did.  I suppose you can close this if that's the case.
Comment 5 Jaroslav Škarvada 2017-07-13 16:04:31 UTC 
Closing per comment 2 and comment 3.
Note You need to log in before you can comment on or make changes to this bug.