Il 04/06/2013 20:11, Sven Miller ha scritto:

On Tue, Jun 4, 2013 at 1:26 PM, Eric Shubert <[email protected] <mailto:[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).  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] <mailto: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.


I suggest to keep chkuser enabled and comment these lines in configuration:

/*    #define CHKUSER_RCPT_FORMAT */
/*    #define CHKUSER_SENDER_FORMAT */

Regards,

Tonino


--
------------------------------------------------------------
        Inter@zioni            Interazioni di Antonio Nati
   http://www.interazioni.it      [email protected]
------------------------------------------------------------

Reply via email to