John Pettigrew wrote:
In a previous message, Oskar Teran wrote:
the server fetchmail is bringing the emails to!! it seems you may need to do some reading...you sound like you're new at this. this setup you require is very common....
IIUC, you are saying that fetchmail can act as an IMAP server to the LAN. no, the same server you have fetchmail running on can also run an imap server using postfix or sendmail for example. easy imap daemon : uw-imap - it comes standard with most linux distros now, but it's not meant for heavy usage (production). For a home email box, this should be sufficient.
better imap daemons : courier or cyrus - these not as easy to setup as uw-imap, but they are better for a heavy mail server (production). For home, they would work, but probably overkill. However, if you have the time, go for it!
This is at odds with what I am reading in the man page and on the fetchmail website. For example, "Fetchmail retrieves mail from remote mail servers and forwards it via SMTP". From what I have read, it sounds like fetchmail can *retrieve* email using IMAP (or POP3 etc.) but *serves* it using SMTP. What I need is something that *serves* email by IMAP.
I know that it could deliver email to an imap daemon - this is mentioned in the docs that I'd already read before asking the original question. What I want to know is, what's a good and easy-to-configure IMAP daemon?
Dead giveaway that fetchmail isn't what I need - even in daemon mode, it is sleeping, merely awaking every so often to query servers and deliver email. What I need is a continually active service that is listening for incoming IMAP connections.
Or have I completely missed the point?
John