yeah, true. the IMAP client might think all remote messages are gone, and then flush the local cache... not nice :)
then we just need the protocol handling part from Courier, and report an error message to the user immediately after connect. But anyway, Steven, why do you want to block pop/imap on a hotspot? ----- Original Message ---- > From: Marc SCHAEFER <schae...@alphanet.ch> > To: Stanislav Sinyagin <ssinya...@yahoo.com> > Sent: Saturday, May 16, 2009 6:26:58 PM > Subject: Re: [swinog] special mail solution? > > On Fri, May 15, 2009 at 11:56:50AM -0700, Stanislav Sinyagin wrote: > > then the daemon will report an error when trying to delete the message. > > As it's a hotspot device, we don't want its syslog overflown with such > things:) > > The whole idea seems wrong, because you will be messing with the user > agent message counter/message ID. > > Aka the user agent will think the new state of the mailbox is the one > you present, which might have mild implications with POP, but big ones > with IMAP. > > Just have an error message. _______________________________________________ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
