Michael H wrote: > Some things to say: > > When building vpopmail, the process died when it couldn't create > /var/qmail. The reason it couldn't is because it already existed, in > fact, I had made a separate partition/mount point for it! To get around > this issue (without ripping down my file systems and re-doing them), I > umounted /var/qmail, mv /var/qmail /var/qmailBAK and ran the process > again. When vpopmail was done, I saw a "rm -fr /var/qmail" command in > the build process and heck! What was that all about?!? So I undid the > umount and the mv command and all seems to be well --- *this* email > server *seems* to be working fine anyway .... > > What I'd like for someone to do or tell me how to do is have the > rpmbuild-er check to see if /var/qmail exists (and then erase what's in > there) instead of just die because it can't create /var/qmail.
That would be in the vpopmail-toaster.spec file. Install the source, change the .spec appropriately, then rpmbuild -bs to build yourself a custom source package. Then proceed as normal. (There might be a better way to do this - someone will likely bring it up if there is). It wouldn't hurt to create a bug report on this at http://devel.qmailtoaster.com/flyspray/. FYI, you might run into a little problem with this configuration (/var/qmail NFS mounted) depending on your mount options. If you're using async, simscan will likely have a problem removing its working directories (I've seen this happen). There's no log message that is generated when this occurs. The simscan queue simply starts filling up with empty directories left over from when it processed each email. The problem occurs because simscan removes the working directory (for each email) immediately after emptying it, and the rmdir fails because NFS isn't through committing the updates yet that empty the directory. There are two solutions for this. First (and I haven't tried this one yet), you can mount it with the sync option. This would reduce your throughput a bit, but I doubt that it would be noticeable. The second option is to create yourself a cron job that runs hourly and removes the empty directories: find /var/qmail/simscan/. -empty -type d -maxdepth 1 -exec rmdir {} \; Not prettt, but it works. > Also, I modified the build script for qmailtoaster-admin (?) with the > 'spambox 1' flag and built it --- so how do I know that it worked? When > in Qmail Admin, creating a new account, there is a checkbox at the > bottom for "Spam Detection?" Is that it? Gee, I was thinking each user > in Squirrelmail would have a SPAM folder which SpamAssassin would read > to make itself smarter ... I think you're ok with this one. My understanding is that the spam folder will be created automatically when spam is received. > Also, with Domainkeys and SPF (set to 3), I can send/receive email > to/from both Yahoo and Hotmail. Yahoo handled things properly right > away (did not go into Bulk). Hotmail put my message into the Junk > folder and I had to manually tell it it's not junk and now all is well. > > I haven't ran into any checkuser.h issues yet -- there's only one email > account on the server thus far -- me! > > Thanks to the QT team -- even I can build a (working) email server! :) > > Michael > Congrats, Michael! Welcome aboard the Toaster Train. -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
