I just used that file over the weekend, and it worked fine for me.
Does your /var/qmail/doc/chkuser_settings.h file contain:
#define CHKUSER_ALLOW_SENDER_CHAR_3 '/'
? If so, then the fixed version is installed. If not, then you may have
neglected to delete the original srpm before wget'ing the new one.
Here's the md5sum for the modified srpm:
7c3225ec4515fdc18d4a60b6d3ff7fd4 qmail-toaster-1.03-1.3.20.src.rpm
--
-Eric 'shubes'
Maloupi wrote:
i run qtp-newmodel and it changes nothing.
i still have a reject :
11-30 22:11:18 CHKUSER rejected sender: from
<SRS0=t/hbT/[email protected]::>
remote <smtp01.bis.eu.blackberry.com:unknown:216.9.253.48> rcpt <> :
invalid sender address format
11-30 22:11:25 tcpserver: end 9425 status 0
11-30 22:11:25 tcpserver: status: 0/100
11-30 22:11:32 tcpserver: status: 1/100
11-30 22:11:32 tcpserver: pid 9440 from 206.53.150.101
11-30 22:11:32 tcpserver: ok 9440 ns24230.ovh.net:91.121.19.20:25
:206.53.150.101::5203
11-30 22:11:33 CHKUSER accepted null sender: from <::> remote
<smtp05.bis.eu.blackberry.com:unknown:206.53.150.101> rcpt <> : accepted
null sender always
11-30 22:11:33 CHKUSER accepted rcpt: from <::> remote
<smtp05.bis.eu.blackberry.com:unknown:206.53.150.101> rcpt
<[email protected]> : found existing recipient
11-30 22:11:33 policy_check: local -> local [email protected]
(UNAUTHENTICATED SENDER)
11-30 22:11:33 policy_check: policy allows transmission
11-30 22:11:38 tcpserver: end 9440 status 0
I get the file you told me
(http://qtp.qmailtoaster.com/repos/SRPMS/qmail-toaster-1.03-1.3.20.src.rpm)
and put it in /usr/src/qtp-upgrade/SRPMS/ and run it as you said but
nothing changed.
Are you sure it is the good file (same name, same size) ?
Jake Vickers a écrit :
Eric Shubert wrote:
Maloupi wrote:
Hi,
Some of my user are using a blackberry and one of them can't use it
because chkuser reject his mails :
invalid sender address format
After looking in the archive of this list, i tried to add
CHKUSER_ALLOW_SENDER_CHAR_3="/" in tcp.smtp
and do after qmailctl cdb
but it does not work.
This is my tcp.smtp file :
127.:allow,RELAYCLIENT="",DKSIGN="/var/qmail/control/domainkeys/%/private",NOP0FCHECK="1"
:allow,BADMIMETYPE="",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",DKSIGN="/var/qmail/control/domainkeys/%/private",CHKUSER_ALLOW_SENDER_CHAR_3="/",NOP0FCHECK="1"
What's wrong please ?
---------------------------------------------------------------------------------
I'm guessing that since the variable is commented out, it doesn't
exist, so cannot be changed (We're not real certain about how chkuser
is handling this).
http://qtp.qmailtoaster.com/repos/SRPMS/qmail-toaster-1.03-1.3.20.src.rpm
is a version of the package that contains the / character for
chkuser. This is the only change in it from the stock package.
Download (wget) it into /usr/src/qtp-upgrade/SRPMS/ (don't forget to
remove the existing package there first), then run qtp-newmodel and
have it rebuild the qmail-toaster package. That'll fix you up.
Jake, please refresh my memory. Why is it that this '/' character
hasn't been added to the stock package? It's becoming a real PITA for
me as well as others. ;)
It's going to be in the next release. I've patched it in a while back,
but have not wanted to make a new release for a minor update. Since
I'm working on adding Mandriva 2010 and Fedora 12 support, when that
update comes out (soon!) it will include the "/" character. Someone
will need to go and edit all the references to changing this to
reflect the fact that it's now defaulted.
---------------------------------------------------------------------------------
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
