Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 84144 - Spamassassin no longer needs -P option
Spamassassin no longer needs -P option
Product: Red Hat Raw Hide
Classification: Retired
Component: spamassassin (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Chip Turner
Depends On:
Blocks: 79579 CambridgeTarget
  Show dependency treegraph
Reported: 2003-02-12 14:39 EST by Reid Rivenburgh
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-30 19:05:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Reid Rivenburgh 2003-02-12 14:39:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210

Description of problem:
I just started using spamassassin 2.44-3.8.x from rawhide.  My log file contains
lines like:

The -P option has been removed.
From reid  Wed Feb 12 11:51:37 2003
 Subject: meeting minutes from February 12
  Folder: /home/reid/inbox                                                 8415

The -P line shouldn't be there.  I assume it's caused by the -P option in

# send mail through spamassassin
| /usr/bin/spamassassin -P

Just removing the -P should work, though I haven't tried it!

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

How reproducible:

Steps to Reproduce:
1.Include /etc/mail/spamassassin/spamassassin-default.rc in your .procmailrc.
2.Turn on logging.

Additional info:
Comment 1 Chip Turner 2003-02-13 08:57:48 EST
ahh, I use spamc/spamd, so I hadn't noticed that.  it's fixed now and should
show up in Rawhide soon.
Comment 2 Bill Nottingham 2003-07-30 19:08:18 EDT
Closing out some bugs that have been in MODIFIED state. Please reopen if they

Note You need to log in before you can comment on or make changes to this bug.