Re: Exim/fetchmail/procmail - bad mail files
On Fri, 21 Jul 2000, James Green wrote:
> OK so I give up trying to figure this one out :-(
> I've got exim up and running. I used eximconf and selected option
> 2. I also have fetchmail and procmail up and running.
> Mail comes in from mail.linux.com using imap. The connection is
> tunnelled over ssh. The connection goes fine and my proc.log shows
> mail being received and filtered to my mail folders.
> I can fire up mutt, and point it at a mailbox (any) and I get:
> /firstname.lastname@example.org is not a mailbox.
> This also occurs on loading mutt, but with
> /var/spool/mail/jg instead.
> The mail files themselves look like this:
> Return-Path: <email@example.com>
> Received: from mail.linux.com
> by localhost with IMAP (fetchmail-5.3.4)
> for jg@localhost (single-drop); Fri, 21 Jul 2000 20:47:26 +0100 (BST)
> Received: from seralph10.essex.ac.uk (seralph10.essex.ac.uk [188.8.131.52])
> by mail.linux.com (8.9.3/8.9.3) with ESMTP id GAA24469
> for <firstname.lastname@example.org>; Fri, 24 Mar 2000 06:57:57 -0800
> Received: from sunlab19.essex.ac.uk
> ([184.108.40.206] helo=sunlab19 ident=jmkgre)
> by seralph10.essex.ac.uk with esmtp (Exim 3.13 #1)
> id 12YVXA-0005xx-00
> for email@example.com; Fri, 24 Mar 2000 14:57:56 +0000
> Date: Fri, 24 Mar 2000 14:57:55 +0000 (GMT)
> From: Green J M K <firstname.lastname@example.org>
> X-Sender: jmkgre@sunlab19
> To: email@example.com
> Subject: vrml link
> Message-ID: <Pine.LNX.4.05.10003241457380.20496-100000@sunlab19>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Content-Length: 33
> Lines: 3
> [ at which point more emails follow ]
> This format is identical to /var/spool/mail/jg.
> I'm told that the formatting is wrong and that exim is to blame.
> However I am unable to find anyone in IRC who knows exim to help.
As far as I see the problem about the formatting is that you need a
From <user@host> <Date>
line at the beginning of every message. You can make it by creating a
little wrapper-script in your favourite programming language (awk, perl,
python, bash, tcsh, even C/C++), and piping the message through the
script in your procmailrc.
Ask for help if you are not a programmer,