Yes, I followed this process. I created the zmfetchercfg file and made it executable, I used it to generate the my_fetchrc file and set that to chmod710, and I then tested it as described.

The original post seems to show that the fetchmail command should be executed from a folder with write permissions, so I made a folder called zimbra in /home and set the permissions on it to zimbra:zimbra. I did this as root. Then I changed to the zimbra user and moved into /home/zimba and typed in the fetchmail command there with the same results, an error about being unable to create a lock file.

It seems to want to create a lock file in /opt/zimbra/.fetchmail.pid this file does not exist when I look for it, so I cant change it's permissions to suit, nor does it seem I can change the location the file is created.

I have yet to set this up on a schedule as I need to ensure I've got it all right first.

I told it to use the zimbra user as this server is setup at home just for this purpose and no other users are configured. I'm also setting up one at work, but we are using smtp delivery for that and it works ok, so I'm pretty convinced the servers themselves are set right as I'm on the same learning curve on them both, the only difference is the ability to recieve mail from a remote pop3 server.

I told it to use the zimbra user as this server is setup at home just for this purpose and no other users are configured.

Sorry, perhaps I should have read your earlier post a bit more carefully. You do actually need a local user to collect the mail for. As you've already found out you can't write to the zimbra directory.

Thanks Phoenix, shortly after I posted I reconfigured the jobs via webmin to check using the root users and found it to work. I'll add a user for the task shortly.

So, POP3 email retrieval is now working fine, I'm happy with the speed too, I've set it to check every 3 minutes and considering that this one is running on an underpowered server, I'm very impressed.

If it matters to anyone, the home setup is using a Compaq 1600 rack server with 512MB ram and two PIII 550MHz chips, the work one is on 1GB Ram and a P4 3.6MHz chip, so quite a difference, but performance is similar (of course the work one will be supporting more users and a lot more email traffic)

Thanks all, it's a great product and although it's tricky to get it all working (when knowledge is limited) it's nice to get there eventually.

There are still a few teething problems though, so I'm sure I'll be back for more help soon

How to fix dates after fetchmail imports from POP3?

Thanks for these terrific instructions! Fetchmail seems just the ticket for importing POP3 mail for my migration from a post.office server. A test run of 10,000 messages ran very well.

However, I am now facing the date problem other people have mentioned -- messages are sorted in Zimbra with the timestamp of import and not the original message-received timestamp. I know that importing using imapsync from an imapserver can solve this with the syncdates option, but post.office doesn't have imap.

So how can I get fetchmail to set the date correctly? Perusing its manpage didn't reveal any option similar to imapsync's -syncdates option.