Re: Problem with pine (i want to use mutt)
On 2000-03-22 16:52:46 -0500, Bennett Todd wrote: There's a pile o' problems here. They can all be summed up by "mbx". Yeah, another mailbox format. Is there a specification somewhere? Maybe we should add support _after_ 1.2 is out. (We have an IMAP bug open which will take a couple of days to be fixed.) -- http://www.guug.de/~roessler/
Re: Problem with pine (i want to use mutt)
At 10:23 +0100 23 Mar 2000, Thomas Roessler [EMAIL PROTECTED] wrote: On 2000-03-22 16:52:46 -0500, Bennett Todd wrote: There's a pile o' problems here. They can all be summed up by "mbx". Yeah, another mailbox format. Is there a specification somewhere? Maybe we should add support _after_ 1.2 is I did some looking around, and didn't find anything. From what I found, it looks like the closest thing to a specification is the c-client source. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald Knuth
Re: Problem with pine (i want to use mutt)
Hi all, I have solved the problem by using procmail, and I'm happily all after. CU -- \o/ Michael Thies --- [EMAIL PROTECTED] "Haben Sie sich an meine Anweisungen gehalten, als das Boot kenterte???" - "Nein, ans Boot..."
Re: Problem with pine (i want to use mutt)
On 2000-03-23 03:55:40 -0600, Aaron Schrab wrote: I did some looking around, and didn't find anything. From what I found, it looks like the closest thing to a specification is the c-client source. No, thanks. -- http://www.guug.de/~roessler/
Re: Problem with pine (i want to use mutt)
Mikko Hänninen hat ueber "Re: Problem with pine (i want to use mutt)" geschrieben: What's "pine-format"? Doesn't Pine use standard unix mbox files? Hmm? I don't know. If I use setting spoolfile, and/or starting mutt with "-f INBOX" I get INBOX is not a mailbox. Pine doesn't control the mail delivery, so nothing you can change in Pine will help. The delivery location is controlled by whatever mail delivery program is used (/bin/mail, procmail, the MTA's own, etc.) OK. I thought, that maybe pine is corrupting something in the system, maybe the sysadmin has done that. The INBOX-File has at the beginning two lines with *mbx* 38d90673 then 30 empty lines, an interessant line with the date: 22-Mar-2000 18:44:19 +0100,636;- and then the "normal" mail. Maybe it is a feature from tmail-4.1(10) or sendmail on this host. I will ask the sysadmin, but he is on vacation till end of march. thanx for all the answers -- \o/ Michael Thies --- [EMAIL PROTECTED] Der Physiklehrer möchte die Wirkung des Magneten erklären. Einleitend fragt er: "Was hebt Gegenstände vom Boden auf und fängt mit 'M' an?" - "Meine Mutter!"
Re: Problem with pine (i want to use mutt)
i know that it won't see it as a mailbox unless it is under the Mail directory... i create a mail directory for use in mutt, pine and netscape by doing this in my Msgs directory: touch mailbox ...and i have a symlink of Mail to Msgs directory for use with procmail...so it reads from this directory. I have a link to my inbox in the Msgs directory to my spooled maildirectory ln -s /var/spool/mail/$USER ~$USER/Msgs/inbox this seems to work very nicely --- /helfman "At any given moment, you may find the ticket to the circus that has always beenin your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private! - Original Message - From: Michael Thies [EMAIL PROTECTED] Date: Wednesday, March 22, 2000 12:02 pm Subject: Re: Problem with pine (i want to use mutt) Mikko Hänninen hat ueber "Re: Problem with pine (i want to use mutt)" geschrieben: What's "pine-format"? Doesn't Pine use standard unix mbox files? Hmm? I don't know. If I use setting spoolfile, and/or starting mutt with "-f INBOX" I get INBOX is not a mailbox. Pine doesn't control the mail delivery, so nothing you can change in Pine will help. The delivery location is controlled by whatever mail delivery program is used (/bin/mail, procmail, the MTA's own, etc.) OK. I thought, that maybe pine is corrupting something in the system, maybe the sysadmin has done that. The INBOX-File has at the beginning two lines with *mbx* 38d90673 then 30 empty lines, an interessant line with the date: 22-Mar-2000 18:44:19 +0100,636;- and then the "normal" mail. Maybe it is a feature from tmail-4.1(10) or sendmail on this host. I will ask the sysadmin, but he is on vacation till end of march. thanx for all the answers -- \o/ Michael Thies --- [EMAIL PROTECTED] Der Physiklehrer möchte die Wirkung des Magneten erklären. Einleitend fragt er: "Was hebt Gegenstände vom Boden auf und fängt mit 'M' an?" - "Meine Mutter!"
Re: Problem with pine (i want to use mutt)
Michael Thies [EMAIL PROTECTED] wrote on Wed, 22 Mar 2000: Mikko Hänninen hat ueber "Re: Problem with pine (i want to use mutt)" geschrieben: What's "pine-format"? Doesn't Pine use standard unix mbox files? Hmm? I don't know. It does, at least for the stored mail folders... When I've used it, anyway, a long long time ago. :-) If I use setting spoolfile, and/or starting mutt with "-f INBOX" I get INBOX is not a mailbox. The INBOX-File has at the beginning two lines with *mbx* 38d90673 then 30 empty lines, an interessant line with the date: 22-Mar-2000 18:44:19 +0100,636;- and then the "normal" mail. Okay, that's not the standard mbox mail format. So Mutt rightly says it can't read the folder. Mutt supports only 4 mail folder formats: standard unix mbox, Maildir, MH and MMDF. I don't think that you have any of those, though I don't know all the details of what MMDF is like. You need to have your incoming mail folder in one of the above recognised formats, before Mutt can read it. Maybe it is a feature from tmail-4.1(10) or sendmail on this host. I've never heard of tmail. I doubt sendmail is doing that on its own, although it could be invoking a separate mail delivery program that uses that format. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / "Personally, I want my computer's memory to be more reliable than mine." /.
Re: Problem with pine (i want to use mutt)
A-Ha! Found it! There are clues scattered about the netnews posting
I attach to this email.
There's a pile o' problems here. They can all be summed up by "mbx".
This is a special non-standard mailbox folder format, invented by
someone who thinks Maildir is a bad idea. That much can be said
objctively, and so I think I'll just stop there.
tmail appears to be the gizmo created to allow sendmail to deliver
directly into "mbx" format folders.
If you want to use mutt, you need to get your email out of those
folders. If you want to use mutt and _enjoy_ it, you'll need to do
this on a permanent basis, so a one-time conversion isn't any real
help.
If you hate the works of that designer as much as I do, you can free
yourself from them entirely by e.g. using procmail for your local
delivery. Set up your .forward to pipe into procmail, and set your
.procmailrc to file your email in some normal folder format.
If that kind of brute-force assault against the establishment makes
you nervous, then why not dodge the problem; if your server is using
tmail, it's probably also running an imap server that works off mbx
folder format, so use mutt's imap support. Set your inbox to
{localhost} and read your email that way.
-Bennett
On 3 Mar 2000, Matthew Black wrote:
I'm interested in migrating my site from the Unix and mbox drivers to
the mbx driver but don't know how.
There are three parts of the equation, which must be considered
independently. You can also choose not to do any one of these, although
generally you'll do at least (1).
1) Creating an mbx-format INBOX for each user. This is done by using the
mbxcreat program in ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z,
e.g.
mbxcreat #driver.mbx/INBOX
while logged in as the user.
2) Converting existing mailboxes to mbx format. This is done by using the
the mbxcvt program in ftp://ftp.cac.washington.edu/mail/imap-utils.tar.Z
e.g.
mv myfolder myfolder.old;mbxcvt myfolder.old mbx myfolder
3) Causing new secondary folders to be created in mbx format. This is
done by rebuilding c-client based applications (imapd, Pine, etc.)
with CREATEPROTO=mbxproto (instead of unixproto) in the c-client
makefile (imap-4.[]/src/osdep/unix/Makefile).
4) Delivering new mail directly to the mbx-format INBOX. This is done by
using either tmail (again from the IMAP utilities package) for a direct
call from sendmail, or dmail if you want to do it from procmail.
All of the IMAP utilities have man pages to help you along.
I read that both mbx and mbox use a flat file format. When a user
connects to the imap server, the mbox driver copies the mail spool into
the file ~/mbox if it exists. What does the mbx driver do?
The mbx driver uses a file called INBOX in the home directory as INBOX.
Most sites configure direct delivery to it (see (4) above) but if there is
an INBOX in the spool directory the mbx driver will automatically snarf
the new messages into the mbx INBOX.
How does one configure their system to select the mbx driver? Will
this affect the flat-file format of user folders or just the inbox?
As system administrator, do I need to create an empty INBOX file in every
user's home directory?
Have I answered these questions to your satisfaction?
I would prefer this change to be transparent to
users so they don't need to edit their Netscape configuration.
It should be.
Does the
env_init() patch specifying that imap folders reside in ~/mail/ rather
than ~/ affect where to place mbx INBOX?
Yes.
The mbox driver always expects
that file to be located in ~/mbox. If a user manages to destroy their
mbx INBOX file, does this push them back to the Unix driver?
Yes. The same is true for both mbx and mbox.
-- Mark --
* RCW 19.190 notice: This email address is located in Washington State. *
* Unsolicited commercial email may be billed $500 per message. *
Science does not emerge from voting, party politics, or public debate.
PGP signature
Re: Problem with pine (i want to use mutt)
Michael Thies [EMAIL PROTECTED] wrote on Tue, 21 Mar 2000: But all my incoming mails are going to $HOME/INBOX in pine-format. What's "pine-format"? Doesn't Pine use standard unix mbox files? Not to /var/mail/mthies In /etc/mail/sendmail* I didn't find the point, why mails are going to INBOX. I think (I don't have any knowledge on pine and don't want to have this) the problem is to be found in pine ? Pine doesn't control the mail delivery, so nothing you can change in Pine will help. The delivery location is controlled by whatever mail delivery program is used (/bin/mail, procmail, the MTA's own, etc.) This isn't much of a problem, you don't need to change the delivery location, you just need to tell Mutt where to look for the mail. Setting the MAIL environment variable is probably the best way (before starting Mutt), but failing that, you can specify the location with the $spoolfile setting in your .muttrc. set spoolfile=~/INBOX Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / "I took an IQ test and the results were negative."
Re: Problem with pine (i want to use mutt)
At 23:08 +0100 21 Mar 2000, Michael Thies [EMAIL PROTECTED] wrote: But all my incoming mails are going to $HOME/INBOX in pine-format. Not to /var/mail/mthies Set the MAIL environment variable to the location of your inbox or put 'set spoolfile="$HOME/INBOX"' in your .muttrc file. As far as I know, there is no such thing as "pine-format". In /etc/mail/sendmail* I didn't find the point, why mails are going to INBOX. sendmail is an MTA (message transfer agent), so it doesn't determine where messages get delivered, that's the MDA's (message delivery agent) job. -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ [A computer is] like an Old Testament god, with a lot of rules and no mercy. -- Joseph Campbell
Re: Problem with pine (i want to use mutt)
Hi! On Tue, Mar 21, 2000 at 11:08:41PM +0100, Michael Thies wrote: at my new job, I have an account on a slowlaris-machine. the one and only mua is pine *argh* Quoting your header: Organization: IT Services - Thies It's not a new job in your own company, isn't it? But all my incoming mails are going to $HOME/INBOX in pine-format. Check the spoolfile configuration variable. Pine uses mbox format AFAIK, so there should be no problem. In /etc/mail/sendmail* I didn't find the point, why mails are going to INBOX. A wild guess: Is there an IMAP server (possibly from the University of Washington :-) pushing your mail there? Gero
Re: Problem with pine (i want to use mutt)
On Tue, Mar 21, 2000 at 11:08:41PM +0100, Michael Thies wrote: But all my incoming mails are going to $HOME/INBOX in pine-format. Not to /var/mail/mthies Others have told you how to get mutt to read mail from an arbitrary location, so I won't cover that here, but I felt the need to clear something up that's implied by the above statement. Pine, mutt, elm, etc are nothing more than mail -readers-. They have nothing to do with where or -how- mail is delivered. As readers, you can tell them to archive messages in different files, obviously, but with regards to the initial delivery method, location, and form, this has nothing to do with the mail reader (mutt, pine, elm, etc) but is instead handled by processes such as sendmail or qmail. In other words, there's no such thing as 'pine-format' when it comes to freshly delivered mail. - Myrddin -- ICQ: 22404528 Why Vegan? http://www.firstmagic.com/vegan --
