[toaster] migration from 4.9 to 5.4+mysql
Hi all, I want to migrate some domains from vpopmail 4.9.11 with cdb to latest 5.4 with mysql. On 5.2 versions, crypt passwords are valid on new installations with md5, but on mysql it seems to fail (I has replaced pw_passwd field with the encrypted password from vpasswd file and it fail to auth), how can I migrate passwords from 4.9 to mysql? I haven't passwords from my users so all are encrypted, any solution? Regards, Eduardo
Re: [toaster] simscan
On Sep 29, 2004, at 7:24 PM, Bill Shupp wrote: a.h.s. boy (lists) wrote: So it sounds like you can just set the simscan rejection level very high, like 30, and it will only reject the mail over that threshold. If SpamAssassin's own "threshold" setting can be different (like 7), then SA will still mark the mail as Spam, and simscan will allow it to pass through. That's how I read it. I plan to test simscan soon. Right now it's failing, and strace is not helping, but I have not tested it much yet. I'll report back when I have. I got a response from Ken Jones. Sounds like we have it right: With spamassassin enabled --enable-spam the email is passed through spamassassin with all it's associated headers. If the email is marked as spam then it is rejected. All other emails pass through with the spamassassin headers intact. With --enable-spam-hits=number then only email above this hit count is rejected. All other email is passed through including email marked as spam. The idea was to only reject really bad spam and let the user filter the rest. Cheers, spud. --- a.h.s. boy spud(at)nothingness.org"as yes is to if,love is to yes" http://www.nothingness.org/ ---
Re: [toaster] simscan
spud, Thanks for looking into this a little moreIt sounds like an awesome replacement to qmailscanner, and will certainly limit the queue filling up from bounces to invalid domains, etc. Peter a.h.s. boy (lists) wrote: On Sep 29, 2004, at 7:24 PM, Bill Shupp wrote: a.h.s. boy (lists) wrote: So it sounds like you can just set the simscan rejection level very high, like 30, and it will only reject the mail over that threshold. If SpamAssassin's own "threshold" setting can be different (like 7), then SA will still mark the mail as Spam, and simscan will allow it to pass through. That's how I read it. I plan to test simscan soon. Right now it's failing, and strace is not helping, but I have not tested it much yet. I'll report back when I have. I got a response from Ken Jones. Sounds like we have it right: With spamassassin enabled --enable-spam the email is passed through spamassassin with all it's associated headers. If the email is marked as spam then it is rejected. All other emails pass through with the spamassassin headers intact. With --enable-spam-hits=number then only email above this hit count is rejected. All other email is passed through including email marked as spam. The idea was to only reject really bad spam and let the user filter the rest. Cheers, spud. --- a.h.s. boy spud(at)nothingness.org"as yes is to if,love is to yes" http://www.nothingness.org/ ---
