Re: [vchkpw] odd problem after OS upgrade (hey, Tom, Ken, jkitchen: around?)
On 6/22/2013 9:11 PM, Jeremy Kister wrote: hrm. i replaced vchkpw with checkpasswd. still broken. ends up the problem was actually stunnel/openssl. who knows what it was doing that was causing the tunneled program to behave incorrectly. for reference: on debian 6 (squeeze): sed s/squeeze/wheezy/g /etc/apt/sources.list /tmp/u.tmp mv /tmp/u.tmp /etc/apt/sources.list apt-get update apt-get upgrade apt-get dist-upgrade reboot gives you debian 7 (wheezy) this came both libssl 0.9.8, libssl 1.0.0, and stunnel 4.53 i ran 'apt-get autoremove libssl0.9.8', and then compiled/installed the latest stunnel (4.56), and the problem is no more. who knows. thanks for the replies. Greetings to all who are still here, -- Jeremy Kister http://jeremy.kister.net./ !DSPAM:51c68ea134131777546213!
Re: [vchkpw] odd problem after OS upgrade (hey, Tom, Ken, jkitchen: around?)
On 6/22/2013 10:26 AM, Eric Shubert wrote: Have you found where in the code the oops messages is being issued? yes. it complains only here: if (wait_pid(wstat,child) == -1) return err_child(); if (wait_crashed(wstat)) return err_child(); the wait_pid is when everything goes fubar. i'm not even sure it's a vpopmail problem, i suppose i may need a cross post on the qmail list. -- Jeremy Kister http://jeremy.kister.net./ !DSPAM:51c6407234139947713131!
Re: [vchkpw] odd problem after OS upgrade (hey, Tom, Ken, jkitchen: around?)
On 6/22/2013 8:26 PM, Jeremy Kister wrote: i'm not even sure it's a vpopmail problem, i suppose i may need a cross post on the qmail list. hrm. i replaced vchkpw with checkpasswd. still broken. -- Jeremy Kister http://jeremy.kister.net./ !DSPAM:51c64afa34132172261138!
Re: [vchkpw] odd problem after OS upgrade (hey, Tom, Ken, jkitchen: around?)
Did you recompile qmail and vpopmail after the OS upgrade? I'm wondering if it's something odd where the size of some data type changed from 32 to 64 bits after the OS upgrade, and one program is using the new size (perhaps because of a dynamically linked library) and the other is still using the old size. That's my best guess. I haven't been doing POSIX development in a long time, and even when I did I didn't wade too far into spawning children and exit codes. But it seems like the successful exit code isn't being interpreted correctly on qmail-smtpd. -Tom On Jun 22, 2013, at 6:11 PM, Jeremy Kister wrote: On 6/22/2013 8:26 PM, Jeremy Kister wrote: i'm not even sure it's a vpopmail problem, i suppose i may need a cross post on the qmail list. hrm. i replaced vchkpw with checkpasswd. still broken. -- Jeremy Kister http://jeremy.kister.net./ !DSPAM:51c68c1e34131709335937!
Re: [vchkpw] odd problem
Hi, Are you running fast_spamassassin in qmail-scanner? It doesn't take by default. Regards, Rick Paul Theodoropoulos wrote: i suppose this isn't strictly a vpopmail issue, but since my environment is vpopmail at the delivery end i just set up a gateway machine to handle my spamassassin processing. instead of the vpopmail server having all that added load on it, new incoming mail goes to a separate dedicated server running qmailscanner, and sending messages through spamassassin and clamav. that server processes the message, then forwards it on to the vpopmail server for final delivery. it's running fine, except for one thing: it won't tag the subject line with [SPAM] like they were tagged on the vpopmail server. it adds the scoring headers, but not the subject tag. i've verified that the /etc/mail/spamassassin/local.cf has that set correctly. any thoughts? anyone run into this before? Paul Theodoropoulos http://www.anastrophe.com http://folding.stanford.edu The Nicest Misanthrope on the Net
Re: [vchkpw] odd problem
Sigh, TAG, TAG. fast_spamassassin doesn't TAG by default on the subject line. Long day, typing sucks. Please excuse. Regards, Rick Paul Theodoropoulos wrote: i suppose this isn't strictly a vpopmail issue, but since my environment is vpopmail at the delivery end i just set up a gateway machine to handle my spamassassin processing. instead of the vpopmail server having all that added load on it, new incoming mail goes to a separate dedicated server running qmailscanner, and sending messages through spamassassin and clamav. that server processes the message, then forwards it on to the vpopmail server for final delivery. it's running fine, except for one thing: it won't tag the subject line with [SPAM] like they were tagged on the vpopmail server. it adds the scoring headers, but not the subject tag. i've verified that the /etc/mail/spamassassin/local.cf has that set correctly. any thoughts? anyone run into this before? Paul Theodoropoulos http://www.anastrophe.com http://folding.stanford.edu The Nicest Misanthrope on the Net
Re: [vchkpw] odd problem
no problem. i did rebuild qmailscanner, and it's working okay now. At 04:58 PM 06/19/2003, Rick Macdougall wrote: Sigh, TAG, TAG. fast_spamassassin doesn't TAG by default on the subject line. Long day, typing sucks. Please excuse. Regards, Rick Paul Theodoropoulos wrote: i suppose this isn't strictly a vpopmail issue, but since my environment is vpopmail at the delivery end i just set up a gateway machine to handle my spamassassin processing. instead of the vpopmail server having all that added load on it, new incoming mail goes to a separate dedicated server running qmailscanner, and sending messages through spamassassin and clamav. that server processes the message, then forwards it on to the vpopmail server for final delivery. it's running fine, except for one thing: it won't tag the subject line with [SPAM] like they were tagged on the vpopmail server. it adds the scoring headers, but not the subject tag. i've verified that the /etc/mail/spamassassin/local.cf has that set correctly. any thoughts? anyone run into this before? Paul Theodoropoulos http://www.anastrophe.com http://folding.stanford.edu The Nicest Misanthrope on the Net Paul Theodoropoulos http://www.anastrophe.com http://folding.stanford.edu The Nicest Misanthrope on the Net
