On 13/02/18 03:02 AM, Carlos E. R. wrote:
On 2018-02-13 03:50, Anton Aylward wrote:
On 11/02/18 05:54 PM, Carlos E. R. wrote:
You can see that in the rest of the thread. I wanted, and I got it done, to parse the fetchmail log from only a particular manual session. And as i run two concurrent fetchmails, I had to differentiate each one by its PID.
I can post the entire script if you are interested.
Well, I look at the man page for fetchmail and I see you can not only specify the config file on the command line but also the pid file.
Actually I'm more curious as to why you need to run two separate fetchmail processes.
Speed.
Ah. I'm still dubious.
One process fetches from gmail, which is an slow imap server, and another fetches from the rest, that are faster.
I use Thunderbird as my front end. It deals with about 40+ accounts. Almost all of my accounts, and that includes GMail -- which seems to be an obligatory account these days even if you don't use it very much -- are imap based. The one exception is a very old and very critical service at a server that deals only with POP. That, and that alone, I apply fetchmail on. Fetchmail pulls stuff from that old account, runs SpamAssassin -- since its been around for decades it has appeared on many spam distributions by now -- pushes the email through procmail which puts it into disk folders. LOTS OF THEM. I then run Dovecot locally and point it at those folders. Thunderbird runs imap to to talk to Dovecot. So Thunderbird run imap and imap only The overall strategy was to make the remote accounts do the work of email storage, I only download very specific mail items that I want to archive. They go into folders serviced by Doevcot. Speed? I never have problems with speed. Very occasionally I'll wake up the fetchmail daemon from its ten minute cycle.
Speed is more important when I don't have fetchmail running in a time loop, but manually when I want it.
That makes no sense to me. I'd have it running as a deamon with, perhaps, a shorter cycle, perhaps, or a longer cycle. The idea is 'don't forget to fetch mail'. If I need more urgency I can wake it up manually.
Another reason would be a busy server, fetching from hundreds of accounts.
That's not a problem for me. As I said, I run the accounts using imap; Thunderbird polls and the imao protocol indicates if there is any new mail without needing to fetch it. See https://busylog.net/telnet-imap-commands-note/#24 To be honest, Thunderbird doesn't give me the fine tuned imap access that is possible, but then I don't feel like writing my own MUA. Good enough for me. Oh, and there's also the IDLE command. Does Thunderbird use that? If your IMAP server supports that you don't have to manually check for new mail or have Thunderbird poll for new mail every x minutes. https://support.mozilla.org/en-US/questions/1115907 Yes, I see that my version does and I have it set on all my imap accounts. including Gmail. So, yes, I take a more hands-off approach . I'm one of the school of sysadmins who are lazy, make the software do the work without having to do the 'fiddly-bits'. I look at what you've described and blink and wonder why there isn't "one fetchmail process for each account". I just seems like too much work to me, which is why you you asked this question anyway. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org