Marius Micluta | 10 Jun 16:38

imapd snarfing to mix formatted inbox


Although this list seems almost inactive since Mark Crispin's regrettable 
departure, I place my query here with the hope of a reply from the users' 
community. I also sent a message to the alpine-contact address listed by Mark 
in his last message, but no reply followed.

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
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
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 and
path for these inboxes were set according to the documentation (i.e., INBOX for
mix or mbox for mbox, placed in my home directory), but imap clients do not see
them as inboxes. On the contrary, pine run directly on the mail server detects
these mailboxes as inboxes and snarfs the messages from the mail spool.

I know that tmail delivery is a better alternative, but for the moment, lacking
a test system, I have to resort to a gradual and maybe partial migration of the
mailboxes. 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.

Marius Micluta

Institute of Biochemistry of the Romanian Academy
Splaiul Independentei 296
060031 Bucharest
ROMANIA
(Continue reading)

Joel Reicher | 11 Jun 14:56

Re: imapd snarfing to mix formatted inbox

> 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.
(Continue reading)

Marius Micluta | 11 Jun 18:25

Re: imapd snarfing to mix formatted inbox


Thank you very much, Joel, for your reply and for the good news.

> imap-2007b has been released so you should consider installing that.

I already downloaded and installed it; it works great out of the box!

> 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.

My previous build was OK, I only changed path names to match my system, but my
pine/alpine remote configuration file was wrong. The inbox-path was
{imap.server}~/INBOX instead of just {imap.server}INBOX. I have set it so to
test the mix driver, but thereafter I forgot about the magic of the INBOX name.
Thank you for pointing me out this detail.

> 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.

This is also the roadmap I planned.

> So far as I can tell tmail works perfectly.

Now I am more confident and I will give tmail a trial after migrating the 
inboxes to the mix format.

> It is just appropriate configuration of your MTA you need to worry about.

(Continue reading)

Joel Reicher | 12 Jun 05:01

Re: imapd snarfing to mix formatted inbox

> My previous build was OK, I only changed path names to match my system, but m
> y
> pine/alpine remote configuration file was wrong. The inbox-path was
> {imap.server}~/INBOX instead of just {imap.server}INBOX.

What was probably happening is that imapd was interpreting "~/INBOX" as
a custom mailbox name rather than the special name "INBOX", and so the
snarfing wasn't triggered.

I take it the snarfing is now happening since you fixed this?

By the way, I'm pretty sure all you need is "{imap.server}" since "INBOX"
should be the default mailbox.

Cheers,

	- Joel
_______________________________________________
Imap-uw mailing list
Imap-uw <at> u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw

Marius Micluta | 12 Jun 17:54

Re: imapd snarfing to mix formatted inbox

On Thu, 12 Jun 2008, Joel Reicher wrote:

> What was probably happening is that imapd was interpreting "~/INBOX" as
> a custom mailbox name rather than the special name "INBOX", and so the
> snarfing wasn't triggered.

Yes, this was indeed my problem. The special name INBOX looses its magic 
behavior if prefixed by "~/". At least for uw-imapd, "INBOX" means by default 
spool inbox AND non-spool home directory-based inboxes, as you already 
mentioned. The imapd server recognizes them both, if present, and messages 
are snarfed automagically. It is an easily overlooked subtlety, so it is 
worth outlining it here, as it is maybe not obvious from the documentation.

> I take it the snarfing is now happening since you fixed this?

It works like a charm, out of the box.

> By the way, I'm pretty sure all you need is "{imap.server}" since "INBOX"
> should be the default mailbox.

Indeed, default names work pretty well with uw-imapd. but it might not be true 
for other IMAP servers. A somewhat more complex .pinerc file is prone to 
mistakes and fixing it is a matter of trial and error, where client-side 
idiosyncrasies add to IMAP server peculiarities. A little out of topic, I 
found that having an uw-imap server listening on both ports 993 and 143 with 
TLS negotiation enabled, I am able to access the mailboxes from a pine 4.64 
client with both the {imap.server/tls} and {imap.server/ssl} configuration 
options, while the remote address book is only accessible if prefixed with 
{imap.server/ssl}. In alpine, {imap.server/tls} also works for the remote 
address book.
(Continue reading)

Andrew Laurence | 12 Jun 19:48

Re: imapd snarfing to mix formatted inbox

At 10:56 PM +1000 6/11/08, Joel Reicher wrote:
>  > 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.

Given Mark's departure, what does this release constitute?  Is it 
more than the last development tarball?   Does it contain Mark's 
"last final bits"?  Does it contain someone else's bits?

-Andrew

At 2:44 PM -0700 5/20/08, Mark Crispin wrote:
>Unfortunately, I didn't get a change to push imap-2007b out the door 
>in release status, but the development tarball there is pretty close 
>to my final bits.

Steve Hubert | 12 Jun 20:13

Re: imapd snarfing to mix formatted inbox

On Thu, 12 Jun 2008, Andrew Laurence wrote:

> At 10:56 PM +1000 6/11/08, Joel Reicher wrote:
>>  > 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.
>
> Given Mark's departure, what does this release constitute?  Is it more than 
> the last development tarball?   Does it contain Mark's "last final bits"? 
> Does it contain someone else's bits?
>
> -Andrew
>
>
> At 2:44 PM -0700 5/20/08, Mark Crispin wrote:
>> Unfortunately, I didn't get a change to push imap-2007b out the door in 
>> release status, but the development tarball there is pretty close to my 
>> final bits.

It is Mark's last final bits with no one else's bits. It is what he said 
should be called 2007b.

Steve Hubert <hubert <at> washington.edu>
Univ. of Washington Technology Services, Seattle
_______________________________________________
Imap-uw mailing list
Imap-uw <at> u.washington.edu
(Continue reading)

Oscar del Rio | 12 Jun 16:05

Re: imapd snarfing to mix formatted inbox

Marius Micluta wrote:
> 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
> 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
> 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 and
> path for these inboxes were set according to the documentation (i.e., INBOX for
> mix or mbox for mbox, placed in my home directory), but imap clients do not see
> them as inboxes. On the contrary, pine run directly on the mail server detects
> these mailboxes as inboxes and snarfs the messages from the mail spool.

How did you create the INBOX?  It should be with "mailutil", specifying
the desired format (e.g. #driver.mix/INBOX), instead of just "touch ~/INBOX"

_______________________________________________
Imap-uw mailing list
Imap-uw <at> u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw

Marius Micluta | 12 Jun 18:08

Re: imapd snarfing to mix formatted inbox

On Thu, 12 Jun 2008, Oscar del Rio wrote:

> How did you create the INBOX?  It should be with "mailutil", specifying
> the desired format (e.g. #driver.mix/INBOX), instead of just "touch ~/INBOX"

The inbox was created correctly, by conversion with mixcvt (the recommended 
way). I also used mailutil during the tests. The clue was that I addressed it 
as "{imap.server}~/INBOX" instead of "{imap.server}INBOX", or simply 
"{imap.server}". Problem solved, thanks to Joel Reicher's generous help.

I also thank you for your reply.

Marius Micluta
_______________________________________________
Imap-uw mailing list
Imap-uw <at> u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw


Gmane