My company's mail server only keeps mail around for two months.

The common solution to this is to archive all of the mail on a client workstation, using a program like Outlook (egads!) or Thunderbird.

That's fine if you only have one client, but if you have ~5 devices from which you want to access mail, having the mail on some random GUI client doesn't fix your problem.

My idea is to create a mail flow like this:

(Corporate server) <--> (Team server) <--> (Clients)

Note: alternately, I could learn how to use mutt/alpine on the Team server, and just read my mail there, from a given client. That's OK, I guess, but not ideal.

Really, my question is about what to do on the Team server.

The desired functionality is:

- Regularly poll and download mail via IMAP/POP from the corporate server.
- Persist to an unrestricted mail store on the internal team server.
- Expose that same mail store as incoming mail via IMAP/POP, to n clients.
- Use team server as the first-class IMAP/POP server configuration for all of my clients.
- On a given client, use Thunderbird to read my mail.

What programs/approaches could I use to implement this? Note: team server does not run X.

It sounds somewhat like a "mail proxy" or "mail relay", but keep in mind that I have no control over the corporate server. My intermediary box needs to be both a client, and then a server. That said, it's been a few years since I put up a mail relay, or event thought about what that is.

Thank you.

This is a common setup.

Use fetchmail to pop you mail from a POP server. Store it locally using procmail, filtering is optional. Use Dovecot as IMAP server.

jlinkels

1 members found this post helpful.