Re: Prototype 51 Released!

> # Command line paramenters TAKE PRECEDENCE over .conf file values.

Yeah, I remember having read that...

> What it doesn't say but probably should is that the parameters that
> are not specified at the command line stay the same as specified in
> the configuration file. I thought it was evident but maybe it is not
> so for someone who hasn't actually coded YoSucker...

I think it says this somewhere...

> This said lets have a look at your example. You specified only one
> --config and that is OK, then you specify is only one --box=Bulk;
> Great! So why does YoSucker keep complaining?! I bet there is a
> DIGEST=Bulk in your ctubutis.conf file. As you haven't said anything
> about the DIGEST at the command line, YoSucker sees BOX=Bulk and
> DIGEST=Bulk. And that is not alright! So... All you have to do is to
> add --digest="" to your command line, that should do the trick!!! (at
> least I hope...:-)

Well...... I ran it once with both BOX and DIGEST configured in the
config file. Because I have YoSucker running in a cron job every 3
minutes, I then went and commented out the DIGEST parameter from the
config file, I didn't want any additional messages from the YoSucker
Olympics Team telling me about new SPAM that had just come in, not until
I had first dealt with what I already knew about. I then ran the example
I sent yesterday to which it got upset. :) But adding the '--digest=""'
parameter seems to have sucked down 13 new messages (though I thought
there should have been 14, maybe one of 'em was purged overnight by
Yahoo or something).

OK, that much worked. But even thought I said '--bulk=1' the messages
are still in my Bulk box on Yahoo.

And, ya know what? So are two new ones that came in overnight. If
specifying '--bulk=1' results in all messages in the Bulk folder being
removed, then I wouldn't have the opportunity to have known about
'em. Though this would be stupid on my part, performing different
aspects of the operation several hours from each other; of course things
are going to change over that time. But things can change over the
course of a minute, too. So specifying it like that probably isn't a
good thing in my case. So, can I specify something like LEAVE=0 to move
to Trash only those messages which have been sucked down from the Bulk
box? Um, I kinda suspect not, I seem to remember that LEAVE parameter
causing problems from the start, it seemed to globally affect
everything. I guess what we need are separate LEAVEs that apply to each
BOX/DIGEST.

I'll bet the juices in your brain are flowin'.......... =)

ct



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/