mainSpamAssassin Milter Plugin - Support: sr #101005, User preferences

 
 

sr #101005: User preferences

Submitter:  None
Submitted:  Fri 14 Jun 2002 09:39:15 PM UTC
   
 
Category:  None Priority:  5 - Normal
Severity:  2 - Minor Status:  None
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 25 Sep 2004 05:39:41 PM UTC, comment #5: 

Use the -u option to spamass-milter.  You need to decide on a username to send when there are multiple recipients, since the milter is only called once even if there are multiple local recipients.  So to pass the recipient's username to spamc and use root's local settings if there are multiple local recipients, the syntax would be

spamass-milter -u root -otherargs

The CVS code has support for expanding aliases and virtusertable entries unser the -x option, and a new release will be out shortly.

Dan Nelson <dnelson>
Group administrator
Sat 25 Sep 2004 05:28:18 PM UTC, comment #4: 

"currently all it can do is
pass the original recipient username to spamc. "

How can i do this ? currently, spamass-milter passes "root" as the user to spamc, becuase this is the user running sendmail, can i make it use the user in the "rcpt to:" ?

Marco.

Marco Supino <msupino>
Fri 22 Aug 2003 06:03:01 PM UTC, comment #3: 


Messages with multiple recipients get sent only once through
the milter API, so spamass-milter calls spamc with the
fallback username specified with -u.

The next release of the milter will support
alias/virtusertable expansion; currently all it can do is
pass the original recipient username to spamc.

Dan Nelson <dnelson>
Group administrator
Fri 22 Aug 2003 04:33:12 PM UTC, comment #2: 



Even if aliases/virtusertable etc already have been
expanded - what about mails with multiple local
recipients? spamd would have to fork itself for each
recipient, drop privileges and apply each users pre-
ferences - which would consume additional resources
on the mail server.

Anonymous
Wed 26 Jun 2002 09:18:55 PM UTC, comment #1: 


It can't easily be done (and for some messages can't be done
at all).  I believe the milter gets called before delivery,
while the message is being sent by the sender.  At this
stage, all you know is MAIL FROM, RCPT TO, the headers, and
the message body.  Neither virtusertable nor aliases have
been expanded, and the incoming message might be CC'ing two
people with different personal settings.  On my system, for
example there are no local users; all email is relayed to a
Lotus Notes server.

If your setup has no aliases or virtusers, you can probably
just scan RCPT TO:, and pass the first username to spamc
with the -u flag.  This will work for most messages, but
multiple recipients will all be processed with the same
settings.

Dan Nelson <dnelson>
Group administrator
Fri 14 Jun 2002 09:39:15 PM UTC, original submission:  


Hello,

I noticed that spamass-milter doesn't allow spamd to
get proper username (userid) to get preferences. As I
understand spamd retreives preferences of user, who is
running spamc. So, spamass-milt should somehow tell
spamd which userid it should use. If I'm running
spamass-milt under root account, spamd ALWAYS trying
to retreive root's preferences and uses defaults if
there are no preferences for user root.
Or I'm doing something wrong? I'm running spamd under
root account with switches -a -x -q -D
There is everything right with SQL setup I'm sure.
Is there a fast workaround if there is really a
problem?

Thanx a lot,
Dmitry

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

No changes have been made to this item

Back to the top

Powered by Savane 3.13-5190.
Corresponding source code