All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Campbell <campbell@accelinc.com>
To: urgrue <urgrue@tumsan.fi>
Cc: linux-admin@vger.kernel.org
Subject: Re: switching to mbx problems
Date: Wed, 4 Jun 2003 09:08:58 -0500	[thread overview]
Message-ID: <20030604090857.A9992@helium.inexs.com> (raw)
In-Reply-To: <20030604131623.GA24291@fede2.tumsan.fi>; from urgrue@tumsan.fi on Wed, Jun 04, 2003 at 04:16:23PM +0300

Well,
I did a quick look and found nothing in the procmail docs about mbx.  I did
a google search on "procmail mbx" and found that the short answer is 
no native procmail support for mbx format because:
  1)It is not a documented format.
  2)Someone would have to reverse engineer it to write code to support it.


I do not claim to speak for the developers.  Check with the procmail mailing 
list to be sure.

-chuck


On Wed, Jun 04, 2003 at 04:16:23PM +0300, urgrue wrote:
> im wanting to switch my mailboxes over from generic crappy unix format 
> to mbx.
> ive compiled a newer imap and pop daemon, and converted some test boxes 
> over to mbx. i can successfully read from them.
> 
> but then they break. i figure that when new mail gets delivered, my 
> procmail is just writing to the mailbox as if it was the same old unix 
> format, which creates a hybrid starts-out-as-mbx-ends-as-unix mailbox. 
> which nobody can read.
> 
> procmail doesnt seem to be mbx aware, yet ive seen claims that mbx is 
> the current preferred mailbox format. 
> can i get procmail to handle mbx? if not, any suggestions?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
ACCEL Services, Inc.| Specialists in Gravity, Magnetics |  1(713)993-0671 ph.
 2401 Fountain View |   and Integrated Interpretation   |  1(713)993-0608 fax
     Suite 900      |                                   |
 Houston, TX, 77057 |          Chuck Campbell           | campbell@accelinc.com
                    |  President & Senior Geoscientist  |

     "Integration means more than having all the maps at the same scale!"

  parent reply	other threads:[~2003-06-04 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-04 13:16 switching to mbx problems urgrue
2003-06-04 13:35 ` urgrue
2003-06-05  0:21   ` paul niemandt
2003-06-05  5:25     ` James Turnbull
2003-06-05 11:01       ` urgrue
2003-06-05 20:10         ` Glynn Clements
2003-06-05 23:25         ` James Turnbull
2003-06-04 14:08 ` Chuck Campbell [this message]
2003-06-04 14:40 ` Chuck Campbell
2003-06-04 16:15   ` urgrue
2003-06-04 20:25     ` RH 9 and Toshiba Satellite 2545XCDT Stephen Satchell
2003-06-04 21:24       ` Aaron Baer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030604090857.A9992@helium.inexs.com \
    --to=campbell@accelinc.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=urgrue@tumsan.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.