Opened 15 years ago

Closed 15 years ago

#206 closed defect (worksforme) - razor2 report failed

Reported by: segr@… Owned by: rjl
Priority: normal Milestone: 1.0.0 RC6
Component: Perl scripts Version: 1.0.0 RC5
Severity: normal Keywords: razor2


I'm seeing this error coming back thru the cron when running the script. I'm at a loss as to why this is coming up. What should I be checking for? Or is this a bug with the script?

razor2 report failed: No such file or directory Razor2 report requires authentication at /usr/local/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/ line 148.
Learned mail item 2581 as SPAM and reported it
1 spam items processed (1 learned, 1 reported)
0 ham items processed (0 learned)

I'm running on a FreeBSD 5.3-RELEASE-p9 system with perl 5.8.6

Change History (1)

comment:1 Changed 15 years ago by anonymous

  • Resolution set to worksforme
  • Status changed from new to closed

This is not a problem with maia but a problem with your razor installation/configuration.

In order to report messages to razor, you need to register.

From the razor-admin man page:

       "razor-admin" is the Razor Agent that performs administrative func-
       tions, most notably registering (-register)

       "razor-admin" must have one of the following arguments:

           Registers a new identity, used for authenticating with Razor Nomi-
           nation Servers.  Identities are a user + password pair stored in
           "<razorhome>/identity-<user>".  The first time "razor-admin -regis-
           ter" exits successfully, a symlink "identity" is created to point
           to the active "identity-<user>" file. After that, new identities
           can be created, but in order to use them the symlink "identity"
           must be changed to point to them. In general, it should be called
           once from the command line. Exits 0 for success, exits 1 on failure
           with a human-readable output message.

           Both razor-report(1) and razor-revoke(1) require user authentica-
           tion to work, razor-check(1) does not. 

So...there are a few things you can do to resolve this.

  1. Turn off reporting
  2. run "razor-admin -register" as the user that amavisd-maia runs as.

Even though I'm not a member of the development team, I think writing to the mailing list would be a better option than filing bugs for things like this.

Note: See TracTickets for help on using tickets.