After a few weeks of implementing and teting I've got Dovecot, Dovecot's delivery, and Dovecot's sieve integration all working.
I've got an archive of years of email in 'the cloud" (one on of my own servers for the moment). Now I'm trying to decide on the architecture of the current store. My goal is to use my desktop, my laptop, my netbook, even my tablet, to read email depending on circumstances, and to send email as well. My support staff is being switched from pooled reading of the support email to a ticket system. I'm currently using lots of different email addresses, and I sort quite a bit based on incoming email. I have for example, mybusinessemail@, mypersonalemail@, individualvendor@, magazinesubscriptions@, and the like. And to make it even more complex, we've got a bunch of domain names, which we inherited when we bought up small failing hosting companies. Two thoughts come to mind: business.stuff@, personal.stuff@, vendor.stuff@, magazine.stuff@, all for only one domain, and other email addresses as forwarders, temporarily, until we can get rid of them. Or one.email.addr...@one.example.com with everything else forwarded to it. This would give me (I think) an easier file store to navigate; imap otherwise will give me multiple inboxes, sent messages, spam folders, and the like. Do you have any experience with either of these, or with something I haven't thought of? Your notes, suggestions, and experiences appreciated. Thanks. Jeff -- Post Office Box 52200, Riverside, CA 92517 My jplists address used on lists is for list email only Phone +1 909 266-9209 _______________________________________________ LinuxUsers mailing list LinuxUsers@socallinux.org http://socallinux.org/cgi-bin/mailman/listinfo/linuxusers
