yes, good point. I've updated the POD docs now for 3.3.0. --j.
On Wed, Jan 13, 2010 at 09:01, Cecil Westerhof <ce...@decebal.nl> wrote: > In the thread: > http://osdir.com/ml/debian-bugs-closed/2009-08/msg01318.html > > Error code 98 is described as the message being fed being to big and the > problem resolved. But it is not. > > I have a big message: > -rw-r--r-- 1 imaps users 1,4M 2010-01-11 18:05 > 1263235863.M361818P11014V0000000000000303I00D10102_0.Asterisk,S=1406379:2,S > > When feeding it to spamc with: > spamc -L spam > <toProcess/1263235863.M361818P11014V0000000000000303I00D10102_0.Asterisk,S=1406379:2,S > > I get a return code of 98 and this breaks my crontab job. I now solved > this by: > set +e > message=$(spamc -L ${typeStr} <${toProcessSpamDir}${i}) > errorCode=${?} > set -e > case ${message} in > 'Message successfully un/learned') > let "++learned" > ;; > 'Message was already un/learned') > let "++notLearned" > ;; > *) > let "++error" > case ${errorCode} in > 98) > echo "${i} was to big to be processed" > ;; > *) > echo "unknown error (${errorCode})" > ;; > esac > ;; > esac > > But I think this should be documented. (With other undocumented errors > if there are.) > > -- > Cecil Westerhof > Senior Software Engineer > LinkedIn: http://www.linkedin.com/in/cecilwesterhof > > -- --j.
