* On 24 Mar 2013, Chris Green wrote:
Exactly! So mutt *doesn't* add a blank line before the 'File ' if there
wasn't one there already, in fact it doesn't do anything except copy
what it's given by the MDA.
This may be correct in that mutt isn't an MDA but it isn't what everyone
here has
On Mon, Mar 25, 2013 at 12:20:38AM -0500, David Champion wrote:
* On 24 Mar 2013, Chris Green wrote:
Exactly! So mutt *doesn't* add a blank line before the 'File ' if there
wasn't one there already, in fact it doesn't do anything except copy
what it's given by the MDA.
This may be
I looked at a mbox that was entirely created under Ubuntu and there are
blank lines at the end of each message before the From line.
On Sat, Mar 23, 2013 at 03:28:29PM +, Chris Green wrote:
On Sun, Mar 24, 2013 at 01:22:56AM +1100, Erik Christiansen wrote:
On 23.03.13 12:40, Chris Green
[- Sun 24.Mar'13 at 7:05:44 + Brian Salter-Duke :-]
I looked at a mbox that was entirely created under Ubuntu and there are
blank lines at the end of each message before the From line.
I can confirm that my sent mbox, created by mutt (current version), also
has a blank
On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote:
It looks as though your python delivery program might be doing this?
Have you tried taking the python program out of the process to test, to
see if the messages are being appended to the mbox correctly? I know
you've looked at it
On Sun, Mar 24, 2013 at 06:48:25PM +, Chris Green wrote:
On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote:
It looks as though your python delivery program might be doing this?
Have you tried taking the python program out of the process to test, to
see if the messages are
On Sun, Mar 24, 2013 at 02:29:09PM -0500, Will Fiveash wrote:
On Sun, Mar 24, 2013 at 06:48:25PM +, Chris Green wrote:
On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote:
It looks as though your python delivery program might be doing this?
Have you tried taking the
On Sun, Mar 24, 2013 at 07:36:13PM +, Chris Green wrote:
On Sun, Mar 24, 2013 at 02:29:09PM -0500, Will Fiveash wrote:
On Sun, Mar 24, 2013 at 06:48:25PM +, Chris Green wrote:
On Sun, Mar 24, 2013 at 11:09:31AM +, James Griffin wrote:
It looks as though your python
On Sun, Mar 24, 2013 at 19:36:13 +, Chris Green wrote:
Yes, but did you look in the existing mbox file to see if there were
blank lines betweeen the messages there?
For what it's worth, I took a simple test message, saved it into a new
mailbox, and then used vi to make four copies of the
On Sun, Mar 24, 2013 at 03:28:28PM -0500, Will Fiveash wrote:
When I use the mutt (on Solaris 11) copy function to copy three messages
in an existing mbox file to an new mbox file I see a blank line before
each new message's From line except for the first message. Maybe
it's time to
On Sun, Mar 24, 2013 at 05:53:05PM -0400, Nathan Stratton Treadway wrote:
So... it does appear that Mutt will preserve whatever trailing-blank-
line situation was originally created by the MDA, even as it saves the
messages into new mailboxes (and that it doesn't actually care what
On 22.03.13 12:54, Derek Martin wrote:
On Fri, Mar 22, 2013 at 09:04:21AM +, Chris Green wrote:
Mutt itself *doesn't* put a blank line there, if you S[ave] or
C[opy] messages to a new mbox the messages have no blank lines
before the 'From '.
When I save a message to another mailbox,
On Sat, Mar 23, 2013 at 08:15:27PM +1100, Erik Christiansen wrote:
On 22.03.13 12:54, Derek Martin wrote:
On Fri, Mar 22, 2013 at 09:04:21AM +, Chris Green wrote:
Mutt itself *doesn't* put a blank line there, if you S[ave] or
C[opy] messages to a new mbox the messages have no blank
On 23.03.13 12:40, Chris Green wrote:
Well I first actually tried it and saw no blank line.
I've now looked throught my archive (1845 mailboxes) and most of them,
saved with mutt, using S[ave], seem *not* to have a blank line either.
There are some with blank lines between but I suspect
On Sun, Mar 24, 2013 at 01:22:56AM +1100, Erik Christiansen wrote:
On 23.03.13 12:40, Chris Green wrote:
Well I first actually tried it and saw no blank line.
I've now looked throught my archive (1845 mailboxes) and most of them,
saved with mutt, using S[ave], seem *not* to have a blank
On Thu, Mar 21, 2013 at 05:06:17PM -0500, Derek Martin wrote:
On Wed, Mar 20, 2013 at 06:08:49PM -0500, David Champion wrote:
There absolutely should be a blank line. I think though that the order
is wrong: mutt expects that a message (i.e. a From_ line) appears at
the old EOF marker, and
[- Fri 22.Mar'13 at 9:04:21 + Chris Green :-]
On Thu, Mar 21, 2013 at 05:06:17PM -0500, Derek Martin wrote:
On Wed, Mar 20, 2013 at 06:08:49PM -0500, David Champion wrote:
There absolutely should be a blank line. I think though that the order
is wrong: mutt expects
[- Fri 22.Mar'13 at 7:38:54 -0400 Patrick Shanahan :-]
* James Griffin j...@kontrol.kode5.net [03-22-13 05:24]:
[...]
Sorry Chris, I believe you're confusing MTA with MDA/LDA, although
that's not really relevent. Could you perhaps alter your python script
as David
On Fri, Mar 22, 2013 at 09:22:34AM +, James Griffin wrote:
[- Fri 22.Mar'13 at 9:04:21 + Chris Green :-]
On Thu, Mar 21, 2013 at 05:06:17PM -0500, Derek Martin wrote:
On Wed, Mar 20, 2013 at 06:08:49PM -0500, David Champion wrote:
There absolutely should be a
* On 22 Mar 2013, Chris Green wrote:
What should an MTA do if there *isn't* a blank line at the end of
the current mbox where it is going to append a new message? It
seems to me that what the Python libraries do guarantees that there
will always be a blank line before the
On Fri, Mar 22, 2013 at 11:48:46AM -0500, David Champion wrote:
* On 22 Mar 2013, Chris Green wrote:
What should an MTA do if there *isn't* a blank line at the end of
the current mbox where it is going to append a new message? It
seems to me that what the Python libraries do
On Fri, Mar 22, 2013 at 09:04:21AM +, Chris Green wrote:
On Thu, Mar 21, 2013 at 05:06:17PM -0500, Derek Martin wrote:
On Wed, Mar 20, 2013 at 06:08:49PM -0500, David Champion wrote:
There absolutely should be a blank line. I think though that the order
is wrong: mutt expects that a
[- Wed 20.Mar'13 at 18:08:49 -0500 David Champion :-]
* On 20 Mar 2013, Chris Green wrote:
Has the mutt handling of this changed in the last few versions?
Not that I know of, and I doubt it.
The python way of doing this is correct according to the RFC as far as I
On Thu, Mar 21, 2013 at 09:25:49AM +, James Griffin wrote:
[- Wed 20.Mar'13 at 18:08:49 -0500 David Champion :-]
* On 20 Mar 2013, Chris Green wrote:
Has the mutt handling of this changed in the last few versions?
Not that I know of, and I doubt it.
The
On Thu, Mar 21, 2013 at 11:45:22AM +1100, raf wrote:
the python code needs to be changed to write the From header, then
the
message, then the blank line.
Then it appears to be a bug in the Python mailbox library code. I have
attached it here. If you look through you will see, in the mbox
On Wed, Mar 20, 2013 at 06:08:49PM -0500, David Champion wrote:
There absolutely should be a blank line. I think though that the order
is wrong: mutt expects that a message (i.e. a From_ line) appears at
the old EOF marker, and that the EOF marker is on/after a blank line.
I think that if you
What is supposed to happen in the following scenario:-
I'm viewing my incoming mail (inbox), looking at the index view in mutt.
Some new mail arrives, delivered by procmail/python script/whatever
to the inbox.
Is there supposed to be some mechanism whereby mutt recognises that all
On 20.03.13 13:14, Chris Green wrote:
What is supposed to happen in the following scenario:-
I'm viewing my incoming mail (inbox), looking at the index view in mutt.
Some new mail arrives, delivered by procmail/python script/whatever
to the inbox.
Is there supposed to be
On Thu, Mar 21, 2013 at 01:05:27AM +1100, Erik Christiansen wrote:
On 20.03.13 13:14, Chris Green wrote:
What is supposed to happen in the following scenario:-
I'm viewing my incoming mail (inbox), looking at the index view in mutt.
Some new mail arrives, delivered by
What I want to know is:-
Is it possible for a message to be delivered into an mbox that mutt
is looking at without provoking the Mailbox was externally
modified message?
If the above is possible then what does the delivering MTA have to
do so that the delivered
On 20.03.13 14:11, Chris Green wrote:
What I want to know is:-
Is it possible for a message to be delivered into an mbox that mutt
is looking at without provoking the Mailbox was externally
modified message?
Yes. Here the message is New mail in this mailbox.
(Confirmed by
On Wed, Mar 20, 2013 at 02:58:58PM +, Chris Green wrote:
What I want to know is:-
Is it possible for a message to be delivered into an mbox that mutt
is looking at without provoking the Mailbox was externally
modified message?
If the above is possible then
* On 20 Mar 2013, Chris Green wrote:
I suspect my MTA doesn't agree exactly with mutt about where the
'message separator' is.
When your script delivers a message, does it append a message and then
a blank line, or does it append a blank line and then a message?
--
David Champion •
On Wed, Mar 20, 2013 at 10:11:06AM -0500, David Champion wrote:
* On 20 Mar 2013, Chris Green wrote:
I suspect my MTA doesn't agree exactly with mutt about where the
'message separator' is.
When your script delivers a message, does it append a message and then
a blank line, or does it
* On 20 Mar 2013, Chris Green wrote:
Has the mutt handling of this changed in the last few versions?
Not that I know of, and I doubt it.
The python way of doing this is correct according to the RFC as far as I
can tell, there *should* be a blank line between the end of a message
and the
Chris Green wrote:
On Wed, Mar 20, 2013 at 10:11:06AM -0500, David Champion wrote:
* On 20 Mar 2013, Chris Green wrote:
I suspect my MTA doesn't agree exactly with mutt about where the
'message separator' is.
When your script delivers a message, does it append a message and
36 matches
Mail list logo
