Re: [qmailtoaster] Re: Soft Rejections
Jake Vickers wrote: Qmailtoaster was originally started by Miguel Beccari years ago as an easy way to install Qmail. I've personally installed it about every way you can think of, and this is one of the faster ways to get a mail server up an running. Carrying on, Miguel kinda disappeared after a while, and Nick Hemmesch took the project over for the next 4 years or so. Since this is a hobby for those of us who develop things for Qmailtoaster the release cycle is sporadic at best. Nick became busy with work and home life and handed over the position to Erik Espinoza. Erik also has a real job and works on the project when he has spare time. Since it all ran on the server owned by whoever was maintaining it at the time, they were the only ones who could update the packages. At this time, Erik is the only one who can update the main site. Eric Shubes, myself, Justice London, Sam Clippinger, Lucian Cristian, Dan McCallister, Nate Davis, and the many who I've forgotten to mention (Sorry!) all contribute when/if we can. A couple of us have written updated packages and we have to submit them to Erik who will (if everything turns out okay during testing) update the main site when he has some time. I created the Qmailtoaster-Plus package along with Eric Shubes as a helper for those who run Qmailtoaster systems everyday. A lot of the tools bundled with it are the same tools that we (and those who have contributed to the package) use everyday. It's meant to try and make an admin's job easier. You'll find that myself and Eric write 85% of the scripts in this package ourselves, for ourselves. The package was meant as a way for us to easily share some of the tools we use. Jake, this Qmailtoaster's history seems more up-to-date than http://wiki.qmailtoaster.com/index.php/Main_Page#History can I update it, so the rest of us can know who is our founding father.. :) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Roxanne Sandesara wrote: On May 11, 2008, at 11:53 AM, Eric Shubert wrote: There are some other interesting options as well: -C : path for default config files Aha! I'm guessing that if you were to add -C /etc/mail/spamassassin to the exec command, that would solve your problem without having to use the /var/tmp/ directory. It doesn't explain though why your spamd is defaulting to /var/tmp first while other toasters are not. It does seem to be a simpler work-around though. OK. Made a copy of the run file for spamd as run.bak. Modified run to add -C /etc/mail/spamassassin. Saved that. Made a copy of it as run.new so that I could potentially switch back and forth, and have referents before and after the change. Stopped qmail. Deleted the /var/tmp/spamassassin-toaster-root directory and contents. (Since we want to see how this will work with the change in place, we don't want there to be any chance it is reading the 'stopgap' copy of config files I placed there to make things run yesterday.) Started qmail. Checked our spamd log. The errors I was getting before are no longer present. It is scanning successfully. The directory /var/tmp/spamassassin-toaster-root is not being re-created. Obviously, this doesn't yet answer the question of how or why the system was behaving as it was - and why uninstalling and re-installing the packages didn't correct that issue - but adding the -C option to the run file has at least corrected the problem so that the system is running 'as it should' from its default configuration files without errors. Thanks for the writeup Roxie. This gives a clear picture of what you did and the results. Is it possible that for some reason the vpopmail user doesn't have permissions to read /etc/mail/spamassassin and/or it's contents? # su - vpopmail -s /bin/sh # ls -l /etc/mail/spamassassin All of the files in this directory should be rw-r--r-- # su - vpopmail -s /bin/sh -sh-3.00$ ls -l /etc/mail/spamassassin total 52 -rw-r--r-- 1 root root 1299 May 10 16:34 init.pre -rw-r--r-- 1 root root 1299 May 8 19:02 init.pre.rpmnew -rw-r--r-- 1 root root 399 May 10 16:34 local.cf -rw-r--r-- 1 root root 399 May 8 19:02 local.cf.rpmnew -rw-r--r-- 1 root root 1703 Jan 8 16:41 local.cf.rpmsave -rw-r--r-- 1 root root 2397 May 10 16:34 v310.pre -rw-r--r-- 1 root root 2397 May 8 19:02 v310.pre.rpmnew -rw-r--r-- 1 root root 2443 May 7 15:27 v310.pre.rpmsave -rw-r--r-- 1 root root 1195 May 10 16:34 v312.pre -rw-r--r-- 1 root root 1195 May 8 19:02 v312.pre.rpmnew -rw-r--r-- 1 root root 2416 May 10 16:34 v320.pre -rw-r--r-- 1 root root 2416 May 8 19:02 v320.pre.rpmnew I realized after asking this that permissions were not a problem, as earlier to had run spamassassin successfully after a su - vpopmail. It's interesting (to me) to see both .rpmnew and .rpmsave files. This indicates that the (noreplace) option was added to the spec file some time in between. So. That being the case of our results, it seems clear to me that there is something 'hanging around' that is influencing both Spamassassin and spamd to go looking for that directory. Initiating spamd with the -C option is correcting for this. Which I am fine with, frankly, as I can read man pages well enough to continue replicating that correction in the future as needed. But it doesn't quite satiate my curiosity. Any thoughts as to where I should look to run down where this might be coming from? Or should I feed my curiosity some chocolate and tell it to be happy as-is? :) I found the bug: https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5904 I've applied the work around to the spec file and it appears to be working. EE will put it through his tests and if it passes will post it to the site. Isn't life great on the bleeding edge? ;) -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Roxanne Sandesara wrote:
Thanks, Eric.
Having provided what I just have, what's next? What piece of information
should I hunt down to get us to the next step in tracking?
As I said, when I ran 'spamassassin --lint -D' from the temporary bash
shell login as vpopmail, it does try to look in that directory, gives a
warning that it's inaccessible, and then tries and succeeds in finding
and processing the files in the default /etc/mail/spamassassin directory.
Should I try running 'spamassassin --lint -D' with the -x -u vopopmail
-s options, as specified in the spamd run file, while logged in
(otherwise) as my normal admin login, to see if its output and behaviors
differ?
Thanks again for all of the help and advice. I'll keep trying so long as
it takes. After all, I learn more with every step than I knew before.
Roxanne
I've run a few tests, and here's what I've observed:
.) The --rebuild option of rpmbuild does not actually install the binary
rpm. The man page must be referring to the %install phase of the build, in
which the toaster's spec does an install to the %{buildroot} environment,
which is subsequently used to create the binary rpm. I had read this out of
context yesterday (although the man page might read does a %prep, %compile
and %install to be clearer).
.) ran both
# sudo -u vpopmail -H spamassassin --lint -D
and
# su - vpopmail -s /bin/sh
# spamassassin --line -D
There was no reference to /var/tmp in either run, and no errors in the spamd
log after starting qmail. I did notice this though:
dbg: util: running in taint mode? yes
dbg: util: taint mode: deleting unsafe environment variables, resetting PATH
This shows that spamassassin is altering its environment, and might explain
a few things.
.) I ran a diff of the essential results:
# diff sa-lint.sudo sa-lint.su
After eliminating differences in hashes, which are to be expected, this is
what's left:
7d6
dbg: util: PATH included '/usr/kerberos/sbin', keeping
9d7
dbg: util: PATH included '/usr/local/sbin', keeping
11d8
dbg: util: PATH included '/sbin', keeping
13d9
dbg: util: PATH included '/usr/sbin', keeping
16,17c12
dbg: util: PATH included '/root/bin', which doesn't exist, dropping
dbg: util: final PATH set to:
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
---
dbg: util: final PATH set to:
/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin
151c146
This shows the result of the differing PATHs, in combination with running in
taint mode (noted just previously). In a nutshell, we see that sudo keeps
the present environment (in this case, root's), while su - takes on a
whole new environment. This is as we expected. It may be interesting to note
the difference in the resulting paths. While it doesn't exactly explain why
the configuration files are found differently, it does show how/why the
PATHs are different, and other environment variables will almost certainly
be different too (they would only be the same coincidentally).
So we're still in the same boat, but we've seen that spamassassin can behave
differently depending on how and from which account it's invoked. We've also
missed one other fine detail. The toaster runs spamd, not spamassassin.
These are two entirely different programs. So now we're back to the question
of, how does *spamd* find its configuration files.
Let's remind ourself first how we're invoking spamd:
exec /usr/bin/spamd -x -u vpopmail -s stderr 21
A good place to look is always the man page. From that we see that:
-x : Disable user config files
-u : run as vpmail
-s : log to stderr
There are some other interesting options as well:
-C : path for default config files
Aha! I'm guessing that if you were to add -C /etc/mail/spamassassin to the
exec command, that would solve your problem without having to use the
/var/tmp/ directory. It doesn't explain though why your spamd is defaulting
to /var/tmp first while other toasters are not. It does seem to be a simpler
work-around though.
Is it possible that for some reason the vpopmail user doesn't have
permissions to read /etc/mail/spamassassin and/or it's contents?
# su - vpopmail -s /bin/sh
# ls -l /etc/mail/spamassassin
All of the files in this directory should be rw-r--r--
Let us know what you find with -C and permissions.
--
-Eric 'shubes'
-
QmailToaster hosted by: VR Hosted http://www.vr.org
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
On May 11, 2008, at 11:53 AM, Eric Shubert wrote: There are some other interesting options as well: -C : path for default config files Aha! I'm guessing that if you were to add -C /etc/mail/ spamassassin to the exec command, that would solve your problem without having to use the /var/tmp/ directory. It doesn't explain though why your spamd is defaulting to /var/tmp first while other toasters are not. It does seem to be a simpler work-around though. OK. Made a copy of the run file for spamd as run.bak. Modified run to add -C /etc/mail/spamassassin. Saved that. Made a copy of it as run.new so that I could potentially switch back and forth, and have referents before and after the change. Stopped qmail. Deleted the /var/tmp/spamassassin-toaster-root directory and contents. (Since we want to see how this will work with the change in place, we don't want there to be any chance it is reading the 'stopgap' copy of config files I placed there to make things run yesterday.) Started qmail. Checked our spamd log. The errors I was getting before are no longer present. It is scanning successfully. The directory / var/tmp/spamassassin-toaster-root is not being re-created. Obviously, this doesn't yet answer the question of how or why the system was behaving as it was - and why uninstalling and re- installing the packages didn't correct that issue - but adding the -C option to the run file has at least corrected the problem so that the system is running 'as it should' from its default configuration files without errors. Is it possible that for some reason the vpopmail user doesn't have permissions to read /etc/mail/spamassassin and/or it's contents? # su - vpopmail -s /bin/sh # ls -l /etc/mail/spamassassin All of the files in this directory should be rw-r--r-- # su - vpopmail -s /bin/sh -sh-3.00$ ls -l /etc/mail/spamassassin total 52 -rw-r--r-- 1 root root 1299 May 10 16:34 init.pre -rw-r--r-- 1 root root 1299 May 8 19:02 init.pre.rpmnew -rw-r--r-- 1 root root 399 May 10 16:34 local.cf -rw-r--r-- 1 root root 399 May 8 19:02 local.cf.rpmnew -rw-r--r-- 1 root root 1703 Jan 8 16:41 local.cf.rpmsave -rw-r--r-- 1 root root 2397 May 10 16:34 v310.pre -rw-r--r-- 1 root root 2397 May 8 19:02 v310.pre.rpmnew -rw-r--r-- 1 root root 2443 May 7 15:27 v310.pre.rpmsave -rw-r--r-- 1 root root 1195 May 10 16:34 v312.pre -rw-r--r-- 1 root root 1195 May 8 19:02 v312.pre.rpmnew -rw-r--r-- 1 root root 2416 May 10 16:34 v320.pre -rw-r--r-- 1 root root 2416 May 8 19:02 v320.pre.rpmnew Let us know what you find with -C and permissions. -- -Eric 'shubes' So. That being the case of our results, it seems clear to me that there is something 'hanging around' that is influencing both Spamassassin and spamd to go looking for that directory. Initiating spamd with the -C option is correcting for this. Which I am fine with, frankly, as I can read man pages well enough to continue replicating that correction in the future as needed. But it doesn't quite satiate my curiosity. Any thoughts as to where I should look to run down where this might be coming from? Or should I feed my curiosity some chocolate and tell it to be happy as-is? :) Roxanne (And I hope everyone remembered to tell their mothers Happy Mothers Day. I know I did.) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
An update for everyone who may have been following my difficulties with spamassassin and sa-update. I took the time this afternoon to do the rebuild I'd promised myself I would do. I performed the following steps: qmailctl stop rpm -e --nodeps simscan-toaster-1.3.1-1.3.6 rpm -e --nodeps ripmime-toaster-1.4.0.6-1.3.3 rpm -e --nodeps clamav-toaster-0.93-1.3.18 rpm -e --nodeps spamassassin-toaster-3.2.4-1.3.15 rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/spamassassin- toaster-3.2.4-1.3.15.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/spamassassin- toaster-3.2.4-1.3.15.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/clamav- toaster-0.93-1.3.18.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/clamav-toaster-0.93-1.3.18.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/ripmime- toaster-1.4.0.6-1.3.3.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/ripmime- toaster-1.4.0.6-1.3.3.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/simscan- toaster-1.3.1-1.3.6.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/simscan-toaster-1.3.1-1.3.6.i386.rpm I then su'ed to the shell of vpopmail and ran the --lint -D process to see what I could see. It still looked, first, for configuration files in that dratted /var/ tmp/spamassassin-toaster-root/etc/mail/spamassassin When it found none, it then looked in /etc/mail/spamassassin and loaded the files there. So it succeeded in the test. So I started up qmail. Then I checked the log ... and it was giving me that 'unable to find check_mail' error. Which I've seen often enough in the last week to know what it was and how to make it go away. So I copied my *.pre files from /etc/mail/spamassassin to /var/tmp/spamassassin-toaster- root/etc/mail/spamassassin and then checked the log again, and it is now succeeding. But this means that even having successfully cleaned out all (supposedly) remnants of the old system, and then re-installed, somehow it is still maintaining the call for that directory. I'm up and running. But the underlying problem still exists. I'm wondering what I can do to help troubleshoot this. Would it, for instance, be at all useful to see a script recording of the entire process of each build and installation? Are there some things that I should go hunting for after the uninstallation of packages, to be sure that the problem is cleared out before installing again? Looking for advice and suggestions, Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
The /var/tmp/package-name-root directory is used by the rpmbuild process, and should not exist after a successful build. I don't think the fact that spamassassin looks there for the configuration is a problem as long as it ultimately finds it where it is, in /etc/mail/spamassassin. You su'd to Roxanne Sandesara wrote: An update for everyone who may have been following my difficulties with spamassassin and sa-update. I took the time this afternoon to do the rebuild I'd promised myself I would do. I performed the following steps: qmailctl stop rpm -e --nodeps simscan-toaster-1.3.1-1.3.6 rpm -e --nodeps ripmime-toaster-1.4.0.6-1.3.3 rpm -e --nodeps clamav-toaster-0.93-1.3.18 rpm -e --nodeps spamassassin-toaster-3.2.4-1.3.15 Using the version number(s) is not necessary with most installed packages (exception being those which can have multiple versions installed concurrently such as the kernel). You could have simply run: # rpm -e --nodeps simscan-toaster ripmime-toaster clamav-toaster spamassassin-toaster instead. It shouldn't have hurt to do it the way you did though (ttbomk), as long as these were indeed the versions which were installed. rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/spamassassin-toaster-3.2.4-1.3.15.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/spamassassin-toaster-3.2.4-1.3.15.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/clamav-toaster-0.93-1.3.18.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/clamav-toaster-0.93-1.3.18.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/ripmime-toaster-1.4.0.6-1.3.3.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/ripmime-toaster-1.4.0.6-1.3.3.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/simscan-toaster-1.3.1-1.3.6.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/simscan-toaster-1.3.1-1.3.6.i386.rpm These look ok. Personally, I would have used the -ivh options instead of -Uvh, but -Uvh will install them if they don't exist. -ivh would have failed if they already exist, which I would have wanted it to do, to be sure that they had been removed. Not a big deal. On 2nd look though, I checked the man page about --rebuild option, which says: rpmbuild --rebuild|--recompile SOURCEPKG ... When invoked this way, rpmbuild installs the named source package, and does a prep, compile and install. In addition, --rebuild builds a new binary package. When the build has completed, the build directory is removed (as in --clean) and the the sources and spec file for the package are removed. This seems to indicate that the execution of rpm after the rpmbuild is entirely unnecessary, as the rpmbuild does the install as well as building the binary. Hmmm. I obviously never noticed this before. That would explain why the -U instead of -i is necessary. I'll have to do some testing. The question that this brings to mind is, what happens when a package is updated over itself? I don't know off hand, but imagine that it might cause problems with some configuration files (rpmsave files would be replaced twice and the original lost). Other than that, I don't see a problem off hand, but we should keep this in mind (and probably modify the install and newmodel scripts appropriately). I then su'ed to the shell of vpopmail and ran the --lint -D process to see what I could see. You su'ed to vpopmail? That shouldn't be possible on a stock installation, as the vpopmail user should have /sbin/nologin as the login script. sudo'ing would be safer, as that's closer to the way that spamd is run by supervise. I don't know of a reason why su'ing to vpopmail wouldn't work though, although you need to be careful to usually use the '-' flag when using su. Omitting '-' can produce seemingly mysterious results because the target user's environment isn't set up completely without it (and vpopmail doesn't necessarily have one). It still looked, first, for configuration files in that dratted /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin The /var/tmp/spamassassin-toaster-root is used by the rpmbuild process. It should not exist after the build is done. I wouldn't be concerned with this as long as SA finds the appropriate config files, as apparently it subsequently does. When it found none, it then looked in /etc/mail/spamassassin and loaded the files there. So it succeeded in the test. So I started up qmail. Then I checked the log ... and it was giving me that 'unable to find check_mail' error. Which I've seen often enough in the last week to know what it was and how to make it go away. So I copied my *.pre files from /etc/mail/spamassassin to /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin and then checked the log again, and it is now succeeding. You realize that this is not the correct fix though, right? It appears that the environment that spamd runs in (as a result of the -u option, as specified in the /var/qmail/supervise/spamd/run file) is different than what you're
Re: [qmailtoaster] Re: Soft Rejections
On May 10, 2008, at 8:28 PM, Eric Shubert wrote: The /var/tmp/package-name-root directory is used by the rpmbuild process, and should not exist after a successful build. I don't think the fact that spamassassin looks there for the configuration is a problem as long as it ultimately finds it where it is, in /etc/mail/spamassassin. You su'd to Roxanne Sandesara wrote: An update for everyone who may have been following my difficulties with spamassassin and sa-update. I took the time this afternoon to do the rebuild I'd promised myself I would do. I performed the following steps: qmailctl stop rpm -e --nodeps simscan-toaster-1.3.1-1.3.6 rpm -e --nodeps ripmime-toaster-1.4.0.6-1.3.3 rpm -e --nodeps clamav-toaster-0.93-1.3.18 rpm -e --nodeps spamassassin-toaster-3.2.4-1.3.15 Using the version number(s) is not necessary with most installed packages (exception being those which can have multiple versions installed concurrently such as the kernel). You could have simply run: # rpm -e --nodeps simscan-toaster ripmime-toaster clamav-toaster spamassassin-toaster instead. It shouldn't have hurt to do it the way you did though (ttbomk), as long as these were indeed the versions which were installed. I did rpm -qa | grep toaster to get the numbers, and uninstalled what I found there. They were correctly uninstalled. rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/spamassassin-toaster-3.2.4-1.3.15.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/spamassassin-toaster-3.2.4-1.3.15.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/clamav-toaster-0.93-1.3.18.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/clamav- toaster-0.93-1.3.18.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/ripmime-toaster-1.4.0.6-1.3.3.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/ripmime- toaster-1.4.0.6-1.3.3.i386.rpm rpmbuild --rebuild --with cnt40 /usr/src/redhat/SRPMS/simscan-toaster-1.3.1-1.3.6.src.rpm rpm -Uvh /usr/src/redhat/RPMS/i386/simscan- toaster-1.3.1-1.3.6.i386.rpm These look ok. Personally, I would have used the -ivh options instead of -Uvh, but -Uvh will install them if they don't exist. -ivh would have failed if they already exist, which I would have wanted it to do, to be sure that they had been removed. Not a big deal. On 2nd look though, I checked the man page about --rebuild option, which says: rpmbuild --rebuild|--recompile SOURCEPKG ... When invoked this way, rpmbuild installs the named source package, and does a prep, compile and install. In addition, --rebuild builds a new binary package. When the build has completed, the build directory is removed (as in --clean) and the the sources and spec file for the package are removed. This seems to indicate that the execution of rpm after the rpmbuild is entirely unnecessary, as the rpmbuild does the install as well as building the binary. Hmmm. I obviously never noticed this before. That would explain why the -U instead of -i is necessary. I'll have to do some testing. The question that this brings to mind is, what happens when a package is updated over itself? I don't know off hand, but imagine that it might cause problems with some configuration files (rpmsave files would be replaced twice and the original lost). Other than that, I don't see a problem off hand, but we should keep this in mind (and probably modify the install and newmodel scripts appropriately). I can obviously only speak to my own experience. But when I do an rpmbuild --rebuild, the binary RPM is created. It is not subsequently installed until I do the rpm command independently (the next line). I'll gladly run the intermediary commands next time, and record things in an script so that we can be 100% sure. I then su'ed to the shell of vpopmail and ran the --lint -D process to see what I could see. You su'ed to vpopmail? That shouldn't be possible on a stock installation, as the vpopmail user should have /sbin/nologin as the login script. sudo'ing would be safer, as that's closer to the way that spamd is run by supervise. I don't know of a reason why su'ing to vpopmail wouldn't work though, although you need to be careful to usually use the '-' flag when using su. Omitting '-' can produce seemingly mysterious results because the target user's environment isn't set up completely without it (and vpopmail doesn't necessarily have one). Specifically, the command I used - suggested by Jaime earlier in this thread - was: su - vpopmail -s /bin/bash Which doesn't ask me for a password, and takes care of giving me a shell to work with despite the fact that vpopmail isn't allowed to login normally. It still looked, first, for configuration files in that dratted /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin The /var/tmp/spamassassin-toaster-root is used by the rpmbuild process. It should not exist after the build is done. I wouldn't be
Re: [qmailtoaster] Re: Soft Rejections
So, having run find / -type f | xargs grep -i spamassassin-toaster- root, I find the following: /usr/bin/sa-compile:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-learn:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin'; # substituted at 'make' time /usr/bin/sa-update:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-update: 'LOCAL_RULES_DIR' = '/var/tmp/ spamassassin-toaster-root/etc/mail/spamassassin', /usr/bin/sa-update:/var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin/sa-update-keys Binary file /usr/bin/spamc matches /usr/bin/spamd:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster- root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin So this clearly came into place when I added sa-update in place of RulesDuJour this past weekend. I don't know if that's normal or not, but I'm assuming not, since no one else recognized that path or considered it valid except during build/compile/install. Chkrootkit found nothing. My guess would be, at this point, I open sa-compile, sa-learn, sao- update, etc., in vi, find those instances of that directory and redirect them to where they should be? Which would be /etc/mail/ spamassassin ? Roxanne On May 7, 2008, at 8:39 PM, James Pratt wrote: With all due respect, I see *nothing* that indicates *any* sort of dns issue here. The problem is that the Spamassassin installation is trying to create temp files in a very non-standard directory, as Eric said in a prior post. I would guess the build is just plain messed up - what does rpm -ql Spamassassin-toaster say? Inspect the rebuild output closely after. Do not rebuild it as the root user. If I were you, I would re-rpmbuild, and also run chkrootkit, and/or rkhunter... many people (still!) compile things as root. That is a very bad thing, qmail or no. :( Regards, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 8:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su - into vpopmail's shell to run the spamassassin -- lint -D tests. Roxanne On May 7, 2008, at 7:29 PM, Eric Shubert wrote: Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/ PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7
RE: [qmailtoaster] Re: Soft Rejections
-Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 11:24 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections So, having run find / -type f | xargs grep -i spamassassin-toaster- root, I find the following: /usr/bin/sa-compile:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-learn:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin'; # substituted at 'make' time /usr/bin/sa-update:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-update: 'LOCAL_RULES_DIR' = '/var/tmp/ spamassassin-toaster-root/etc/mail/spamassassin', /usr/bin/sa-update:/var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin/sa-update-keys Binary file /usr/bin/spamc matches /usr/bin/spamd:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster- root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin So this clearly came into place when I added sa-update in place of RulesDuJour this past weekend. I don't know if that's normal or not, but I'm assuming not, since no one else recognized that path or considered it valid except during build/compile/install. Chkrootkit found nothing. My guess would be, at this point, I open sa-compile, sa-learn, sao- update, etc., in vi, find those instances of that directory and redirect them to where they should be? Which would be /etc/mail/ spamassassin ? No , you will just end up pulling your hair out , especially if you have to try and guess paths .. rebuild the entire sa package using rpmbuild ... The sa-learn, sa-compile, and sa-update files are created upon SA installation, so I can't see how just setting up sa-update would rebuild everything like that unless you used some type of automated sa-update configurator or something... (?) The spamassassin executable (perl script) should look something like: $ strings /usr/bin/spamassassin | grep LOCAL my $LOCAL_RULES_DIR = '/etc/mail/spamassassin';# substituted at 'make' time my $LOCAL_STATE_DIR = '/var/lib/spamassassin';# substituted at 'make' time LOCAL_RULES_DIR = $LOCAL_RULES_DIR, LOCAL_STATE_DIR = $LOCAL_STATE_DIR, (This is from a sendmail box, so the paths may be different. I can't get into my toaster server right now. :\ Cheers, jp Roxanne On May 7, 2008, at 8:39 PM, James Pratt wrote: With all due respect, I see *nothing* that indicates *any* sort of dns issue here. The problem is that the Spamassassin installation is trying to create temp files in a very non-standard directory, as Eric said in a prior post. I would guess the build is just plain messed up - what does rpm -ql Spamassassin-toaster say? Inspect the rebuild output closely after. Do not rebuild it as the root user. If I were you, I would re-rpmbuild, and also run chkrootkit, and/or rkhunter... many people (still!) compile things as root. That is a very bad thing, qmail or no. :( Regards, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 8:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su - into vpopmail's shell to run the spamassassin -- lint -D tests. Roxanne On May 7, 2008, at 7:29 PM, Eric Shubert wrote: Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne
Re: [qmailtoaster] Re: Soft Rejections
Roxanne Sandesara wrote: So, having run find / -type f | xargs grep -i spamassassin-toaster-root, I find the following: /usr/bin/sa-compile:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-learn:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin'; # substituted at 'make' time /usr/bin/sa-update:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-update: 'LOCAL_RULES_DIR' = '/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin', /usr/bin/sa-update: /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/sa-update-keys Binary file /usr/bin/spamc matches /usr/bin/spamd:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/mail/spamassassin So this clearly came into place when I added sa-update in place of RulesDuJour this past weekend. I don't know if that's normal or not, but I'm assuming not, since no one else recognized that path or considered it valid except during build/compile/install. It's not so clear to me that sa-update caused your problem, but I do think it's possible, and perhaps likely given that you added it last weekend. I don't run sa-update or RDJ. How did you go about adding sa-update this past weekend? Chkrootkit found nothing. That's always good. ;) My guess would be, at this point, I open sa-compile, sa-learn, sao-update, etc., in vi, find those instances of that directory and redirect them to where they should be? Which would be /etc/mail/spamassassin ? I wouldn't go there. Roxanne On May 7, 2008, at 8:39 PM, James Pratt wrote: With all due respect, I see *nothing* that indicates *any* sort of dns issue here. The problem is that the Spamassassin installation is trying to create temp files in a very non-standard directory, as Eric said in a prior post. I would guess the build is just plain messed up - what does rpm -ql Spamassassin-toaster say? Inspect the rebuild output closely after. Do not rebuild it as the root user. If I were you, I would re-rpmbuild, and also run chkrootkit, and/or rkhunter... many people (still!) compile things as root. That is a very bad thing, qmail or no. :( Regards, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 8:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su - into vpopmail's shell to run the spamassassin -- lint -D tests. Roxanne On May 7, 2008, at 7:29 PM, Eric Shubert wrote: Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further
RE: [qmailtoaster] Re: Soft Rejections
Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ Cheers, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 11:55 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections I used the qtp script qtp-sa-update, so yes, I believe that would qualify as 'an automated sa-update configurator'. I'll have to wait until late tonight or some time this weekend to attempt the rebuild and re-install. On May 8, 2008, at 11:48 AM, James Pratt wrote: -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 11:24 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections So, having run find / -type f | xargs grep -i spamassassin- toaster- root, I find the following: /usr/bin/sa-compile:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-learn:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin'; # substituted at 'make' time /usr/bin/sa-update:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/sa-update: 'LOCAL_RULES_DIR' = '/var/tmp/ spamassassin-toaster-root/etc/mail/spamassassin', /usr/bin/sa-update:/var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin/sa-update-keys Binary file /usr/bin/spamc matches /usr/bin/spamd:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin-toaster- root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:my $LOCAL_RULES_DIR = '/var/tmp/spamassassin- toaster-root/etc/mail/spamassassin';# substituted at 'make' time /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin /usr/bin/spamassassin:=item /var/tmp/spamassassin-toaster-root/etc/ mail/spamassassin So this clearly came into place when I added sa-update in place of RulesDuJour this past weekend. I don't know if that's normal or not, but I'm assuming not, since no one else recognized that path or considered it valid except during build/compile/install. Chkrootkit found nothing. My guess would be, at this point, I open sa-compile, sa-learn, sao- update, etc., in vi, find those instances of that directory and redirect them to where they should be? Which would be /etc/mail/ spamassassin ? No , you will just end up pulling your hair out , especially if you have to try and guess paths .. rebuild the entire sa package using rpmbuild ... The sa-learn, sa-compile, and sa-update files are created upon SA installation, so I can't see how just setting up sa-update would rebuild everything like that unless you used some type of automated sa-update configurator or something... (?) The spamassassin executable (perl script) should look something like: $ strings /usr/bin/spamassassin | grep LOCAL my $LOCAL_RULES_DIR = '/etc/mail/spamassassin';# substituted at 'make' time my $LOCAL_STATE_DIR = '/var/lib/spamassassin';# substituted at 'make' time LOCAL_RULES_DIR = $LOCAL_RULES_DIR, LOCAL_STATE_DIR = $LOCAL_STATE_DIR, (This is from a sendmail box, so the paths may be different. I can't get into my toaster server right now. :\ Cheers, jp Roxanne On May 7, 2008, at 8:39 PM, James Pratt wrote: With all due respect, I see *nothing* that indicates *any* sort of dns issue here. The problem is that the Spamassassin installation is trying to create temp files in a very non-standard directory, as Eric said in a prior post. I would guess the build is just plain messed up - what does rpm -ql Spamassassin-toaster say? Inspect the rebuild output closely after. Do not rebuild it as the root user. If I were you, I would re-rpmbuild, and also run chkrootkit, and/or rkhunter... many people (still!) compile things as root. That is a very bad thing, qmail or no. :( Regards, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 8:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su
Re: [qmailtoaster] Re: Soft Rejections
James Pratt wrote: Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ I'm just jumping in on the tail of this, but you can try and give me the smack down if you want. Or you can quit using the software I write. qtp-sa-update does not touch the SA executables at all. I don't even know where you would get the idea if you even looked at the script. I think if you do your due diligence you'll see the script does almost exactly what the 2 links you provided do almost step by step. Looking at the error, it looks like a remnant left over from when the spamassassin-toaster package spec file was broken or at least acting weird. I'd suggest rebuilding the package (spamassassin-toaster). It looks like you got one of the many bugs reported on the list by this latest version or revert to an older version. (to recap: the qtp-sa-update script removed the RDJ rules if they were there from an older version of QTP, then installs the Apache/Spamassassin channel, then installs the OpenProtect channel. It doesn't touch the executable at all) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
To be clear, I was not blaming Jake, or his utilities. I've had great luck with everything Jake has ever done or offered. I was merely answering the question of how it was I'd installed sa-update. I'm also not really sure that the executables themselves /have/ been messed up. It's possible. They might be. Or they might be pulling in data from some other included file that is incorrect. I just can't / find/ that other file. I also can't quite fathom how, if the executables had been messed up during the installation - which also happened this prior weekend - how things managed to run just fine until yesterday afternoon. My suspicion would have been that some run of some cron job or another ended up altering some file or another to put in this incorrect path and create the issue. But I really have no clue. I'm fishing in the dark. Nevertheless. I will try, as stated, to DL the latest SA src.rpm, rebuild, and re-install when I get a chance, either late tonight or this coming weekend. I do appreciate all of the help I received trying to narrow down what was going on and how to get things back up and running. Roxanne On May 8, 2008, at 12:49 PM, Jake Vickers wrote: James Pratt wrote: Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ I'm just jumping in on the tail of this, but you can try and give me the smack down if you want. Or you can quit using the software I write. qtp-sa-update does not touch the SA executables at all. I don't even know where you would get the idea if you even looked at the script. I think if you do your due diligence you'll see the script does almost exactly what the 2 links you provided do almost step by step. Looking at the error, it looks like a remnant left over from when the spamassassin-toaster package spec file was broken or at least acting weird. I'd suggest rebuilding the package (spamassassin-toaster). It looks like you got one of the many bugs reported on the list by this latest version or revert to an older version. (to recap: the qtp-sa-update script removed the RDJ rules if they were there from an older version of QTP, then installs the Apache/ Spamassassin channel, then installs the OpenProtect channel. It doesn't touch the executable at all) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Eric, Is there an easy way to go about removing various QTP packages? Such as sa-update, newmodel etc? Have them all installed at the minute with no problems, just wanting the option! Cheers, James On 8 May 2008, at 17:49, Jake Vickers wrote: James Pratt wrote: Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ I'm just jumping in on the tail of this, but you can try and give me the smack down if you want. Or you can quit using the software I write. qtp-sa-update does not touch the SA executables at all. I don't even know where you would get the idea if you even looked at the script. I think if you do your due diligence you'll see the script does almost exactly what the 2 links you provided do almost step by step. Looking at the error, it looks like a remnant left over from when the spamassassin-toaster package spec file was broken or at least acting weird. I'd suggest rebuilding the package (spamassassin-toaster). It looks like you got one of the many bugs reported on the list by this latest version or revert to an older version. (to recap: the qtp-sa-update script removed the RDJ rules if they were there from an older version of QTP, then installs the Apache/ Spamassassin channel, then installs the OpenProtect channel. It doesn't touch the executable at all) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Roxanne Sandesara wrote: To be clear, I was not blaming Jake, or his utilities. I've had great luck with everything Jake has ever done or offered. I was merely answering the question of how it was I'd installed sa-update. I'm also not really sure that the executables themselves /have/ been messed up. It's possible. They might be. Or they might be pulling in data from some other included file that is incorrect. I just can't /find/ that other file. grin I know that. Just tossing some back. The qtp-sa-update basically does exactly what the links James provided do. It doesn't touch the spamassassin executables in any shape or form, other than to run sa-update. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
James Palmer wrote: Eric, Is there an easy way to go about removing various QTP packages? Such as sa-update, newmodel etc? Have them all installed at the minute with no problems, just wanting the option! rpm -e qmailtoaster-plus - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Does that actually remove all the installed packages though, or just the QTP installers? I.e. remove spamdyke, the new channel and cron jobs added by sa-update and the yum repo added by newmodel? Cheers, James On 8 May 2008, at 18:14, Jake Vickers wrote: James Palmer wrote: Eric, Is there an easy way to go about removing various QTP packages? Such as sa-update, newmodel etc? Have them all installed at the minute with no problems, just wanting the option! rpm -e qmailtoaster-plus - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
QTP is a set of tools which provide easy ways to do things that an administrator might typically do. There are no QTP packages per se, only qmailtoaster-plus itself. As far as undoing what a qtp tool has done, that would need to be addressed on a case by case basis: .) for spamdyke, that has been covered on the list and is documented on the wiki. .) for sa-update, I don't know off hand. .) there is no yum repo added by newmodel. I hope this clears things up a bit. James Palmer wrote: Does that actually remove all the installed packages though, or just the QTP installers? I.e. remove spamdyke, the new channel and cron jobs added by sa-update and the yum repo added by newmodel? Cheers, James On 8 May 2008, at 18:14, Jake Vickers wrote: James Palmer wrote: Eric, Is there an easy way to go about removing various QTP packages? Such as sa-update, newmodel etc? Have them all installed at the minute with no problems, just wanting the option! rpm -e qmailtoaster-plus - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
No probs, was just curious! James On 8 May 2008, at 20:21, Eric Shubert wrote: QTP is a set of tools which provide easy ways to do things that an administrator might typically do. There are no QTP packages per se, only qmailtoaster-plus itself. As far as undoing what a qtp tool has done, that would need to be addressed on a case by case basis: .) for spamdyke, that has been covered on the list and is documented on the wiki. .) for sa-update, I don't know off hand. .) there is no yum repo added by newmodel. I hope this clears things up a bit. James Palmer wrote: Does that actually remove all the installed packages though, or just the QTP installers? I.e. remove spamdyke, the new channel and cron jobs added by sa-update and the yum repo added by newmodel? Cheers, James On 8 May 2008, at 18:14, Jake Vickers wrote: James Palmer wrote: Eric, Is there an easy way to go about removing various QTP packages? Such as sa-update, newmodel etc? Have them all installed at the minute with no problems, just wanting the option! rpm -e qmailtoaster-plus - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
James Palmer wrote: Does that actually remove all the installed packages though, or just the QTP installers? I.e. remove spamdyke, the new channel and cron jobs added by sa-update and the yum repo added by newmodel? That removes the qmailtoaster-plus package. It does not undo any changes/upgrade/whatever you have done by using the scripts it contains. To remove sa-update changes I would imagine there would be an easy way to remove the channels but that will be for you to explore. Here's SA's page on sa-learn and channels: http://wiki.apache.org/spamassassin/RuleUpdates#head-612bf6b3bb5d01d608f59869f29630fbf46476fa Then just delete the cron job (should be blatantly obvious, just like it doesn't modify executables) from /etc/cron.daily. Don't know what you're talking about as far as the repo. You can remove the qmailtoaster-plus repo by just removing the RPM. This is all basic stuff. - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
I do have a question. When the last Spamassassin-toaster package came out, there were problems. This was then followed by a thread that included a package Eric put together that was version 3.2.4 release 1.3.14. I have that package. But the QMT website is only showing release 1.3.13. Should I do a rebuild with release 1.3.14's src.rpm? Or should I DL release 1.3.13's src.rpm and build that instead? Roxanne On May 8, 2008, at 12:59 PM, Roxanne Sandesara wrote: To be clear, I was not blaming Jake, or his utilities. I've had great luck with everything Jake has ever done or offered. I was merely answering the question of how it was I'd installed sa-update. I'm also not really sure that the executables themselves /have/ been messed up. It's possible. They might be. Or they might be pulling in data from some other included file that is incorrect. I just can't /find/ that other file. I also can't quite fathom how, if the executables had been messed up during the installation - which also happened this prior weekend - how things managed to run just fine until yesterday afternoon. My suspicion would have been that some run of some cron job or another ended up altering some file or another to put in this incorrect path and create the issue. But I really have no clue. I'm fishing in the dark. Nevertheless. I will try, as stated, to DL the latest SA src.rpm, rebuild, and re-install when I get a chance, either late tonight or this coming weekend. I do appreciate all of the help I received trying to narrow down what was going on and how to get things back up and running. Roxanne On May 8, 2008, at 12:49 PM, Jake Vickers wrote: James Pratt wrote: Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ I'm just jumping in on the tail of this, but you can try and give me the smack down if you want. Or you can quit using the software I write. qtp-sa-update does not touch the SA executables at all. I don't even know where you would get the idea if you even looked at the script. I think if you do your due diligence you'll see the script does almost exactly what the 2 links you provided do almost step by step. Looking at the error, it looks like a remnant left over from when the spamassassin-toaster package spec file was broken or at least acting weird. I'd suggest rebuilding the package (spamassassin-toaster). It looks like you got one of the many bugs reported on the list by this latest version or revert to an older version. (to recap: the qtp-sa-update script removed the RDJ rules if they were there from an older version of QTP, then installs the Apache/ Spamassassin channel, then installs the OpenProtect channel. It doesn't touch the executable at all) - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Use 1.3.14. It contains a bug fix in the spec file (otherwise they're the same). The bug it fixes is: install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/local.cf.bz2': No such file or directory Roxanne Sandesara wrote: I do have a question. When the last Spamassassin-toaster package came out, there were problems. This was then followed by a thread that included a package Eric put together that was version 3.2.4 release 1.3.14. I have that package. But the QMT website is only showing release 1.3.13. Should I do a rebuild with release 1.3.14's src.rpm? Or should I DL release 1.3.13's src.rpm and build that instead? Roxanne On May 8, 2008, at 12:59 PM, Roxanne Sandesara wrote: To be clear, I was not blaming Jake, or his utilities. I've had great luck with everything Jake has ever done or offered. I was merely answering the question of how it was I'd installed sa-update. I'm also not really sure that the executables themselves /have/ been messed up. It's possible. They might be. Or they might be pulling in data from some other included file that is incorrect. I just can't /find/ that other file. I also can't quite fathom how, if the executables had been messed up during the installation - which also happened this prior weekend - how things managed to run just fine until yesterday afternoon. My suspicion would have been that some run of some cron job or another ended up altering some file or another to put in this incorrect path and create the issue. But I really have no clue. I'm fishing in the dark. Nevertheless. I will try, as stated, to DL the latest SA src.rpm, rebuild, and re-install when I get a chance, either late tonight or this coming weekend. I do appreciate all of the help I received trying to narrow down what was going on and how to get things back up and running. Roxanne On May 8, 2008, at 12:49 PM, Jake Vickers wrote: James Pratt wrote: Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ I'm just jumping in on the tail of this, but you can try and give me the smack down if you want. Or you can quit using the software I write. qtp-sa-update does not touch the SA executables at all. I don't even know where you would get the idea if you even looked at the script. I think if you do your due diligence you'll see the script does almost exactly what the 2 links you provided do almost step by step. Looking at the error, it looks like a remnant left over from when the spamassassin-toaster package spec file was broken or at least acting weird. I'd suggest rebuilding the package (spamassassin-toaster). It looks like you got one of the many bugs reported on the list by this latest version or revert to an older version. (to recap: the qtp-sa-update script removed the RDJ rules if they were there from an older version of QTP, then installs the Apache/Spamassassin channel, then installs the OpenProtect channel. It doesn't touch the executable at all) -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
OK. Should probably put 1.3.14 on the website, then. So that qtp- newmodel and other upgrades don't run into the same problem. Interesting. That directory is the one that was coming up as part of my 'issues'. I'm afraid I'm not quite up to 'spec file mod' level status. Is it at all possible that the correction for 1.3.14 would lead to a change somewhere in some portion of the includes or the files for the binaries for Spamassassin which would then convince the system to look for the .pre files in that location rather than /etc/mail/ spamassassin ? Roxanne On May 8, 2008, at 5:59 PM, Eric Shubert wrote: Use 1.3.14. It contains a bug fix in the spec file (otherwise they're the same). The bug it fixes is: install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/ local.cf.bz2': No such file or directory Roxanne Sandesara wrote: I do have a question. When the last Spamassassin-toaster package came out, there were problems. This was then followed by a thread that included a package Eric put together that was version 3.2.4 release 1.3.14. I have that package. But the QMT website is only showing release 1.3.13. Should I do a rebuild with release 1.3.14's src.rpm? Or should I DL release 1.3.13's src.rpm and build that instead? Roxanne On May 8, 2008, at 12:59 PM, Roxanne Sandesara wrote: To be clear, I was not blaming Jake, or his utilities. I've had great luck with everything Jake has ever done or offered. I was merely answering the question of how it was I'd installed sa-update. I'm also not really sure that the executables themselves /have/ been messed up. It's possible. They might be. Or they might be pulling in data from some other included file that is incorrect. I just can't /find/ that other file. I also can't quite fathom how, if the executables had been messed up during the installation - which also happened this prior weekend - how things managed to run just fine until yesterday afternoon. My suspicion would have been that some run of some cron job or another ended up altering some file or another to put in this incorrect path and create the issue. But I really have no clue. I'm fishing in the dark. Nevertheless. I will try, as stated, to DL the latest SA src.rpm, rebuild, and re-install when I get a chance, either late tonight or this coming weekend. I do appreciate all of the help I received trying to narrow down what was going on and how to get things back up and running. Roxanne On May 8, 2008, at 12:49 PM, Jake Vickers wrote: James Pratt wrote: Ah, ok... that explains it ... So whoever wrote this qtp-sa-update deserves a smackdown... What are they thinking by touching the SA executables ? That is just *very* bad (I would dare say *evil* ;) programming... :\ Note to others: Configure sa-update's using these instructions - simple, to the point, and it wont' touch your binaries/scripts... http://wiki.apache.org/spamassassin/RuleUpdates ... and for ditching RDJ, there is openprotect.com's SARE rule channel: http://saupdates.openprotect.com/ I'm just jumping in on the tail of this, but you can try and give me the smack down if you want. Or you can quit using the software I write. qtp-sa-update does not touch the SA executables at all. I don't even know where you would get the idea if you even looked at the script. I think if you do your due diligence you'll see the script does almost exactly what the 2 links you provided do almost step by step. Looking at the error, it looks like a remnant left over from when the spamassassin-toaster package spec file was broken or at least acting weird. I'd suggest rebuilding the package (spamassassin-toaster). It looks like you got one of the many bugs reported on the list by this latest version or revert to an older version. (to recap: the qtp-sa-update script removed the RDJ rules if they were there from an older version of QTP, then installs the Apache/Spamassassin channel, then installs the OpenProtect channel. It doesn't touch the executable at all) -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
Ok, I have to really question the development habits/cycle of this project at this point... Why is this guy recommending a version that's not on the official site, and further, he writes the fix has to do with the OP's original problem. Wasn't' it just last night he was blaming it on dns? Wth?... Sorry about earlier Jake, nothing personal, I don't use qtp, nor did I do due diligence , but in the absence of any developer reply, I was hoping someone may clarify if I put it that way, so thank you . Personally, I knew NOONE on earth would be foolish enough to write a utility that breaks sa of course, I was trying to make the OP understand that a simple update of sa-config would never do such harm. I run qmt , not qtp, and to be brutally honest, it's only because I had to move my qmail server quickly and could not rebuild it from scratch net-qmail src etc. I joined this list to get some idea of who uses this stuff more than needing help, and to keep up with any updates. I guess what *truly* amazes me about this mailing list is that there are s many clueless noobs running these setups as a real business.. that's frightening... When I first learned straight qmail back in '02 and had asked even 50% of the types of questions I see here on a weekly basis (especially, Help, my customers are whining and im clueless!), I would get no reply at all, a swift and terse RTFM and either a link to qmail.org, or the proper RFC/archive post. Point being, it's incredibly complex industrial-grade MTA software that is bundled here... Making it simple for everyday people to run an MTA is not always a good thing - it may be good for mail admins who know what they are doing (Right everyone, you all do know Email and what RFC822 is correct, ? :), but not necessarily for just anybody with a linux shell/server and a static IP with dns... Tell me, does this bother you at all? How do you know your software is not abused by professional spammers? I know if I decided to become one, I would probably be here in a second. Hey, no *real* learning of the mta software necessary? Perfect, spams-aaaay!! :) Lastly, how is this project perceived by the qmail-users mail list folks? This is an open question to anyone who helps develop this qtp/qmt stuff, as I'm simply curious. Do they consider it to be highly bastardized, unsupported, and not recommended, just as qmail rocks is ? ... Can anyone address these questions , especially the apparent lack of version control/builds, as evidenced below, to convince me this is something worth staying with, because right now it looks about as well-kept/organized as the current White House... :-P Cheers! jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 6:09 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections OK. Should probably put 1.3.14 on the website, then. So that qtp- newmodel and other upgrades don't run into the same problem. Interesting. That directory is the one that was coming up as part of my 'issues'. I'm afraid I'm not quite up to 'spec file mod' level status. Is it at all possible that the correction for 1.3.14 would lead to a change somewhere in some portion of the includes or the files for the binaries for Spamassassin which would then convince the system to look for the .pre files in that location rather than /etc/mail/ spamassassin ? Roxanne On May 8, 2008, at 5:59 PM, Eric Shubert wrote: Use 1.3.14. It contains a bug fix in the spec file (otherwise they're the same). The bug it fixes is: install: cannot create regular file `/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin/ local.cf.bz2': No such file or directory Roxanne Sandesara wrote: I do have a question. When the last Spamassassin-toaster package came out, there were problems. This was then followed by a thread that included a package Eric put together that was version 3.2.4 release 1.3.14. I have that package. But the QMT website is only showing release 1.3.13. Should I do a rebuild with release 1.3.14's src.rpm? Or should I DL release 1.3.13's src.rpm and build that instead? Roxanne On May 8, 2008, at 12:59 PM, Roxanne Sandesara wrote: To be clear, I was not blaming Jake, or his utilities. I've had great luck with everything Jake has ever done or offered. I was merely answering the question of how it was I'd installed sa-update. I'm also not really sure that the executables themselves /have/ been messed up. It's possible. They might be. Or they might be pulling in data from some other included file that is incorrect. I just can't /find/ that other file. I also can't quite fathom how, if the executables had been messed up during the installation - which also happened this prior weekend - how things managed to run just fine until yesterday afternoon. My suspicion would have been that some run of some
Re: [qmailtoaster] Re: Soft Rejections
Mr Pratt -- I have to be honest. I find the attitude perceived in this post to be rude, demeaning, and uncalled for. Like you, I was in a situation a few years ago wherein I had to migrate my office's mail server needs from a machine I'd had nothing to do with and no control over to another fully-featured server in a matter of weeks. I did not have time to do this any other way. I could not find the documentation - in manners I could understand quickly and work with effectively - on any other project save QMT. Frankly, QMT saved my company, and in the process my job. The people on this list, including the developers, have been very supportive, very responsive, and very helpful. I will be the first to admit that I do not understand everything I would like to understand about the why and the how of the inner workings of the pieces and parts of QMT. I try, and I think I understand more today than I did three years ago. But I must say that your attitude of negativity to those who do not yet know as much as you is the very reason people end up shelling out thousands of dollars for the hardware and the MS software to fill these business needs: because if they shell out enough money, they can make Microsoft and/or others help them, keeping things functioning and allow them to do their jobs. The positive and supportive attitude of others on this list, like EE, ES and Jake Vickers - and they are the rule, rather than the exception - is exactly what /all/ FOSS projects need if they are to succeed in gaining the 'street' and business credibility they require. Like it or not, sometimes a network admin gets thrown into the deep end and has to accomplish things that are far outside his or her knowledge and expertise. Belittling her for asking for help and support accomplishes nothing, except perhaps making you feel superior. I'm sorry I don't meet your expectations. I'm also sorry you don't meet mine. Roxanne On May 8, 2008, at 7:13 PM, James Pratt wrote: Ok, I have to really question the development habits/cycle of this project at this point... Why is this guy recommending a version that's not on the official site, and further, he writes the fix has to do with the OP's original problem. Wasn't' it just last night he was blaming it on dns? Wth?... Sorry about earlier Jake, nothing personal, I don't use qtp, nor did I do due diligence , but in the absence of any developer reply, I was hoping someone may clarify if I put it that way, so thank you . Personally, I knew NOONE on earth would be foolish enough to write a utility that breaks sa of course, I was trying to make the OP understand that a simple update of sa-config would never do such harm. I run qmt , not qtp, and to be brutally honest, it's only because I had to move my qmail server quickly and could not rebuild it from scratch net-qmail src etc. I joined this list to get some idea of who uses this stuff more than needing help, and to keep up with any updates. I guess what *truly* amazes me about this mailing list is that there are s many clueless noobs running these setups as a real business.. that's frightening... When I first learned straight qmail back in '02 and had asked even 50% of the types of questions I see here on a weekly basis (especially, Help, my customers are whining and im clueless!), I would get no reply at all, a swift and terse RTFM and either a link to qmail.org, or the proper RFC/archive post. Point being, it's incredibly complex industrial-grade MTA software that is bundled here... Making it simple for everyday people to run an MTA is not always a good thing - it may be good for mail admins who know what they are doing (Right everyone, you all do know Email and what RFC822 is correct, ? :), but not necessarily for just anybody with a linux shell/server and a static IP with dns... Tell me, does this bother you at all? How do you know your software is not abused by professional spammers? I know if I decided to become one, I would probably be here in a second. Hey, no *real* learning of the mta software necessary? Perfect, spams-aaaay!! :) Lastly, how is this project perceived by the qmail-users mail list folks? This is an open question to anyone who helps develop this qtp/qmt stuff, as I'm simply curious. Do they consider it to be highly bastardized, unsupported, and not recommended, just as qmail rocks is ? ... Can anyone address these questions , especially the apparent lack of version control/builds, as evidenced below, to convince me this is something worth staying with, because right now it looks about as well-kept/organized as the current White House... :-P Cheers! jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 6:09 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections OK. Should probably put 1.3.14 on the website
Re: [qmailtoaster] Re: Soft Rejections
Jaime, I should think you'd have a little more courtesy on a list associated with a product that apparently helped to bail out your rear end. Be amazed Jaime, be very amazed. No RTFMs here. That's not our gig. We're not here to stroke egos. I think the fact that you've worked with qmail since '02 and ended up with QMT speaks volumes. You couldn't build a reliable mail server in 6 years? You're right that it's not trivial. James Pratt wrote: Ok, I have to really question the development habits/cycle of this project at this point... Why is this guy recommending a version that's not on the official site, and further, he writes the fix has to do with the OP's original problem. Wasn't' it just last night he was blaming it on dns? Wth?... Sorry about earlier Jake, nothing personal, I don't use qtp, nor did I do due diligence , but in the absence of any developer reply, I was hoping someone may clarify if I put it that way, so thank you . Personally, I knew NOONE on earth would be foolish enough to write a utility that breaks sa of course, I was trying to make the OP understand that a simple update of sa-config would never do such harm. I run qmt , not qtp, and to be brutally honest, it's only because I had to move my qmail server quickly and could not rebuild it from scratch net-qmail src etc. I joined this list to get some idea of who uses this stuff more than needing help, and to keep up with any updates. I guess what *truly* amazes me about this mailing list is that there are s many clueless noobs running these setups as a real business.. that's frightening... When I first learned straight qmail back in '02 and had asked even 50% of the types of questions I see here on a weekly basis (especially, Help, my customers are whining and im clueless!), I would get no reply at all, a swift and terse RTFM and either a link to qmail.org, or the proper RFC/archive post. Point being, it's incredibly complex industrial-grade MTA software that is bundled here... Making it simple for everyday people to run an MTA is not always a good thing - it may be good for mail admins who know what they are doing (Right everyone, you all do know Email and what RFC822 is correct, ? :), but not necessarily for just anybody with a linux shell/server and a static IP with dns... Tell me, does this bother you at all? How do you know your software is not abused by professional spammers? I know if I decided to become one, I would probably be here in a second. Hey, no *real* learning of the mta software necessary? Perfect, spams-aaaay!! :) Lastly, how is this project perceived by the qmail-users mail list folks? This is an open question to anyone who helps develop this qtp/qmt stuff, as I'm simply curious. Do they consider it to be highly bastardized, unsupported, and not recommended, just as qmail rocks is ? ... Can anyone address these questions , especially the apparent lack of version control/builds, as evidenced below, to convince me this is something worth staying with, because right now it looks about as well-kept/organized as the current White House... :-P Cheers! jamie -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
-Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 7:50 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections Mr Pratt -- I have to be honest. I find the attitude perceived in this post to be rude, demeaning, and uncalled for. Like you, I was in a situation a few years ago wherein I had to migrate my office's mail server needs from a machine I'd had nothing to do with and no control over to another fully-featured server in a matter of weeks. I did not have time to do this any other way. I could not find the documentation - in manners I could understand quickly and work with effectively - on any other project save QMT. Frankly, QMT saved my company, and in the process my job. Ms Silver/Sandesara, Ok, so perhaps I am jaded. I have watched the spam literally destroy the value of email. If QMT saved a company, super. That's great. I have no problems with that. What I am questioning is the version control here, or lack thereof, and forgive me, but I do not feel pity for any business that find's themselves in hot water over email. It's been going to hell for 7 years now, life is tough, get a helmet. The people on this list, including the developers, have been very supportive, very responsive, and very helpful. I will be the first to admit that I do not understand everything I would like to understand about the why and the how of the inner workings of the pieces and parts of QMT. I try, and I think I understand more today than I did three years ago. But I must say that your attitude of negativity to those who do not yet know as much as you is the very reason people end up shelling out thousands of dollars for the hardware and the MS software to fill these business needs: because if they shell out enough money, they can make Microsoft and/or others help them, keeping things functioning and allow them to do their jobs. I agree, list support seems great, however that is true of any oss list out there, that is the point of them. My point was that it should not be simple for just anyone to install a mail server, as that is at least 50% of the reason email is growing more and more worthless. Again, I have spent 7 years dealing with messed-up configurations, spam beyond belief and utter stupidity on the part of people who suddenly started running mail servers and thereby proliferating the spam problem further, because they did not know enough to lock down their boxes, and ignored the problem(s) afterwards. The positive and supportive attitude of others on this list, like EE, ES and Jake Vickers - and they are the rule, rather than the exception - is exactly what /all/ FOSS projects need if they are to succeed in gaining the 'street' and business credibility they require. Agreed , my apologies for not espousing the oss warriors - we all owe them indeed. As well as Dr. Bernstein. And Linus. Etc. etc. ;) Like it or not, sometimes a network admin gets thrown into the deep end and has to accomplish things that are far outside his or her knowledge and expertise. Yes, that is when you call a consultant, or ask for the risk of business suicide, I've been there myself And quite the contrary , although I do the majority of my work these days on very propietery systems, and no they are not MS, either! Belittling her for asking for help and support accomplishes nothing, except perhaps making you feel superior. I'm sorry I don't meet your expectations. I'm also sorry you don't meet mine. Roxanne Roxanne - I did not mean for this to be about you, or your level of competence in any fashion, and so my deepest apologies for you taking it this way. If you do remember , I did try to help you with sa, and am only trying to help you further by getting some clarification on this project, because in all reality, it's really just a re-package project, of other projects... This makes version control yet even more complex. :\ My profound apologies to you, as I tried to refer to you in the 3rd person for that specific reason. I do not consider myself better than anyone else either just because I have run mail servers for a long time ,,, rather, I was trying to get a reply from the developers here. (To be honest, I despise email, I am actually a storage area network admin these days, and am getting out of the email business completely in a few months, and could not be happier about it! :) In my opinion, having watched Email's business value (ok so it never really had any but whatever right) decrease with the spam and viruses over the past few years by 100% a year, I am quite convinced that like the current us economy, it cannot sustain itself. The spam and garbage grows by 100% per year. How can any system accurately filter it all in 5 more years? ... yikes... I have no interest in finding out either at this point, because it's beyond hope.. :\ PS - I don't know you , so I have
Re: [qmailtoaster] Re: Soft Rejections
James Pratt wrote: Ok, I have to really question the development habits/cycle of this project at this point... Why is this guy recommending a version that's not on the official site, and further, he writes the fix has to do with the OP's original problem. Wasn't' it just last night he was blaming it on dns? Wth?... Qmailtoaster was originally started by Miguel Beccari years ago as an easy way to install Qmail. I've personally installed it about every way you can think of, and this is one of the faster ways to get a mail server up an running. Carrying on, Miguel kinda disappeared after a while, and Nick Hemmesch took the project over for the next 4 years or so. Since this is a hobby for those of us who develop things for Qmailtoaster the release cycle is sporadic at best. Nick became busy with work and home life and handed over the position to Erik Espinoza. Erik also has a real job and works on the project when he has spare time. Since it all ran on the server owned by whoever was maintaining it at the time, they were the only ones who could update the packages. At this time, Erik is the only one who can update the main site. Eric Shubes, myself, Justice London, Sam Clippinger, Lucian Cristian, Dan McCallister, Nate Davis, and the many who I've forgotten to mention (Sorry!) all contribute when/if we can. A couple of us have written updated packages and we have to submit them to Erik who will (if everything turns out okay during testing) update the main site when he has some time. I created the Qmailtoaster-Plus package along with Eric Shubes as a helper for those who run Qmailtoaster systems everyday. A lot of the tools bundled with it are the same tools that we (and those who have contributed to the package) use everyday. It's meant to try and make an admin's job easier. You'll find that myself and Eric write 85% of the scripts in this package ourselves, for ourselves. The package was meant as a way for us to easily share some of the tools we use. In the course of helping people you have to remember that we're reading the same emails as you and probably while working on other projects. You don't hear much out of ME because I work on other things. Installing/fixing/repairing/upgrading/building Qmail machines is one of the services that I offer at my consulting company. I get paid for these services and have successfully gotten several ISPs running using this very same software and I was even asked to consult on a 1-million user Qmail system out West /shameless plug. I (like the others who provide support on this list) receive 400-800 emails a day (I work on a couple different projects). I don't always read the emails in depth and (bad on my part I'll admit) I shoot answers from the hip most of the time. That's what you get on a list like this though. If you want personal attention and someone to hold your hand through every step of whatever problem you may have (and not get from-the-hip answers) then you're more than welcome to hire a consultant for this purpose. There's a section on the wiki for commercial support that lists those of us who offer services. No offense to Roxanne, but if you want faster fixes and someone to give you more than 25% of their attention to your problem then be willing to pay for it. Without seeing specific things on a system we have to guess at what the problem may be and that's the risk you take for relying on free support. As far as the development cycle; it's frozen. At least Qmailtoaster is. Erik is working on the 1.4 branch and has frozen the 1.3 branch with the exception of upstream updates (spamassassin, clamav). We (Eric and I, with me being the only one who can update the website right now but that's soon to be rectified) update qmailtoaster-plus when we get time and as we feel that enough updates have been made to qualify for a new release. Sorry about earlier Jake, nothing personal, I don't use qtp, nor did I do due diligence , but in the absence of any developer reply, I was hoping someone may clarify if I put it that way, so thank you . Personally, I knew NOONE on earth would be foolish enough to write a utility that breaks sa of course, I was trying to make the OP understand that a simple update of sa-config would never do such harm. No offense taken. I explained why I don't answer much in the above. I run qmt , not qtp, and to be brutally honest, it's only because I had to move my qmail server quickly and could not rebuild it from scratch net-qmail src etc. I joined this list to get some idea of who uses this stuff more than needing help, and to keep up with any updates. QTP is just an add-on for QMT. It's a collection of scripts and utilities mostly written by Eric and myself that we felt like sharing with others in the hopes of making their jobs easier. And I came to Qmailtoaster in pretty much the same way as you a few years ago. I guess what *truly*
RE: [qmailtoaster] Re: Soft Rejections
-Original Message- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: Thursday, May 08, 2008 8:07 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections Jaime, I should think you'd have a little more courtesy on a list associated with a product that apparently helped to bail out your rear end. Nah... .. your... um... product in no way bailed out my rear end, I was just lazy. LOL. ;) Be amazed Jaime, be very amazed. No RTFMs here. That's not our gig. We're not here to stroke egos. I understand that, that's awesome, I would go join bind-users for ego-strokes and flame-wars. What I'm asking is if this project has any real version control. No answer so far..?. I think the fact that you've worked with qmail since '02 and ended up with QMT speaks volumes. You couldn't build a reliable mail server in 6 years? You're right that it's not trivial. Well my friend, not to burst your bubble, but it's my personal home mail server, just for fun. (I really only care about my web server) .. Yes, I had built the old one six years ago, and many others since for other people. If you are implying that it took me 6 years to build a server, and that it is *that* complex, that's pretty funny.. I could have just as easily used sendmail, since I only need one account nowadays, but was feeling lazy and did not want to deal with m4 over my last winter break. I had just installed 1.5 mil of new hardware.. I was a bit tired. .. should I apologize to you now too? :0) Back to the point.. version control , anyone...? hmm... James Pratt wrote: Ok, I have to really question the development habits/cycle of this project at this point... Why is this guy recommending a version that's not on the official site, and further, he writes the fix has to do with the OP's original problem. Wasn't' it just last night he was blaming it on dns? Wth?... Sorry about earlier Jake, nothing personal, I don't use qtp, nor did I do due diligence , but in the absence of any developer reply, I was hoping someone may clarify if I put it that way, so thank you . Personally, I knew NOONE on earth would be foolish enough to write a utility that breaks sa of course, I was trying to make the OP understand that a simple update of sa-config would never do such harm. I run qmt , not qtp, and to be brutally honest, it's only because I had to move my qmail server quickly and could not rebuild it from scratch net-qmail src etc. I joined this list to get some idea of who uses this stuff more than needing help, and to keep up with any updates. I guess what *truly* amazes me about this mailing list is that there are s many clueless noobs running these setups as a real business.. that's frightening... When I first learned straight qmail back in '02 and had asked even 50% of the types of questions I see here on a weekly basis (especially, Help, my customers are whining and im clueless!), I would get no reply at all, a swift and terse RTFM and either a link to qmail.org, or the proper RFC/archive post. Point being, it's incredibly complex industrial-grade MTA software that is bundled here... Making it simple for everyday people to run an MTA is not always a good thing - it may be good for mail admins who know what they are doing (Right everyone, you all do know Email and what RFC822 is correct, ? :), but not necessarily for just anybody with a linux shell/server and a static IP with dns... Tell me, does this bother you at all? How do you know your software is not abused by professional spammers? I know if I decided to become one, I would probably be here in a second. Hey, no *real* learning of the mta software necessary? Perfect, spams-aaaay!! :) Lastly, how is this project perceived by the qmail-users mail list folks? This is an open question to anyone who helps develop this qtp/qmt stuff, as I'm simply curious. Do they consider it to be highly bastardized, unsupported, and not recommended, just as qmail rocks is ? ... Can anyone address these questions , especially the apparent lack of version control/builds, as evidenced below, to convince me this is something worth staying with, because right now it looks about as well-kept/organized as the current White House... :-P Cheers! jamie -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
Re: [qmailtoaster] Re: Soft Rejections
James Pratt wrote: I agree, list support seems great, however that is true of any oss list out there, that is the point of them. My point was that it should not be simple for just anyone to install a mail server, as that is at least 50% of the reason email is growing more and more worthless. Again, I have spent 7 years dealing with messed-up configurations, spam beyond belief and utter stupidity on the part of people who suddenly started running mail servers and thereby proliferating the spam problem further, because they did not know enough to lock down their boxes, and ignored the problem(s) afterwards. I'm only going to comment at this one part: Were you an admin during the days of the net send spams? That was OS related, not even email and I was called in to fix a system that was receiving THOUSANDS a day. I find that an hour long TV show is only 26 minutes a tiny step over into the spam realm. Spam is nothing but advertising. I even purchased XM radio because I was tired of what I considered spam - I already have a new car; I don't need someone screaming at me like a WWF wrestler that I *HAVE* to go get a new one. Or Dan Marino endorsing Chevy dealerships. Come on, like he drives anything less than an S-Class. Spam is spam. It was a problem BEFORE projects like this one came about. It would be there either way. There was even unsolicited messages back on my FIDOnet BBS back in the 80's. There wasn't really even an interweb thing then (yes, I've been at this a while). And just about anyone could go to a hacker FTP site or use Bittorrent and download Exchange 2000, 2002, 2003, etc. and spam from them just as easily. And they're a *LOT* easier to install (okay, another shameless plug: my ISO is about as easy to install, but you still don't get the pretty icons to click on to do everything for you). Anyway, spam would be there any way. In an independent study that I conducted (not endorsed, qualified, accurate, blah blah blah) most of my spam comes from Sendmail mailers or PHP based mailers. I'm off to spend some time with my family now. Night all!
[qmailtoaster] Re: Soft Rejections
Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft-rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
Could this be it http://lists.mailscanner.info/pipermail/mailscanner/2008-March/082765.ht ml ~ciao jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:18 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Soft Rejections Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft-rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Yes and no. I did not mess up the pre files. The line in question is there in the proper file. However, the additional testing measures suggested there have yielded other results. When I shell in as vpopmail user and --lint, I get : warn : config: path /var/tmp/spamassassin-toaster-root/etc/mail/ spamassassin is inaccessible: Permission denied I've tried going back to root and chowning this to vpopmail:vchkpw. The outcome/error does not change. Somehow, this must be the problem, but I know I didn't make this happen and I don't know how to correct it. Help? Roxanne On May 7, 2008, at 3:27 PM, James Pratt wrote: Could this be it http://lists.mailscanner.info/pipermail/mailscanner/2008-March/ 082765.ht ml ~ciao jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:18 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Soft Rejections Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at / usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft-rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
If you run spamassassin --lint -D can you verify you are loading the configs you are intending? Ie, is the config path below that is erroring the same as your sa installation for your site? Check directories higher up in the path for the r-xr-xr-x bits as well... jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:41 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections Yes and no. I did not mess up the pre files. The line in question is there in the proper file. However, the additional testing measures suggested there have yielded other results. When I shell in as vpopmail user and --lint, I get : warn : config: path /var/tmp/spamassassin-toaster-root/etc/mail/ spamassassin is inaccessible: Permission denied I've tried going back to root and chowning this to vpopmail:vchkpw. The outcome/error does not change. Somehow, this must be the problem, but I know I didn't make this happen and I don't know how to correct it. Help? Roxanne On May 7, 2008, at 3:27 PM, James Pratt wrote: Could this be it http://lists.mailscanner.info/pipermail/mailscanner/2008-March/ 082765.ht ml ~ciao jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:18 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Soft Rejections Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at / usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft-rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
You can also try modifying /var/qmail/supervise/spamd/run and add a -D to the spamd startup option. This will make spamd output lots of mostly useless information to /var/log/qmail/spamd/current, which may or may not help you figure it out.. (Obviously, you have to restart spamd etc) I can't think of anything else or why it may have happened. I've had a similar issue before with the config path being un-readable, but on sendmail and mimedefang, not qmail or qtp. :\ jamie -Original Message- From: James Pratt [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:46 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] Re: Soft Rejections If you run spamassassin --lint -D can you verify you are loading the configs you are intending? Ie, is the config path below that is erroring the same as your sa installation for your site? Check directories higher up in the path for the r-xr-xr-x bits as well... jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:41 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections Yes and no. I did not mess up the pre files. The line in question is there in the proper file. However, the additional testing measures suggested there have yielded other results. When I shell in as vpopmail user and --lint, I get : warn : config: path /var/tmp/spamassassin-toaster-root/etc/mail/ spamassassin is inaccessible: Permission denied I've tried going back to root and chowning this to vpopmail:vchkpw. The outcome/error does not change. Somehow, this must be the problem, but I know I didn't make this happen and I don't know how to correct it. Help? Roxanne On May 7, 2008, at 3:27 PM, James Pratt wrote: Could this be it http://lists.mailscanner.info/pipermail/mailscanner/2008-March/ 082765.ht ml ~ciao jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:18 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Soft Rejections Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at / usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft- rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED
Re: [qmailtoaster] Re: Soft Rejections
I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at / usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
: Wednesday, May 07, 2008 3:41 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections Yes and no. I did not mess up the pre files. The line in question is there in the proper file. However, the additional testing measures suggested there have yielded other results. When I shell in as vpopmail user and --lint, I get : warn : config: path /var/tmp/spamassassin-toaster-root/etc/mail/ spamassassin is inaccessible: Permission denied I've tried going back to root and chowning this to vpopmail:vchkpw. The outcome/error does not change. Somehow, this must be the problem, but I know I didn't make this happen and I don't know how to correct it. Help? Roxanne On May 7, 2008, at 3:27 PM, James Pratt wrote: Could this be it http://lists.mailscanner.info/pipermail/mailscanner/2008-March/ 082765.ht ml ~ciao jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:18 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Soft Rejections Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at / usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft-rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used for at
your site? Is something in one of your .cf's pointing to it? This is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require' failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version 2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin/
10_default_prefs.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_advance_fee.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_body_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_compensate.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_dnsbl_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_drugs.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_dynrdns.cf
[10425] dbg: config: read file /usr/share/spamassassin/
20_fake_helo_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_head_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_html_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_imageinfo.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_meta_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_net_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_phrases.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_porn.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_ratware.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_uri_tests.cf
[10425] dbg: config: read file /usr/share
Re: [qmailtoaster] Re: Soft Rejections
OK. I went back and checked on the rest of the path. Set 555, this cleared that up ... and returned me to the check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/ 5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. And as I've said, the loadplugin line is in my .pre files. So I feel like I'm chasing my tail and coming up without a clue. Any other ideas? Anyone? Roxanne On May 7, 2008, at 3:52 PM, James Pratt wrote: You can also try modifying /var/qmail/supervise/spamd/run and add a -D to the spamd startup option. This will make spamd output lots of mostly useless information to /var/log/qmail/spamd/current, which may or may not help you figure it out.. (Obviously, you have to restart spamd etc) I can't think of anything else or why it may have happened. I've had a similar issue before with the config path being un-readable, but on sendmail and mimedefang, not qmail or qtp. :\ jamie -Original Message- From: James Pratt [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:46 PM To: qmailtoaster-list@qmailtoaster.com Subject: RE: [qmailtoaster] Re: Soft Rejections If you run spamassassin --lint -D can you verify you are loading the configs you are intending? Ie, is the config path below that is erroring the same as your sa installation for your site? Check directories higher up in the path for the r-xr-xr-x bits as well... jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:41 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections Yes and no. I did not mess up the pre files. The line in question is there in the proper file. However, the additional testing measures suggested there have yielded other results. When I shell in as vpopmail user and --lint, I get : warn : config: path /var/tmp/spamassassin-toaster-root/etc/mail/ spamassassin is inaccessible: Permission denied I've tried going back to root and chowning this to vpopmail:vchkpw. The outcome/error does not change. Somehow, this must be the problem, but I know I didn't make this happen and I don't know how to correct it. Help? Roxanne On May 7, 2008, at 3:27 PM, James Pratt wrote: Could this be it http://lists.mailscanner.info/pipermail/mailscanner/2008-March/ 082765.ht ml ~ciao jamie -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 3:18 PM To: qmailtoaster-list@qmailtoaster.com Subject: [qmailtoaster] Re: Soft Rejections Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at / usr/ lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: About two hours ago, my Toaster just started soft-rejecting just about every message that isn't coming from inside. The first confirmed symptom was that email was not being sent from people's clients. I checked the submission logs, found the errors, and altered the tcp.smtp file to put RBLSMTP= into the line for the external IP address of the firewall. This corrected our outgoing mail. But email is still being soft-rejected from all outside sources. I've tried doing the same for the 'everything else' line, but that isn't working to fix this. 1) If I need to uninstall Spamdyke, how do I do so? 2) How do I find out /why/ these messages are being soft- rejected, so that I can wrangle this server around and make it start accepting email like a mailserver should? 3) Anyone have any idea why this would just suddenly start to be a problem? Roxanne - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http
Re: [qmailtoaster] Re: Soft Rejections
To be honest, I have no clue what it is used for. I didn't create it.
I didn't ask for it. I would have to assume that something within
SpamAssassin for Toaster is doing this. But if it's a path no one
else here has heard of, then I don't know what would have set it up
to use this.
To me, it looks like a chrooted spamassassin. But I don't know why
that would be in place. How would you suggest I go about looking for
whatever is creating or calling for it?
Roxanne
On May 7, 2008, at 4:09 PM, James Pratt wrote:
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used for at
your site? Is something in one of your .cf's pointing to it? This is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require'
failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version 2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin/
10_default_prefs.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_advance_fee.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_body_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_compensate.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_dnsbl_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_drugs.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_dynrdns.cf
[10425] dbg: config: read file /usr/share/spamassassin/
20_fake_helo_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_head_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_html_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/
20_imageinfo.cf
RE: [qmailtoaster] Re: Soft Rejections
Weird... When you break that path down, it almost seems like you have
some sort of variable foo-barr'ing going on ?
/var/tmp (makes sense) /spamassassin-toaster-root (???)
/etc/mail/spamassassin (again, makes sense..)
I wonder if you have something putting too many vars together
someplace. It would probably work fine if it were just trying to open
files in /var/tmp, right?
Well, there is always :
su - vpopmail -c strace Spamassassin --lint -D , but be sure you have
a large scroll buffer and some aspirin! :(
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require' failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version 2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin/
10_default_prefs.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_advance_fee.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_body_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_compensate.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_dnsbl_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_drugs.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_dynrdns.cf
[10425] dbg: config: read file /usr/share/spamassassin/
20_fake_helo_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_head_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_html_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_imageinfo.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_meta_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_net_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_phrases.cf
[10425] dbg: config: read
Re: [qmailtoaster] Re: Soft Rejections
OK. Digging further into that directory structure, it continues with /
sa-update-keys, in which are several .gpg files. I'm assuming, as
such, that this is coming from my installing sa-update instead of
RulesDuJour when I rebuilt things this weekend. I'll have to go back
and figure out if that particular error had been going on the whole
time or not.
Regardless, I appear to have corrected that problem, and I am now
back with the earlier check_mail error.
Roxanne
On May 7, 2008, at 4:18 PM, Roxanne Sandesara wrote:
To be honest, I have no clue what it is used for. I didn't create
it. I didn't ask for it. I would have to assume that something
within SpamAssassin for Toaster is doing this. But if it's a path
no one else here has heard of, then I don't know what would have
set it up to use this.
To me, it looks like a chrooted spamassassin. But I don't know why
that would be in place. How would you suggest I go about looking
for whatever is creating or calling for it?
Roxanne
On May 7, 2008, at 4:09 PM, James Pratt wrote:
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used
for at
your site? Is something in one of your .cf's pointing to it? This is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment
variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require'
failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version 2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin/
10_default_prefs.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_advance_fee.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_body_tests.cf
[10425] dbg: config: read file
/usr
RE: [qmailtoaster] Re: Soft Rejections
I'd probably start with:
find / -type f | xargs grep -i spamassassin-toaster-root
(that will find any file on the system containing that string)
if that fails, run a --lint -D with strace like I mentioned - you should
see what is calling it from where and how in the output .
lastly, Does that folder even exist in /var/tmp, or is it trying to be
created and failing with the error?
jamie
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:19 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
To be honest, I have no clue what it is used for. I didn't create it.
I didn't ask for it. I would have to assume that something within
SpamAssassin for Toaster is doing this. But if it's a path no one
else here has heard of, then I don't know what would have set it up
to use this.
To me, it looks like a chrooted spamassassin. But I don't know why
that would be in place. How would you suggest I go about looking for
whatever is creating or calling for it?
Roxanne
On May 7, 2008, at 4:09 PM, James Pratt wrote:
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used for
at
your site? Is something in one of your .cf's pointing to it? This
is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment
variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require'
failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version
2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin
Re: [qmailtoaster] Re: Soft Rejections
Roxanne,
I read your posts, and this is looks like perl problem. You can update
via CPAN or yum.
SpamDyke is nice, but requare configuration and maintance, and i
disable it.
Eric is give me realy simple how to disable spamdyke
# cd /var/qmail/supervise/smtp
# rm -f run
# ln -s run.dist run
# qmailctl restart
Replace run.dist with run.spamdyke to turn it back on.
On 2008.05.07, at 22:25, Roxanne Sandesara wrote:
OK. Digging further into that directory structure, it continues
with /sa-update-keys, in which are several .gpg files. I'm assuming,
as such, that this is coming from my installing sa-update instead of
RulesDuJour when I rebuilt things this weekend. I'll have to go back
and figure out if that particular error had been going on the whole
time or not.
Regardless, I appear to have corrected that problem, and I am now
back with the earlier check_mail error.
Roxanne
On May 7, 2008, at 4:18 PM, Roxanne Sandesara wrote:
To be honest, I have no clue what it is used for. I didn't create
it. I didn't ask for it. I would have to assume that something
within SpamAssassin for Toaster is doing this. But if it's a path
no one else here has heard of, then I don't know what would have
set it up to use this.
To me, it looks like a chrooted spamassassin. But I don't know why
that would be in place. How would you suggest I go about looking
for whatever is creating or calling for it?
Roxanne
On May 7, 2008, at 4:09 PM, James Pratt wrote:
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used
for at
your site? Is something in one of your .cf's pointing to it? This
is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment
variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require'
failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version
2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail
Re: [qmailtoaster] Re: Soft Rejections
That directory (/var/tmp/package-root/) is used to build the binary rpms.
It should not come into play at all in an operational machine, and should be
safely removed (as is true for anything in /var/tmp/).
James Pratt wrote:
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used for at
your site? Is something in one of your .cf's pointing to it? This is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require' failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version 2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin/
10_default_prefs.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_advance_fee.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_body_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_compensate.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_dnsbl_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_drugs.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_dynrdns.cf
[10425] dbg: config: read file /usr/share/spamassassin/
20_fake_helo_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_head_tests.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_html_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_imageinfo.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_meta_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_net_tests.cf
[10425] dbg: config: read file /usr/share/spamassassin/20_phrases.cf
[10425] dbg
Re: [qmailtoaster] Re: Soft Rejections
Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
Something - I haven't found it yet - is still calling to this
directory. I managed to make the perl plugin error disappear by
copying my .pre files from /etc/mail/spamassassin to its mate in the /
var/tmp/package-root/... tree. --lint -D then shows each of those
files being processed, and no errors.
I did a ./qmail-spam.sh restart and mail has begun to flow again.
There will still be some earlier soft-rejected mail that may take
hours yet to be re-attempted and accepted, but I've gotten new
messages from the outside just fine now.
I've started a search to find all references to that directory
anywhere on the system. Hopefully that will help me track down what
caused this. As I said in an earlier email, it seems to have been
related to the sa-update installation, as that directory was the only
one previously that had an files in it, a few .gpg files.
Roxanne
On May 7, 2008, at 4:51 PM, Eric Shubert wrote:
That directory (/var/tmp/package-root/) is used to build the
binary rpms.
It should not come into play at all in an operational machine, and
should be
safely removed (as is true for anything in /var/tmp/).
James Pratt wrote:
Possibly a very dumb question, but what is :
/var/tmp/spamassassin-toaster-root/etc/mail/spamassassin used
for at
your site? Is something in one of your .cf's pointing to it? This is
probably why it's not on google, as it's not a standard path, or at
least one I've ever heard of.. :\
-Original Message-
From: Roxanne Sandesara [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 07, 2008 4:00 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Re: Soft Rejections
I believe it's the only error I have going on. The output is below.
$ spamassassin --lint -D
[10425] dbg: logger: adding facilities: all
[10425] dbg: logger: logging level is DBG
[10425] dbg: generic: SpamAssassin version 3.2.4
[10425] dbg: config: score set 0 chosen.
[10425] dbg: util: running in taint mode? yes
[10425] dbg: util: taint mode: deleting unsafe environment
variables,
resetting PATH
[10425] dbg: util: PATH included '/usr/kerberos/bin', keeping
[10425] dbg: util: PATH included '/usr/local/bin', keeping
[10425] dbg: util: PATH included '/bin', keeping
[10425] dbg: util: PATH included '/usr/bin', keeping
[10425] dbg: util: PATH included '/usr/X11R6/bin', keeping
[10425] dbg: util: final PATH set to: /usr/kerberos/bin:/usr/local/
bin:/bin:/usr/bin:/usr/X11R6/bin
[10425] dbg: dns: is Net::DNS::Resolver available? yes
[10425] dbg: dns: Net::DNS version: 0.58
[10425] dbg: diag: perl platform: 5.008008 linux
[10425] dbg: diag: module installed: Digest::SHA1, version 2.07
[10425] dbg: diag: module installed: HTML::Parser, version 3.56
[10425] dbg: diag: module installed: Net::DNS, version 0.58
[10425] dbg: diag: module installed: MIME::Base64, version 3.07
[10425] dbg: diag: module installed: DB_File, version 1.816
[10425] dbg: diag: module installed: Net::SMTP, version 2.31
[10425] dbg: diag: module installed: Mail::SPF, version v2.005
[10425] dbg: diag: module installed: Mail::SPF::Query, version
1.999001
[10425] dbg: diag: module installed: IP::Country::Fast, version
604.001
[10425] dbg: diag: module not installed: Razor2::Client::Agent
('require' failed)
[10425] dbg: diag: module not installed: Net::Ident ('require'
failed)
[10425] dbg: diag: module installed: IO::Socket::INET6, version 2.54
[10425] dbg: diag: module installed: IO::Socket::SSL, version 1.13
[10425] dbg: diag: module installed: Compress::Zlib, version 1.42
[10425] dbg: diag: module installed: Time::HiRes, version 1.9712
[10425] dbg: diag: module installed: Mail::DomainKeys, version 1.0
[10425] dbg: diag: module installed: Mail::DKIM, version 0.301
[10425] dbg: diag: module installed: DBI, version 1.602
[10425] dbg: diag: module installed: Getopt::Long, version 2.35
[10425] dbg: diag: module installed: LWP::UserAgent, version 2.033
[10425] dbg: diag: module installed: HTTP::Date, version 1.47
[10425] dbg: diag: module installed: Archive::Tar, version 1.38
[10425] dbg: diag: module installed: IO::Zlib, version 1.04
[10425] dbg: diag: module not installed: Encode::Detect ('require'
failed)
[10425] dbg: ignore: using a test message to lint rules
[10425] warn: config: path /var/tmp/spamassassin-toaster-root/etc/
mail/spamassassin is inaccessible: Permission denied
[10425] dbg: config: using /etc/mail/spamassassin for site rules
pre files
[10425] dbg: config: read file /etc/mail/spamassassin/init.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v310.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v312.pre
[10425] dbg: config: read file /etc/mail/spamassassin/v320.pre
[10425] dbg: config: using /usr/share/spamassassin for sys rules
pre files
[10425] dbg: config: using /usr/share/spamassassin for default
rules dir
[10425] dbg: config: read file /usr/share/spamassassin/
10_default_prefs.cf
[10425] dbg: config: read file
/usr/share/spamassassin/20_advance_fee.cf
[10425
Re: [qmailtoaster] Re: Soft Rejections
Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ---Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [qmailtoaster] Re: Soft Rejections
No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su - into vpopmail's shell to run the spamassassin -- lint -D tests. Roxanne On May 7, 2008, at 7:29 PM, Eric Shubert wrote: Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/ PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz -- --- QmailToaster hosted by: VR Hosted http://www.vr.org -- --- To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- -- QmailToaster hosted by: VR Hosted http://www.vr.org --- -- To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] ---Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] -- -Eric 'shubes' - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] - QmailToaster hosted by: VR Hosted http://www.vr.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [qmailtoaster] Re: Soft Rejections
With all due respect, I see *nothing* that indicates *any* sort of dns issue here. The problem is that the Spamassassin installation is trying to create temp files in a very non-standard directory, as Eric said in a prior post. I would guess the build is just plain messed up - what does rpm -ql Spamassassin-toaster say? Inspect the rebuild output closely after. Do not rebuild it as the root user. If I were you, I would re-rpmbuild, and also run chkrootkit, and/or rkhunter... many people (still!) compile things as root. That is a very bad thing, qmail or no. :( Regards, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 8:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su - into vpopmail's shell to run the spamassassin -- lint -D tests. Roxanne On May 7, 2008, at 7:29 PM, Eric Shubert wrote: Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However, this has not corrected my problem. Messages are still being soft-rejected, even after turning off spamdyke and restarting qmail. I've got this strange permissions problem with what must be a created subdirectory in /tmp, which seems to be causing errors with SpamAssassin. I have no idea if that could be causing the soft rejects or not, but I'd - obviously - like to correct it. but I can't find anything on the Net matching the error message with the directory. Still looking for help. Roxanne On May 7, 2008, at 3:34 PM, im.fuzzy wrote: Roxanne Sandesara wrote: Further searching. I found an instance of this in the archives that suggested running a spamassassin --lint. I did so, and got the following: # spamassassin --lint check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/ PerMsgStatus.pm line 164. Help? I'm not sure what to do here. Roxanne On May 7, 2008, at 3:10 PM, Roxanne Sandesara wrote: spamdyke has to be configured...it is not a plug-n-play (like so much of the toaster stuff is) for us noobs, in my experience. i had had the watchall running and installed spamdyke...my supplier emails started being being delayed/ rejected/whatever mostly for the rdns checks...uninstalled spamdyke immediately...revisit it later in off-peak times for me igor or ivan asked 'spamdyke uninstall...howto' about a week ago...that is how i fixed my toaster fuzz - - --- QmailToaster hosted by: VR Hosted http://www.vr.org - - --- To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - -- QmailToaster hosted by: VR Hosted http://www.vr.org -- - -- To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED] ---Eric 'shubes' --- - - QmailToaster hosted by: VR Hosted http://www.vr.org --- - - To unsubscribe, e-mail: qmailtoaster-list- [EMAIL PROTECTED] For additional commands, e-mail: qmailtoaster-list- [EMAIL PROTECTED
Re: [qmailtoaster] Re: Soft Rejections
::SpamAssassin::PerMsgStatus.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PersistentAddrList.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::ASN.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AWL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AccessDB.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AntiVirus.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::AutoLearnThreshold. 3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::BodyRuleBaseExtractor. 3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Check.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DCC.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DKIM.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::DomainKeys.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Hashcash.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::MIMEHeader.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::OneLineBodyRuleType. 3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Pyzor.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Razor2.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::RelayCountry.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::ReplaceTags.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Rule2XSBody.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::SPF.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Shortcircuit.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::SpamCop.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::Test.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::TextCat.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::URIDNSBL.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::URIDetail.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::VBounce.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Plugin::WhiteListSubject.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::PluginHandler.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::SQLBasedAddrList.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::SubProcBackChannel.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Timeout.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util::DependencyInfo.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util::Progress.3pm.gz /usr/share/man/man3/Mail::SpamAssassin::Util::RegistrarBoundaries.3pm.gz /usr/share/man/man3/spamassassin-run.3pm.gz /var/log/qmail /var/log/qmail/spamd /var/qmail/supervise/spamd /var/qmail/supervise/spamd/log /var/qmail/supervise/spamd/log/run /var/qmail/supervise/spamd/run /var/qmail/supervise/spamd/supervise On May 7, 2008, at 8:39 PM, James Pratt wrote: With all due respect, I see *nothing* that indicates *any* sort of dns issue here. The problem is that the Spamassassin installation is trying to create temp files in a very non-standard directory, as Eric said in a prior post. I would guess the build is just plain messed up - what does rpm -ql Spamassassin-toaster say? Inspect the rebuild output closely after. Do not rebuild it as the root user. If I were you, I would re-rpmbuild, and also run chkrootkit, and/or rkhunter... many people (still!) compile things as root. That is a very bad thing, qmail or no. :( Regards, jp -Original Message- From: Roxanne Sandesara [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 07, 2008 8:24 PM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] Re: Soft Rejections No, nothing in the blacklists file. And Spamassassin's RBL checks are turned off in local.cf. I'm running chrooted Bind, not a caching nameserver. And yes. I was su - into vpopmail's shell to run the spamassassin -- lint -D tests. Roxanne On May 7, 2008, at 7:29 PM, Eric Shubert wrote: Roxanne Sandesara wrote: DNS appears to be working. I have no idea if an RBL site is down. At this point I've deactivated spamdyke, which was the only thing doing RBL checks, so that shouldn't be an issue anymore. You have nothing in /var/qmail/control/blacklists? That would do rbl checking. Spamassassin probably is as well, unless you are running it with the -L (local checks only) option. Are you running a caching-nameserver on the toaster? That isn't absolutely required, but highly recommended. I still have this nonsense SpamAssassin perl module error, and no way to correct it. Are you running spamassassin commands with sudo -u vpopmail -h? You need to always run spamassassin as vpopmail user. Otherwise it won't pick up the correct environment. Roxanne On May 7, 2008, at 4:52 PM, Eric Shubert wrote: Sounds a bit like a DNS issue to me. Is your DNS not working, or perhaps an RBL site down? Roxanne Sandesara wrote: I've had spamdyke running for a week without any problems until today (if indeed Spamdyke is the problem). However, thanks for the advice. I went back, found that discussion from last week, and have - at least temporarily - deactivated spamdyke. However
