You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2005/07/16 01:06:53 UTC
[Bug 4482] New: Per Email Address MySQL configurations
http://bugzilla.spamassassin.org/show_bug.cgi?id=4482
Summary: Per Email Address MySQL configurations
Product: Spamassassin
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: spamc/spamd
AssignedTo: dev@spamassassin.apache.org
ReportedBy: jaco@ngear.nl
CC: jm@jmason.org
I would like to see the addition of extra keywords in the
user_scores_sql_custom_query, something like _TO_ADDRESS_ and
_TO_ADDRESS_DOMAIN_, which will allow for having user preferences that depend
on the email address of the receiver of the email.
(I browsed through the source code a bit and I think a small change to
load_with_dbi in SQL.pm should do the trick :) , just need to get the "To:"
header information of the message that is being processed to that function.)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4482] RFE: Per Email Address MySQL configurations
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4482
------- Additional Comments From dallase@nmgi.com 2005-07-15 20:25 -------
this is not a job for spamassassin... you can pass a user argument already,
there is no reason SA should have to decode To: header info. Especially when
multiple recips are in To:, Cc:, Bcc:, this becomes a real bitch. This is best
done at the envelope level, when RCPT TO: <user> is specified, spawn off a
`spamc -u <user>`, per RCPT TO:.
you might want to read up on the article i wrote about UsingSQL on the wiki.
http://wiki.apache.org/spamassassin/UsingSQL - I have a section in there titled
"Global, Per-Domain, and Per-User Preferences via SQL". May give you some ideas...
-d
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4482] RFE: Per Email Address MySQL configurations
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4482
parkerm@pobox.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From parkerm@pobox.com 2005-07-16 12:22 -------
*** This bug has been marked as a duplicate of 3929 ***
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4482] RFE: Per Email Address MySQL configurations
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4482
------- Additional Comments From jaco@ngear.nl 2005-07-16 05:06 -------
(In reply to comment #1)
> this is not a job for spamassassin... you can pass a user argument already,
> there is no reason SA should have to decode To: header info. Especially when
> multiple recips are in To:, Cc:, Bcc:, this becomes a real bitch. This is best
> done at the envelope level, when RCPT TO: <user> is specified, spawn off a
> `spamc -u <user>`, per RCPT TO:.
>
> you might want to read up on the article i wrote about UsingSQL on the wiki.
> http://wiki.apache.org/spamassassin/UsingSQL - I have a section in there titled
> "Global, Per-Domain, and Per-User Preferences via SQL". May give you some
ideas...
>
> -d
Hi Dallas,
I actually used your article to change local.cf and set things up :)
The problem with your solution in our situation is that we would need to create
a user for every email address or at least every domain. Also, one user can have
several domains and users do not have a username in the format of name@domain.ext.
-Jaco
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4482] RFE: Per Email Address MySQL configurations
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4482
jaco@ngear.nl changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Per Email Address MySQL |RFE: Per Email Address MySQL
|configurations |configurations
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4482] RFE: Per Email Address MySQL configurations
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4482
Bob@Menschel.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |triage
------- Additional Comments From Bob@Menschel.net 2005-07-16 12:01 -------
> The problem with your solution in our situation is that we would need to create
a user for every email address or at least every domain. Also, one user can have
several domains and users do not have a username in the format of name@domain.ext.
Then how do you expect to tie the to-address (which may or may not be the user
receiving the email) or the to-domain (which may or may not be the user
receiving the email) to your receiving user's user_prefs parameters?
The only way to reliably know who will be receiving the email, so you can use
that person's individual parameters, would be to identify the receiving user,
which SA cannot determine.
Yes, you have a challenge. There may or may not be a viable solution to your
challenge. I don't think that the solution lies within SA. That solution
probably lies in whatever software is calling SA for you. Assuming it knows who
the recipient is, perhaps it can reference a table you develop matching
recipient to some pseudo-userid, and call SA with that pseudo-userid so that it
pulls the correct user_prefs parameters for you?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.