Thanks jake, This looks exactly what i needed. I think ( or so I think ) that I didn't see an answer the last time ( Oct 5 , 2007 ) cause I kept the thread... and here is something that may mean zero ... but the last time this lady had this same problem it was a friday and the same time of day ..... isn't that...interesting...
Thanks again! ----- Original Message ----- From: Jake Vickers To: [email protected] Sent: Friday, October 26, 2007 1:06 PM Subject: Re: [qmailtoaster] I hate Blackberry , 5.1.0 - Unknown address error 571-'sorry, (#5.7.1 - chkuser)' Jim Shupert, Jr. wrote: Friends, I have a blckberry user who has the complaint of 5.1.0 - Unknown address error 571-'sorry, sender address has invalid format (#5.7.1 - chkuser)' I find this in the wiki I got tired of adding a new Blackberry server every couple days so I just disabled the check for all incoming mail: :allow,BADMIMETYPE="",SENDER_NOCHECK="1",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan" my Q is this : 1.Is it generally agreed that "disabling the check for all incoming mail" is a good solution? best solution? 2. are there any - risks downsides? 3. ( most importantly )if I wish to disabled the check for all incoming mail :allow,BADMIMETYPE="",SENDER_NOCHECK="1",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan"exactly how do I do that? meaning do i just open a terminal as root and enter :allow,BADMIMETYPE="",SENDER_NOCHECK="1",BADLOADERTYPE="M",CHKUSER_RCPTLIMIT="50",CHKUSER_WRONGRCPTLIMIT="10",QMAILQUEUE="/var/qmail/bin/simscan" and hit enter ... or do i write that to a config somewhere? and for what it is worth ... I have several blackberry users , only 1 has had this problem ( same lady ) and it comes and goes ... well it's back now... ( and she is a dream to deal with :) Didn't I answer this one for you a while back? Enter the :allow line in your /etc/tcprules.d/tcp.smtp file, and then run 'qmailctl cdb'. In theory there can be security risks by allowing /'s and other characters, but in practice I have not been able to exploit them. Doesn't mean it can't be done though. And don't feel alone. It's only the REAL complainers that get this problem!
