On Thu, 17 Mar 2005, Mark Crispin wrote:
In order to create mailboxes within a mailbox, you need to use a mailbox
format which supports this "dual-use".
mbx format is not such a format; nor is traditional UNIX mailbox format.
The dual-use mailbox formats supported in the distribution version of
On Tue, 21 Dec 2004, Erich Beyrent wrote:
I am running FreeBSD 5.3 and have built the latest version of imap. My
problem is that I cannot seem to get IMAP to download any messages to my
Outlook client. POP3 is working correctly - in my $HOME directory, I have a
.mail file containing all the messa
On Mon, 6 Dec 2004, Andrew Biggs wrote:
I'm just getting started using c-client, and was
trying to use mtest to talk to an IMAP server on
another box. Looking at the code, it's not real clear
to me how to specify the remote address, username,
password, etc. I didn't see any readme's, FAQ's, or
ho
On Wed, 1 Dec 2004, Mark Crispin wrote:
On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote:
... but - are you saying that I don't even need to change into HALFOPEN
mode in order to be able to append messages to any kind of mailbox without
the "Status: O" flag being set?
On Wed, 1 Dec 2004, Mark Crispin wrote:
On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote:
I'm looking at messages in readonly mode in order to determine which ones
need to be synchronized between two sites.
Then I'm flagging those as deleted that have been removed on one s
On Wed, 1 Dec 2004, Mark Crispin wrote:
On Wed, 1 Dec 2004, Tomas Pospisek's Mailing Lists wrote:
I've got reports [1] against Debian's version of c-client 2002e that when
opening a stream, that is not OP_HALFOPEN (such as OP_READONLY or NIL),
c-client will actually close and
I've got reports [1] against Debian's version of c-client 2002e that when
opening a stream, that is not OP_HALFOPEN (such as OP_READONLY or NIL),
c-client will actually close and open the stream again (thus requiring the
user to re-authenticate).
Is this:
* a known problem?
* a feature with a r
On Fri, 11 Jun 2004, Mark Crispin wrote:
> On Fri, 11 Jun 2004, Tomas Pospisek's Mailing Lists wrote:
> > *Is* the mh driver "strictly IMAP semantics compiant" right now? Is the
> > fact that a) it forgets about all the flags and b) when reusing an open
> >
On Fri, 11 Jun 2004, Mark Crispin wrote:
> On Fri, 11 Jun 2004, Tomas Pospisek's Mailing Lists wrote:
> > The problem I'm fighting against here is that when reopening a connection
> > the c-client's mh driver will loose knowledge of which messages were
&g
On Thu, 10 Jun 2004, Mark Crispin wrote:
> mh is a dead format. The only purpose to support it is for compatibility
> with the past; and without that compatibility it isn't worth supporting.
Allthough mailsync beeing a tiny little tool lost somewhere in the huge
masses of OSS I do have 2-3 users
On Thu, 10 Jun 2004, Mark Crispin wrote:
> On Thu, 10 Jun 2004, Tomas Pospisek's Mailing Lists wrote:
> > But I don't understand what would be required to fix it. I can't see
> > the big picture. AFAI can see mh_ping is not changing the status of
> > messa
On Wed, 9 Jun 2004, Tomas Pospisek's Mailing Lists wrote:
> Second question:
> some of my MH users say that re-mail_open'ing a MH store will make it
> forget all all removal flags.
>
> Is this a known bug/problem/feature. Is there a work around or should I
>
Since Mark seems to be listening on the list, but there's no reply yet:
let's make the requirements a bit lighter and ask some more specific
questions. I'll cut this email in two, since it is two different
questions actually.
On Wed, 9 Jun 2004, Tomas Pospisek's Mailing Lists
I'm trying to fix mailsync a mail synchronizer to properly work wrt to
flags. I'm trying to accomplish this by using c-client.
I need to:
* read the headers in box A
* read the headers in box B
* determine from the header which emails I have already seen in what
inbox (same algorithm CVS is usi
On Wed, 10 Dec 2003, Erik Berls wrote:
> I've looked through the mail archives and I've seen support issues
> for MH folders come up numerous times.
>
> I was wondering if anyone had patches that implemented the ability
> to maintain the read/un-read status of messages. Ideally, I would
> prefer
Is there any specific reason, c-client calls the mh inbox #mhinbox and not
INBOX like all the other INBOXes of all the other formats?
It's inconvenient as would force me to do #mhinbox<->INBOX mapping in
mailsync if I wanted to do things properly.
?
*t
--
---
On Thu, 27 Feb 2003, Friedrich Lobenstock wrote:
> Tomas Pospisek's Mailing Lists wrote:
> >
> > You can f.ex synchronize your folders between various workstations. Which
> > you can't with POP.
>
> YES you are right _folders_. BUT the orginal poster wanted on
On Thu, 27 Feb 2003, Friedrich Lobenstock wrote:
> Tomas Pospisek's Mailing Lists wrote:
> > On Wed, 26 Feb 2003, Friedrich Lobenstock wrote:
> >
> >>If the users can only have their INBOX on imap but not any other
> >>folders what do they gain from this ch
On Wed, 26 Feb 2003, Friedrich Lobenstock wrote:
> If the users can only have their INBOX on imap but not any other
> folders what do they gain from this change.
They can move mails back and forth to and from the server, which is
impossible with pop.
*t
--
---
I'm trying to sync mail from an IMAP server to a /var/spool/mail/mbox [1].
The problem is, that mail_append[_full] will allways add a
Status: O
to the mail, even if I pass an empty string to the function as "flags".
The problem with this is that the mutt MUA interprets Status: O as an o
20 matches
Mail list logo
