[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dng
Subject:    [DNG] Procmail on beowulf omits mbox separator
From:       dvalin () internode ! on ! net
Date:       2021-03-31 11:33:02
Message-ID: 5ff4a549a077f4dc2972c40db97abf0b512692e4 () webmail ! internode ! on ! net
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]



 The new beowulf 3.0.0 is nifty nice, but I'm foxed by procmailfailing
to prepend an mbox separator to each delivered email,something which
has been standard behaviour for decades,and essential for reading an
mbox format mailbox.
Invoking procmail in fetchmailrc via the mda option: 
 $ more .fetchmailrc
# Configuration created Sat Mar 27 22:14:20 2021 by fetchmailconf 1.58
set logfile "/tmp/fetchmail_log"
set postmaster "erik"
set bouncemail
set no spambounce
set softbounce
set properties ""
set daemon 600
poll mail.internode.on.net with proto POP3
             user 'dvalin' there is 'erik' here options ssl fetchall
mda /usr/bin/procmail

#           Testing:
#           user 'dvalin' there is 'erik' here options ssl keep mda
/usr/bin/procmail

 works fine as far as delivering mail to a dozen mailboxes, using the
.procmailrc which has served flawlessly on the old host for decades. 
 BUT the standard mbox format email separator "From ..." is omitted on
the beowulf install, making newly received emails unreadable in mutt.
(It's described at some length in the mbox manpage, so I won't
belabour 
it here.)

I've found no mention of mbox format controls in either the procmail
or 
procmailrc manpages, perhaps because it was always the default.Google
is drawing a blank thus far. 
 The new host has procmail version v3.23pre 2001/09/13 , while the old
one has v3.22 2001/09/10. 
 Why not have fetchmail deliver to an MTA on port 25? Well, I tried
thatfirst (beowulf has exim), but that did exactly the same thing.
Direct deliveryto procmail removes one variable.
Is anyone successfully using procmail -> mbox mailboxeson beowulf? 
 I could probably munge a solution with "formail -I", but it shouldn't
be 
 necessary to bodge my way to standard behaviour. 
 Erik
A previous send of this post hasn't even been Bcced by the
mailserverafter an hour, so I'm venturing a retry.


[Attachment #5 (text/html)]

<html><body><br /><div>
				The new beowulf 3.0.0 is nifty nice, but I'm foxed by procmail</div><div>failing \
to prepend an mbox separator to each delivered email,</div><div>something which has \
been standard behaviour for decades,</div><div>and essential for reading an mbox \
format mailbox.</div><div><br /></div><div>Invoking procmail in fetchmailrc via the \
mda option: </div><div><br /></div>
<div>$ more .fetchmailrc<br /># Configuration created Sat Mar 27 22:14:20 2021 by \
fetchmailconf 1.58<br />set logfile "/tmp/fetchmail_log"<br />set postmaster \
"erik"<br />set bouncemail<br />set no spambounce<br />set softbounce<br />set \
properties ""<br />set daemon 600<br />poll mail.internode.on.net with proto POP3<br \
/>             user 'dvalin' there is 'erik' here options ssl fetchall mda \
/usr/bin/procmail<br /><br />#           Testing:<br />#           user 'dvalin' \
there is 'erik' here options ssl keep mda /usr/bin/procmail<br /></div> <div><br \
/></div> <div><br /></div>
<div>works fine as far as delivering mail to a dozen mailboxes, using the</div>
<div>.procmailrc which has served flawlessly on the old host for decades.</div>
<div><br /></div>
<div>BUT the standard mbox format email separator "From ..." is omitted</div>
<div>on the beowulf install, making newly received emails unreadable in mutt.</div>
<div>(It's described at some length in the mbox manpage, so I won't belabour <br \
/></div><div>it here.)<br /></div> <div><br /></div><div>I've found no mention of \
mbox format controls in either the procmail or <br /></div><div>procmailrc manpages, \
perhaps because it was always the default.</div><div>Google is drawing a blank thus \
far. </div><div><br /></div>
<div>The new host has procmail version v3.23pre 2001/09/13 , while the old</div>
<div>one has v3.22 2001/09/10.</div>
<div><br /></div>
<div>Why not have fetchmail deliver to an MTA on port 25? Well, I tried \
that</div><div>first (beowulf has exim), but that did exactly the same thing. Direct \
delivery</div><div>to procmail removes one variable.</div><div><br /></div><div>Is \
anyone successfully using procmail -&gt; mbox mailboxes</div><div>on beowulf?</div> \
<div><br /></div> <div>I could probably munge a solution with "formail -I", but it \
shouldn't be <br /></div> <div>necessary to bodge my way to standard behaviour.</div>
<div><br /></div>
<div>Erik</div><div><br /></div><div>A previous send of this post hasn't even been \
Bcced by the mailserver</div><div>after an hour, so I'm venturing a retry.<br \
/></div></body></html>


[Attachment #6 (text/plain)]

_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic