> I intend to switch the incoming mail inboxes on the system I am administering
> to the alternative mix format. I compiled and installed imapd 2007a and it
imap-2007b has been released so you should consider installing that.
> works fine, but there is one feature that I was not able to use. Mailboxes in
> the mix format (or any alternative format) are recognized, but the messages
> from the Unix mail spool are not snarfed into these mailboxes. On the other
What does MAILSPOOL say during your build? You should find that it's one
of the command line compiler defines echoed to OSCFLAGS. Is it correct?
> hand, pine 4.64 is able to snarf messages from the mail spool files into the
> alternative inboxes it recognizes, as stated in the documentation. The name a
> nd
> path for these inboxes were set according to the documentation (i.e., INBOX f
> or
> mix or mbox for mbox, placed in my home directory), but imap clients do not s
> ee
> them as inboxes.
What, exactly, have you modified for your imap-uw build? The software as
packaged defaults to the user's homedir for "non-spool" INBOXes, so you
should not have set anything to achieve this.
> I know that tmail delivery is a better alternative, but for the moment, lacki
> ng
> a test system, I have to resort to a gradual and maybe partial migration of t
> he
> mailboxes.
In my opinion snarfing is a fine way to do things at first. tmail or dmail
can be introduced at any time since even once they're in use snarfing
will still bring across residual mail.
> The load on the system is not important, so snarfing should do the
> job. Besides, I am not sure that tmail works out of the box, and I kannot
> afford risky tests on a production system.
So far as I can tell tmail works perfectly. It is just appropriate
configuration of your MTA you need to worry about.
Cheers,
- Joel
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
