Ebroch: Created page with "== Intro == This tip is simply a step by step to recompile chkusr to allow the '/' character. == Why? == (PULLED FROM: [http://wiki.qmailtoaster.com/index.php/FAQs#I_keep_getting_.225.1.0_-_Unknown_address_error_571-.27sorry.2C_sender_address_has_invalid_format_.28.235.7.1_-_chkuser.29.27.22_errors.2C_especially_from_people_with_Blackberry_devices._What_can_I_do.3F This FAQ] ) I keep getting "5.1.0 - Unknown address error 571-'sorry, sender address has invalid format..."

2024-03-16T16:48:58Z

Created page with "== Intro == This tip is simply a step by step to recompile chkusr to allow the '/' character. == Why? == (PULLED FROM: [http://wiki.qmailtoaster.com/index.php/FAQs#I_keep_getting_.225.1.0_-_Unknown_address_error_571-.27sorry.2C_sender_address_has_invalid_format_.28.235.7.1_-_chkuser.29.27.22_errors.2C_especially_from_people_with_Blackberry_devices._What_can_I_do.3F This FAQ] ) I keep getting "5.1.0 - Unknown address error 571-'sorry, sender address has invalid format..."

New page

== Intro ==
This tip is simply a step by step to recompile chkusr to allow the '/' character.

== Why? ==

(PULLED FROM: [http://wiki.qmailtoaster.com/index.php/FAQs#I_keep_getting_.225.1.0_-_Unknown_address_error_571-.27sorry.2C_sender_address_has_invalid_format_.28.235.7.1_-_chkuser.29.27.22_errors.2C_especially_from_people_with_Blackberry_devices._What_can_I_do.3F This FAQ] )

I keep getting "5.1.0 - Unknown address error 571-'sorry, sender address has invalid format (#5.7.1 - chkuser)'" errors, especially from people with Blackberry devices. What can I do?

The sender is using an illegal character. In Blackberry's case they're using a spam firewall that uses the slash character (/) in the sending email address when messages are sent from the Blackberry device, regardless of the reply-to address. To work around this you can either recompile chkuser to allow for the illegal character, or turn off chkuser checks for their mail servers.

So in this tip we are opting for the recompile. The reason I usually choose this one is simply because the blackberry servers can change IP's. This is more of a "blanket" method. I personally have found it more reliable for this kind of instance.

== Precautions ==

* Keep in mind that anytime you update your system with newer versions, that this setting will be reset to the default. So if the main qmail-toaster* package is updated - you need to do this process again.
* Since this process usually is hand in hand with an update, keep in mind that if you have spamdyke installed to be sure after the operation that your /var/qmail/supervise/smtp/run file still has spamdyke in it.
* New certificates will be created - below is the output from the rpm update command:
<code>qmail-toaster warning: /var/qmail/control/servercert.pem created as /var/qmail/control/servercert.pem.rpmnew</code>

So if you have any custom certificates or commercial ones, you may want to back them up prior to the process.

== Step by Step ==

Much of this process is derived from this wiki [http://wiki.qmailtoaster.com/index.php/Chkuser entry].

* Make sure that your toaster is completely up to date to avoid having to do this process all over when you realize that. We start with updating QmailToaster-Plus. If you do not have it installed, do so. Head over to the ( [http://qtp.qmailtoaster.com/trac QTP website] for instructions on how to do that). Assuming it is installed, we start with:
<code>
yum update qmailtoaster-plus
</code>
* Update the rest of the toaster packages with the newmodel script included in the QmailToaster-Plus menus.
<code>
qtp-menu
</code>
* Move into the working directory for the SRPMS from your original install.
<code>
cd /usr/src/redhat/SRPMS
</code>
* Check the version of qmail-toaster installed.
<code>
rpm -qa | grep qmail-toaster
</code>
* Get the matching SRPM from the toaster site (you will need to update below link for your version).
<code>
wget http://www.qmailtoaster.com/download/stable/qmail-toaster-1.03-1.3.18.src.rpm
</code>
* Install the proper SRPM.
<code>
rpm -Uvh qmail-toaster*.src.rpm
</code>
* Move to the SPEC directory.
<code>
cd /usr/src/redhat/SPECS
</code>
* Edit qmail-toaster.spec (I use VI. Sub for your favorite CLI editor). find 'sleep 5' (should be line 606). change 5 to 300 (5 seconds to 300 seconds). save.
<code>
vi qmail-toaster.spec
</code>
* Rebuild the RPM. Keep in mind that in future versions or architectures of CentOS that the --with flag value 'cnt50' might need an updated value). You will also need to sub that flag value if you are using another type of system such as Fedora, etc.
<code>
rpmbuild -bb --with cnt50 qmail-toaster.spec
</code>
* When the build process pauses, open another terminal and edit /usr/src/redhat/BUILD/qmail-1.03/chkuser_settings.h to your liking. You have 5 minutes (or whatever you changed the sleep parameter to). Save your changes and wait for the 300 seconds to expire and watch it build.
<code>
vi /usr/src/redhat/BUILD/qmail-1.03/chkuser_settings.h
</code>
* Search for "CHKUSER_ALLOW_SENDER_CHAR"
* Uncomment and change it from:
<code>
/* #define CHKUSER_ALLOW_SENDER_CHAR_3 '' */
</code>
* To:
<code>
#define CHKUSER_ALLOW_SENDER_CHAR_3 '/'
</code>
* Save and exit.
* Once the pause expires, the compile will continue.
* Once the compile is done (there were no errors right?) move to the RPM directory.
<code>
cd /usr/src/redhat/RPMS/i386/
</code>
* Stop Qmail.
<code>
qmailctl stop
</code>
* Upgrade the Toaster package.
<code>
rpm -Uvh --replacefiles --replacepkgs qmail-*.rpm
</code>
* Copy back any custom certificates you had backed up at the beginning (if you did so).
* Restart Qmail.
<code>
qmailctl start
</code>
* Is it all running?
<code>
qmailctl stat
</code>

== Finito ==
You should now be all done and up and running again and the Blackberry users should be able to function as needed.

---

[http://www.interazioni.it/opensource/chkuser/ chkuser site]

CHKUSR - Enable characters for Blackberry devices - Revision history