Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Rick Thomas]

On May 31, 2016, at 2:18 AM, Santiago Vila  wrote:

> On Mon, 30 May 2016, Rick Thomas wrote:
> 
>> Here’s the setup:
>> 
>> I have a POP/IMAP account at pobox.com.  I use cron to run fetchmail which 
>> retrieves (POP3) mail from pobox to a local server on my home network.
>> I process the retrieved mail with procmail to split it into folders and 
>> subfolders based on who it’s from, addressed to, subject, etc…
>> 
>> Here’s the .fetchmailrc file”:
>> = .fetchmailrc ===
>> # Configuration created Thu Aug 15 20:08:16 2002 by fetchmailconf
>> # Lightly edited later by Rick Thomas
>> set postmaster "rbthomas"
>> set bouncemail
>> set no spambounce
>> set properties ""
>> # set syslog
>> 
>> poll mail.pobox.com with proto POP3 timeout 20 and options uidl
>>   user 'XXX' there with password 'YY' is 'rbthomas' here options 
>> keep ssl 
>> 
>> mda "formail -s procmail"
>> ==
>> 
>> As I interpret your reply, I should be using a different mda — NOT
>> formail.  Can you give me some hint as to what it should look like?
> 
> If you are running fetchmail as a user (not daemon, not root), what about 
> this?
> 
> mda "procmail"
> 
> 
> What you are using right now (formail -s procmail) would be required if the 
> output
> of fetchmail were a single mbox folder containing all the emails concatenated.
> 
> "formail -s some-command" splits a whole mbox folder made of concatenaded 
> messages
> and feeds them to "some-command" one at a time.
> 
> I have to confess that I'm also using "formail -s procmail" in my
> setup and I'm not sure why. Maybe there was a time in which fetchmail
> output was a whole mbox folder and you had to split it yourself.
> 
> So I did the following test:
> 
> I created a special mbox folder in my server called "test-folder",
> containing several messages, then I used this script to retrieve it:
> 
> fetchmail -a myserver --folder test-folder -m $HOME/bin/process-email
> 
> where process-email is like this:
> 
> #!/bin/sh
> t=`tempfile`
> cat > ${t}
> 
> What I see after running the above command line is a set of temporary
> files at /tmp, corresponding to each of the messages in the "test-folder".
> 
> This means that fetchmail already feeds a message at a time to whatever
> mda command you are using and you don't need to split them yourself.
> 
> 
> The general problem that you discovered (namely, that the mbox format
> is not 100% reliable regarding message boundaries) has a fix and it's
> called "Maildir format". There is no way to fix that in procmail
> because it is a limitation of the mbox format itself.
> 
> May I close this bug?

Thank you!  Yes, you may close this bug.

My .fetchmailrc file now has
mda “procmail”
and is otherwise unchanged.  I’m using POP3 still, though I’ll experiment with 
imap soon.

Enjoy!
Rick

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Santiago Vila]

I said:
> fetchmail -a myserver --folder test-folder -m $HOME/bin/process-email

Note: For this to work you have to use imap. A .fetchmailrc file
like this would probably work:

server myserver proto imap port 993:
 user "myuser"
 pass "mypasswd"
 ssl
 mda "procmail"

I switched to fetchmail+imap (from fetchmail+pop3) when I realized it
was possible to retrieve different folders that way (not just "INBOX").
POP3 does not allow that.

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Santiago Vila]

On Mon, 30 May 2016, Rick Thomas wrote:

> Here’s the setup:
> 
> I have a POP/IMAP account at pobox.com.  I use cron to run fetchmail which 
> retrieves (POP3) mail from pobox to a local server on my home network.
> I process the retrieved mail with procmail to split it into folders and 
> subfolders based on who it’s from, addressed to, subject, etc…
> 
> Here’s the .fetchmailrc file”:
> = .fetchmailrc ===
> # Configuration created Thu Aug 15 20:08:16 2002 by fetchmailconf
> # Lightly edited later by Rick Thomas
> set postmaster "rbthomas"
> set bouncemail
> set no spambounce
> set properties ""
> # set syslog
> 
> poll mail.pobox.com with proto POP3 timeout 20 and options uidl
>user 'XXX' there with password 'YY' is 'rbthomas' here options 
> keep ssl 
> 
> mda "formail -s procmail"
> ==
> 
> As I interpret your reply, I should be using a different mda — NOT
> formail.  Can you give me some hint as to what it should look like?

If you are running fetchmail as a user (not daemon, not root), what about this?

mda "procmail"


What you are using right now (formail -s procmail) would be required if the 
output
of fetchmail were a single mbox folder containing all the emails concatenated.

"formail -s some-command" splits a whole mbox folder made of concatenaded 
messages
and feeds them to "some-command" one at a time.

I have to confess that I'm also using "formail -s procmail" in my
setup and I'm not sure why. Maybe there was a time in which fetchmail
output was a whole mbox folder and you had to split it yourself.

So I did the following test:

I created a special mbox folder in my server called "test-folder",
containing several messages, then I used this script to retrieve it:

fetchmail -a myserver --folder test-folder -m $HOME/bin/process-email

where process-email is like this:

#!/bin/sh
t=`tempfile`
cat > ${t}

What I see after running the above command line is a set of temporary
files at /tmp, corresponding to each of the messages in the "test-folder".

This means that fetchmail already feeds a message at a time to whatever
mda command you are using and you don't need to split them yourself.


The general problem that you discovered (namely, that the mbox format
is not 100% reliable regarding message boundaries) has a fix and it's
called "Maildir format". There is no way to fix that in procmail
because it is a limitation of the mbox format itself.

May I close this bug?

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Rick Thomas]

On May 30, 2016, at 2:36 AM, Santiago Vila  wrote:

> On Sun, 29 May 2016, Rick Thomas wrote:
> 
>> Package: procmail
>> Version: 3.22-24
>> Severity: normal
>> 
>> Dear Maintainer,
>> 
>> *** Reporter, please consider answering these questions, where appropriate 
>> ***
>> 
>> If procmail processes a mail with body containing a plaintext attachment 
>> that has a line
>> that begins with the string "From " it seems to think this is a separator 
>> between mails.
>> It winds up splitting the original mail into two parts and filing each as a 
>> separate mail
>> item.
>> 
>> This can happen when the attachment is a mail item that has not had the 
>> proper quoting
>> for lines beginning with "From ".  I have attached such an email to this 
>> bugreport.
> 
> procmail does not split anything unless explicitly told.
> 
> In fact, it is usually "formail -s" who split emails, not procmail.
> 
>> There needs to be some way of telling procmail that it will receive input 
>> one email item
>> at a time, (as when being fed by fetchmail) so the line-begins-with-From 
>> processing is
>> not necessary.
> 
> And there is a way indeed, which is to use procmail alone, not "formail -s 
> procmail".
> 
> Your report says "If procmail processes a mail". What do you mean
> exactly by "processes a mail"? Could you please be more explicit?
> A sample email is good, but the report is incomplete if you don't
> tell me what I'm supposed to do with the email.
> 
> Thanks.

Thank you very much, Santiago, for the prompt reply!

Here’s the setup:

I have a POP/IMAP account at pobox.com.  I use cron to run fetchmail which 
retrieves (POP3) mail from pobox to a local server on my home network.
I process the retrieved mail with procmail to split it into folders and 
subfolders based on who it’s from, addressed to, subject, etc…

Here’s the .fetchmailrc file”:
= .fetchmailrc ===
# Configuration created Thu Aug 15 20:08:16 2002 by fetchmailconf
# Lightly edited later by Rick Thomas
set postmaster "rbthomas"
set bouncemail
set no spambounce
set properties ""
# set syslog

poll mail.pobox.com with proto POP3 timeout 20 and options uidl
   user 'XXX' there with password 'YY' is 'rbthomas' here options 
keep ssl 

mda "formail -s procmail"
==

As I interpret your reply, I should be using a different mda — NOT formail.  
Can you give me some hint as to what it should look like?

Thanks!
Rick

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Santiago Vila]

On Sun, 29 May 2016, Rick Thomas wrote:

> Package: procmail
> Version: 3.22-24
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
> If procmail processes a mail with body containing a plaintext attachment that 
> has a line
> that begins with the string "From " it seems to think this is a separator 
> between mails.
> It winds up splitting the original mail into two parts and filing each as a 
> separate mail
> item.
> 
> This can happen when the attachment is a mail item that has not had the 
> proper quoting
> for lines beginning with "From ".  I have attached such an email to this 
> bugreport.

procmail does not split anything unless explicitly told.

In fact, it is usually "formail -s" who split emails, not procmail.

> There needs to be some way of telling procmail that it will receive input one 
> email item
> at a time, (as when being fed by fetchmail) so the line-begins-with-From 
> processing is
> not necessary.

And there is a way indeed, which is to use procmail alone, not "formail -s 
procmail".

Your report says "If procmail processes a mail". What do you mean
exactly by "processes a mail"? Could you please be more explicit?
A sample email is good, but the report is incomplete if you don't
tell me what I'm supposed to do with the email.

Thanks.

Bug#825794: procmail: attachments containing the string From at the beginning of a line confuse procmail

[Rick Thomas]

Package: procmail
Version: 3.22-24
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

If procmail processes a mail with body containing a plaintext attachment that 
has a line
that begins with the string "From " it seems to think this is a separator 
between mails.
It winds up splitting the original mail into two parts and filing each as a 
separate mail
item.

This can happen when the attachment is a mail item that has not had the proper 
quoting
for lines beginning with "From ".  I have attached such an email to this 
bugreport.

There needs to be some way of telling procmail that it will receive input one 
email item
at a time, (as when being fed by fetchmail) so the line-begins-with-From 
processing is
not necessary.


-- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: powerpc (ppc64)

Kernel: Linux 3.18.16-powerpc64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages procmail depends on:
ii  libc6  2.19-18+deb8u4

Versions of packages procmail recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.84.2-1
ii  fetchmail  6.3.26-1+b1

procmail suggests no packages.

-- no debconf information
--- Begin Message ---
Your message dated Sun, 29 May 2016 22:37:47 +
with message-id 
and subject line Bug#825458: fixed in u-boot 2016.03+dfsg1-5
has caused the Debian Bug report #825458,
regarding Please enable Jetson TX1 (P2371-2180)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: u-boot
Version: 2016.05+dfsg1-1
Severity: wishlist

Please enable Jetson TX1 (P2371-2180).

I've attached a tested patch.

Note: NVidia's flash script looks for a file called "u-boot" so I
added a symlink from eboot.elf.

-- 
Martin Michlmayr
http://www.cyrius.com/
>From 12f46a6bc34370153def69c43e87aede348e4003 Mon Sep 17 00:00:00 2001
From: Martin Michlmayr 
Date: Thu, 26 May 2016 16:11:28 -0700
Subject: [PATCH] Add Jetson TX1 (P2371_2180) target

---
 debian/changelog  | 9 +
 debian/control| 2 +-
 debian/targets| 3 +++
 debian/u-boot-tegra.README.Debian | 8 
 debian/u-boot-tegra.links | 1 +
 debian/u-boot-tegra.lintian-overrides | 2 ++
 6 files changed, 24 insertions(+), 1 deletion(-)
 create mode 100644 debian/u-boot-tegra.links

diff --git a/debian/changelog b/debian/changelog
index 2df0edb..9ab93ce 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+u-boot (2016.05+dfsg1-2) UNRELEASED; urgency=medium
+
+  [ Martin Michlmayr ]
+  * u-boot-tegra: Add Jetson TX1 (P2371-2180) target.
+  * u-boot-tegra: Add arm64 arch.
+  * u-boot-tegra: Update README.Debian for Jetson TX1.
+
+ -- Martin Michlmayr   Thu, 26 May 2016 15:05:36 -0700
+
 u-boot (2016.05+dfsg1-1) experimental; urgency=medium
 
   * New upstream version.
diff --git a/debian/control b/debian/control
index 6da1a69..6e2d3ee 100644
--- a/debian/control
+++ b/debian/control
@@ -39,7 +39,7 @@ Description: A boot loader for imx systems
  ${uboot:platforms}
 
 Package: u-boot-tegra
-Architecture: armhf
+Architecture: armhf arm64
 Multi-Arch: same
 Depends: ${misc:Depends}
 Breaks: u-boot (<< 2014.10~rc2+dfsg1-2~)
diff --git a/debian/targets b/debian/targets
index 634e93c..71a06bf 100644
--- a/debian/targets
+++ b/debian/targets
@@ -153,6 +153,9 @@ armhf	sunxi		orangepi_plus	u-boot-sunxi-with-spl.bin
 # Ryan Finnie 
 arm64	rpi		rpi_3		u-boot.bin
 
+# Martin Michlmayr 
+arm64	tegra		p2371-2180	u-boot-dtb.bin
+
 avr32	-		hammerhead	u-boot.img
 
 mips	-		qemu_mips	u-boot.bin
diff --git a/debian/u-boot-tegra.README.Debian b/debian/u-boot-tegra.README.Debian
index 83cc222..97a0200 100644
--- a/debian/u-boot-tegra.README.Debian
+++ b/debian/u-boot-tegra.README.Debian
@@ -3,11 +3,19 @@
 At this point, you must install U-Boot to flash yourself from a host
 system using the Linux_For_Tegra tools.
 
+=== Jetson TK1 ===
+
 sudo ./flash.sh -L /usr/lib/u-boot/jetson-tk1/u-boot-dtb-tegra.bin jetson-tk1 mmcblk1p1
 
 It seems that L4T R19.3.0 is currently required (image does not boot
 if flashed with L4T R21.X).
 
+=== Jetson