Hi,
This patch is for fetchmail in james-server_2_1_fcs as of 13:50 GMT,
15Sep2003.
It includes...
1) Documentation and Samples (at last!)
- xdocs
* now include fetchmail_configuration_2_2.xml
* documentation_2_1.xml updated to include the above
* fetchpop_configuration_2_1.xml includ
Hi!
I just had a look at the NotifySender family, which took me a while to get the idea.
Besides the available options for packaging the original message (ALL, BODY, ...), I
thought sending back the first lines should also be selectable, especially if there's
no size limit for a message.
Mark
Soeren Hilmer wrote:
I am looking at HEAD branch, FetchMail version 1.9.
HEAD branch should be the newest right? But it seams to be 4 months old, hmmm.
I cannot select any v. 2.2 branch though?
Please tell me what is going on here. The code you supply can be found under
2.1_fcs.
But according to
I am looking at HEAD branch, FetchMail version 1.9.
HEAD branch should be the newest right? But it seams to be 4 months old, hmmm.
I cannot select any v. 2.2 branch though?
Please tell me what is going on here. The code you supply can be found under
2.1_fcs.
But according to contributions patche
Soeren Hilmer wrote:
>
>
> Okay, it looks like FetchMail has a check for this that goes like:
>
> // if we are already fetching then just return
> if (fetching) return;
> fetching = true;
>
> ...
> fetching = false;
>
> May I suggest though the more robust sc
Soeren Hilmer wrote:
Okay, it looks like FetchMail has a check for this that goes like:
// if we are already fetching then just return
if (fetching) return;
fetching = true;
...
fetching = false;
May I suggest though the more robust scheme:
try
After some careful thought and good look through Darrell's code I think
I have most of the pieces I need.
However, I need to store attributes on the user for IMAP to work
properly.
These are two lists:
1) The list of current folders
2) The list of subscribed folders
As there is no place to store
Okay, it looks like FetchMail has a check for this that goes like:
// if we are already fetching then just return
if (fetching) return;
fetching = true;
...
fetching = false;
May I suggest though the more robust scheme:
try {
// if we