| Summary | missing x-header causes spamassassin hit |
| Queue | IMP |
| Queue Version | 3.2.3 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | kevin (at) ualberta (dot) net |
| Created | 01/15/2007 (6827 days ago) |
| Due | |
| Updated | 01/19/2007 (6823 days ago) |
| Assigned | |
| Resolved | 01/19/2007 (6823 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Rejected
conf/header.txt) file.
it on http://spamassassin.apache.org/tests_3_1_x.html, so suppose they
removed this check.
State ⇒ Feedback
only MS products (that set the X-Mailer header) are using X-Priority
too. Did you ask about the rationale behind this rule?
1. I removed the other spamassassin hits for clarity. In this case
it's -98 because it was a whitelisted user.
2. I was going to also suggest that if an X-Mailer header was to be
added it should either be the name given to the server (Horde by
default), OR just the same value as the User-Agent.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ missing x-header causes spamassassin hit
Queue ⇒ IMP
State ⇒ New
/* Add the X-Priority header, if requested. This appears here since
this is the "general" location that other mail clients insert
this header. */
if ($prefs->getValue('set_priority') &&
Util::getFormData('x_priority')) {
$msg_headers->addHeader('X-Priority',
Util::getFormData('x_priority'));
}
That's great except if you don't also add an X-Mailer header,
Spamassassin complains:
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on
mailg.srv.ualberta.ca
X-Spam-Level:
X-Spam-Status: No, hits=-98.8 required=2.0 tests=BAYES_00,PRIORITY_NO_NAME,
USER_IN_WHITELIST autolearn=no version=2.64
X-Spam-Report:
* 1.2 PRIORITY_NO_NAME Message has priority setting, but no X-Mailer
I've done a little hack which just adds an X-Mailer header after the
X-Priority and it solves the problem. Perhaps it should be there by
default if IMP is going to add a priority?