Michael, I did the Bayes --backup from DB and --restore to SQL, and it
imported it all in as each specific user.  That is to say:

- there's a table, bayes_vars, that has a record for each user, and
assigns each user an id.
- the other three relevant tables (bayes_token, bayes_seen, and
bayes_expire) all key their entries to this id, and in my case, they all
keyed to the right people.

I'm not sure how you're doing the import, but that's my experience!

/jason

> On Wed, 8 Sep 2004 16:04:00 -0500
> Michael Parker <[EMAIL PROTECTED]> wrote:
>
>
>> To migrate AWL data you can use the convert_awl_dbm_to_sql script in
>> the tools directory.
>
> Looks like I have it working though I think I'm going to give up on
> importing my bayes db into MySQL and re-train it because it imports the
> entire database under one user - namely root.
>
> For sa-learn ham/spam there doesn't seem to be a way to actually set
> the user so I can do something like this with vmailmgr virtualhosts:
>
> sa-learn --spam /home/josh/Maildir/Spam [EMAIL PROTECTED] sa-learn
> --spam /home/anita/Maildir/Spam [EMAIL PROTECTED]
>
>
> I don't want Josh's Bayes SQL data to conflict with Anita's if I can
> avoid it.  It looks like sa-learn uses whatever username the person running
> sa-learn is logged in as, this won't work for virtual domains as multiple
> domains are "owned" by one user.  In a vmailmgr setup the user might be
> "domain1" and I'd want bayes/awl records to show up with
> usernames: [EMAIL PROTECTED], [EMAIL PROTECTED], etc.
>
>
> For AWL, is there a @GLOBAL username like with SQL userprefs where you
> can say this whitelist entry is global?
>
> This is looking pretty nifty, I'm hoping that I can work around these
> starting issues.
>
> Thanks!
>
>
> Josh
>
>


Reply via email to