On Tue, Jun 4, 2013 at 1:26 PM, Eric Shubert <[email protected]> wrote:
> On 06/04/2013 09:38 AM, Sven Miller wrote: > >> Previously I stumbled my way through a qmailtoaster install, and now I >> have to do a fresh install on a RHEL 6.4 box. I see qmailtoaster-plus >> is the new way to do things, but I don't know how to include the >> install-time tweaks I made in the past. >> >> For one I will need to tweak the chkuser configuration. In the past >> this was done by pausing the build and editing the settings file (per >> http://wiki.qmailtoaster.com/**index.php/Chkuser<http://wiki.qmailtoaster.com/index.php/Chkuser>). >> How will I tweak the >> chkuser config when using QTP? >> > > Same way, for the most part. The build gets done in a chroot environment > though, so you'd need to chroot into it in order to change the sources. I > think it might be simpler to build your own srpm with the modified sources. > Then put your rpm in /usr/src/qtp-upgrade/SRPMS/ and qtp-newmodel will use > it. > > You're likely not to need to do this though. Which settings were you > having to tweak? The stock settings work for just about everyone now, > including many special characters for various things including blackberries > (are people still using those?). ;) Here are the current stock settings > regarding special characters: > #define CHKUSER_ALLOW_SENDER_CHAR_1 '$' > #define CHKUSER_ALLOW_SENDER_CHAR_2 '%' > #define CHKUSER_ALLOW_SENDER_CHAR_3 '/' > #define CHKUSER_ALLOW_SENDER_CHAR_4 '?' > #define CHKUSER_ALLOW_SENDER_CHAR_5 '*' > #define CHKUSER_ALLOW_SENDER_CHAR_6 '^' > #define CHKUSER_ALLOW_SENDER_CHAR_7 '~' > #define CHKUSER_ALLOW_SENDER_CHAR_8 '&' > #define CHKUSER_ALLOW_SENDER_CHAR_9 '#' > #define CHKUSER_ALLOW_SENDER_CHAR_10 '=' Unfortunately we've had to deal with addresses that contain apostrophes like april.o'[email protected]. We initially just added it as a character but when forward slashes also caused problems (srs uses base64 encoding) so we ultimately enabled CHKUSER_STARTING_VARIABLE to let us bypass chkuser completely. This time around I plan to just set CHAR_9 to '\'' and cross my fingers. > > And secondly the srs-qt-0.5 patch included in qmailtoaster has a serious >> bug and we need at least the 0.6 patch. In the past I did this by >> manually installing the SRPMs, tweaking the spec, and rebuilding the >> binary RPMs. How do I do this using QTP? >> > > That's not the patch which is presently being used. Here's the srs patch > which QMT uses now: > Marcelo Coelho - qmail-srs-0.4.patch > http://opensource.mco2.net/**qmail/srs/<http://opensource.mco2.net/qmail/srs/> If I download http://mirror3.qmailtoaster.com/current/SRPMS/qmail-toaster-1.03-1.3.22.src.rpmit appears to have the 0.5 patch in there. Regardless, we need the bugfix added in version 0.6 of the patch. > > Any help will be greatly appreciated. >> > > The stock packages aren't quite ready for COS6 yet (I am working on it), > but there's no reason QMT can't be run on COS6. In fact, Dan has written a > script to aid in the installation process, which is available on this > list's archives: > http://article.gmane.org/**gmane.mail.qmail.toaster/**37705/match=<http://article.gmane.org/gmane.mail.qmail.toaster/37705/match=> > > Thank you, that looks like it will be very helpful. > For migrating from your old to your new server, qtp-backup and qtp-restore > are recommended. Depending on the amount of mail you have to migrate, you > might want to rsync the maildirs again after the initial migration to bring > things current. Also, be sure to use the latest qtp-restore that's in the > svn repo on the QTP web site, as it's been modified for COS6 but the > corresponding qmailtoaster-plus package including COS6 support hasn't been > cut yet. > > That's all that comes to mind right now. Let us know how you make out. > > P.S. Just curious to know, which version is your old QMT? > > It looks like right now we have 1.03-1.3.20 and no trace of qmailtoaster-plus.
