On Thu, 16 Jun 2011 12:40:02 +0200 Claudio Prono <[email protected]> wrote:
> > > Il 16/06/2011 12.09, Stevan Bajić ha scritto: > > On Thu, 16 Jun 2011 12:00:24 +0200 > > Claudio Prono <[email protected]> wrote: > > > >> > >> Il 16/06/2011 11.33, Stevan Bajić ha scritto: > >>> On Thu, 16 Jun 2011 11:27:30 +0200 > >>> Claudio Prono <[email protected]> wrote: > >>> > >>> [...] > >>>> No, i send the mail for retrain with this two lines: > >>>> > >>>> spam unix - n n - - pipe > >>>> flags=Ru user=dspam argv=/usr/sbin/dspam --class=spam --source=error > >>>> --user spam > >>>> nospam unix - n n - - pipe > >>>> flags=Ru user=dspam argv=/usr/sbin/dspam --class=innocent > >>>> --source=error --user spam > >>>> > >>>> With this option, with the option of postfix "recipient_delimiter = -" i > >>>> can send mail to [email protected] or [email protected] to > >>>> retrain the antispam the mail is spam or notspam. > >>>> > >>> How is Postfix supposed to know that it should use the service > >>> spam/nonspam? You must have somewhere some config that tells Postfix that > >>> nonspam-[email] should be processed with the service "nonspam" and that > >>> spam-[email] should be processed with the service "spam". Have you maybe > >>> set some alias inside Postfix or a header check or anything other. You > >>> must have something in place for that. > >>> > >> Postfix know if is spam or nospam with the suffix from the mail. If the > >> recipient of the mail is spam-user@domain, it will use the line spam, if > >> is nospam-user@domain, it will use the line nospam. > >> > > No! Postfix does not know anything about that by default. YOU have to > > configure/tell Postfix how to handle recipients. > > > Sorry, my fault, the recipients are configured into file > "/etc/postfix/dspam_domains", it contains: > > [email protected] FILTER spam: > [email protected] FILTER nospam: > [email protected] FILTER spam: > [email protected] FILTER nospam: > Aha. Now we are talking right. All those 4 aliases are NOT valid DSPAM retraining aliases! Where in the documentation have you read that [email protected] is a valid retraining alias? In the whole DSPAM documentation you will only see that spam-[DSPAM user name] and nonspam-[DSPAM user name] are the only valid retraining aliases if you want to use ParseToHeaders. I know that in 3.8.0 this used to work but we fixed it in 3.9.0 to be exactly how it is documented. > >>>> With the version 3.8.0 > >>>> that system always worked, with the 3.9.0 not...but i don't know why.... > >>>> > >>> Okay. Without much going into detail about the transport... can you try > >>> to remove the "--user spam" from the two services and reload Postfix and > >>> try again? > >>> > >> If i removhe the --user spam, the result is the following: > >> > >> Jun 16 11:59:17 mail2 postfix/pipe[5113]: 338DBB1827F: > >> to=<[email protected]>, relay=spam, delay=0.2, > >> delays=0.13/0/0/0.07, dsn=5.3.0, status=bounced (Command died with > >> status 1: "/usr/sbin/dspam". Command output: Syntax: dspam > >> [--help|--version|[--client|--daemon] [--debug] > >> --mode=[toe|tum|teft|notrain|unlearn] --user [user1 user2 ... userN] > >> [--feature=[no,wh,tb=N]] [--class=[spam|innocent]] > >> [--source=[error|corpus|inoculation]] [--profile=[PROFILE]] > >> [--deliver=[spam,innocent,summary]] [--process|--classify] [--stdout] > >> [--mail-from=sender-address] [--rcpt-to recipient-address(es)] > >> [--signature=DSPAM-Signature] [passthru-arguments]] ) > >> > > Then replace "--user spam" with "--user ${sender}" > > > > > Just the same error, because it use my sender, but it can be different > because of aliases (like claudio.prono@atpss, the mailbox is > [email protected], this is just an alias), so dspam search for > claudio.prono@atpss, and it doesn't exist into the virtual_uids table of > dspam of mysql, the right search is for [email protected].... The only > way it works is using the ${recipient} without the spam- or no-spam.... > Okay. The built in alias retraining is not going to work for you. Not with your current setup. I suggest you take a look at the dspam_alias_retraining[1] script and maybe consider using DSPAM signatures with the UID enabled (see MySQLUIDInSignature). That makes retraining much easier then going with usernames. [1] http://dspam.git.sourceforge.net/git/gitweb.cgi?p=dspam/dspam;a=tree;f=contrib/dspam_alias_retraining;hb=HEAD -- Kind Regards from Switzerland, Stevan Bajić ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
