headers
norm | 25 May 2013 15:17

The zone field of Date-Time components

As I read, RFC822, Section 5.1, the zone filed field of Date components, is required. Do I misread it?  I have
encountered one Email, for which it is missing. It there a de defacto standard which makes it optional?

    Norman Shapiro
    798 Barron Avenue
    Palo Alto CA 94306-3109
    (650) 565-8215
    norm <at> dad.org

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 2 comments |
headers
Dale Alspach | 18 May 2013 18:20

nmh dependence on metamail

Ubuntu 12.04 includes a package for nmh but none for metamail. Someone
noted this in a bug report. Debian seems to have abandoned metamail.
In Ubuntu 10.xx I was able to make it work from source.
The source that I have for metamail 2.7 will not compile on my upgraded
system and I am not knowledgeable enough to try to fix it.

Are there any replacements for metamail  or an updated source?

exmh seems to work fine.

Dale Alspach

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 4 comments |
headers
norm | 17 May 2013 17:40

Date syntax

Would somebody please point me to a specification of the date syntax used by pick and sortm.

    Norman Shapiro

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 3 comments |
headers
norm | 4 May 2013 19:41

reason: 554 5.7.0 Message Size Violation

This is the first I've ever heard of this rejection reason. The message consisted, almost entirely, of an
attachment, Spec_05_04_10:04.zip,  a 471,282 byte zip file.

Is there anything I can do, short of breaking the attachment into several pieces, and sending separately?

Is there some way, other than trial and error, to determine the size limit?
--------

------- Forwarded Message

Return-Path: <MAILER-DAEMON <at> rawbw.com>
X-Original-To: norm <at> localhost
Delivered-To: norm <at> localhost.dad.org
Received: from lad.dad.org (localhost [IPv6:::1])
	by lad.dad.org (Postfix) with ESMTP id 9973360E78
	for <norm <at> localhost>; Sat,  4 May 2013 10:08:25 -0700 (PDT)
Received: from imap.rawbw.com [198.144.192.43]
	by lad.dad.org with IMAP (fetchmail-6.3.17)
	for <norm <at> localhost> (single-drop); Sat, 04 May 2013 10:08:25 -0700 (PDT)
Received: from ns2.adzone.com (ns2.adzone.com [96.247.50.174])
	by mail1.rawbw.com (8.14.2/8.14.2) with ESMTP id r44H73eX067605
	for <soft <at> rawbw.com>; Sat, 4 May 2013 10:07:08 -0700 (PDT)
Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45])
	by ns2.adzone.com (8.14.5/8.14.5) with ESMTP id r44H2LGu118336
	for <norm <at> dad.org>; Sat, 4 May 2013 10:02:21 -0700
Received: from localhost (localhost)
	by shell0.rawbw.com (8.14.4/8.14.4) id r44H72Kw096661;
	Sat, 4 May 2013 10:07:02 -0700 (PDT)
	(envelope-from MAILER-DAEMON)
Date: Sat, 4 May 2013 10:07:02 -0700 (PDT)
(Continue reading)

Permalink | Reply | 4 comments |
headers
Irwin Tillman | 2 May 2013 23:39
Picon
Favicon

files created by Fcc header always have mode 0600

Platform: nmh-1.5 on Solaris 10 SPARC

Is the intended behavior of an Fcc header that
the files it writes always have mode 0600,
regardless of other settings?

--

When I use comp with an Fcc header, the file written
to the Fcc folder always have mode 0600.

My umask is 022, and in .mh_profile I have:
Msg-Protect: 0644
Folder-Protect: 0755

I expected the file written to the Fcc folder to 
have mode 0644 rather the 0600 I I actually see.

It looks like post gets called, creates a temp file (MAILDIR/postXXXXXX)
with permission 0600, then performs chmod(0600) on that file,
then later calls refile to link that temp file into the Fcc folder.

I see that post(1) says that post doesn't read mh_profile,
so it's no surprise that Msg-Protect isn't used.

Irwin Tillman

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
(Continue reading)

Permalink | Reply | 0 comments |
headers
Irwin Tillman | 3 May 2013 14:59
Picon
Favicon

files created by Fcc header always have mode 0600

Platform: nmh-1.5 on Solaris 10 SPARC

Is the intended behavior of an Fcc header that
the files it writes always have mode 0600,
regardless of other settings?

--

When I use comp with an Fcc header, the file written
to the Fcc folder always have mode 0600.

My umask is 022, and in .mh_profile I have:
Msg-Protect: 0644
Folder-Protect: 0755

I expected the file written to the Fcc folder to 
have mode 0644 rather the 0600 I I actually see.

It looks like post gets called, creates a temp file (MAILDIR/postXXXXXX)
with permission 0600, then performs chmod(0600) on that file,
then later calls refile to link that temp file into the Fcc folder.

I see that post(1) says that post doesn't read mh_profile,
so it's no surprise that Msg-Protect isn't used.

Irwin Tillman

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
(Continue reading)

Permalink | Reply | 6 comments |
headers
Ralph Corderoy | 3 May 2013 12:47
Picon

mhshow(1) Suggests moreproc can be used.

Hi,

mhshow(1):

    If a display string is not found, mhshow has several default values:

        mhshow-show-text/plain: %pmoreproc '%F'
        mhshow-show-message/rfc822: %pshow -file '%F'

That suggests to this reader that one can use `moreproc' in one's own
entries, perhaps anywhere in the command but certainly at the beginning.
It doesn't seem to be the case.  Does the man page need clarifying?

Cheers, Ralph.

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 1 comment |
headers
Valdis Kletnieks | 2 May 2013 18:56
Picon
Favicon

send/post busted...

Some commit recently broke my 'post' command's ability to find the
SASL password needed to authenticate to our mail server.  I'd do a git bisect
to track it down further, but 'git log' hints there's intermediate broken
states.

After 'git checkout a431fb0f788cf93c9d93c3ad268fa0813e1bf2ef' (the last commit
before 'credential' support was added, I get this trying to post mail. PW redacted.

(tls-encrypted) => EHLO turing-police.cc.vt.edu
(tls-decrypted) <= 250-auth3.smtp.vt.edu Hello turing-police.cc.vt.edu [128.173.14.107], pleased
to meet you
(tls-decrypted) <= 250-ENHANCEDSTATUSCODES
(tls-decrypted) <= 250-PIPELINING
(tls-decrypted) <= 250-8BITMIME
(tls-decrypted) <= 250-SIZE 26210000
(tls-decrypted) <= 250-DSN
(tls-decrypted) <= 250-AUTH LOGIN PLAIN
(tls-decrypted) <= 250-DELIVERBY
(tls-decrypted) <= 250 HELP
(tls-encrypted) => AUTH LOGIN
(tls-decrypted) <= 334 VXNlcm5hbWU6
(tls-encrypted) => dmFsZGlzQHZ0LmVkdQ==
(tls-decrypted) <= 334 UGFzc3dvcmQ6
(tls-encrypted) => redacted-base64-pass-here
(tls-decrypted) <= 235 2.0.0 OK Authenticated
(tls-encrypted) => MAIL FROM:<Valdis.Kletnieks <at> vt.edu>
(tls-decrypted) <= 250 2.1.0 <Valdis.Kletnieks <at> vt.edu>... Sender ok
(tls-encrypted) => RCPT TO:<valdis <at> vt.edu>
(tls-decrypted) <= 250 2.1.5 <valdis <at> vt.edu>... Recipient ok
(tls-encrypted) => DATA
(Continue reading)

Permalink | Reply | 4 comments |
headers
Bob Carragher | 2 May 2013 05:00
Picon

Setup help???

Can someone please point me to resources or provide a simple How-To
for configuring NMH (and related systems, like sendmail)?  My setup:

*  Laptop running (Ubuntu 10.04) Linux.
*  My "public" address is "dnc2dnc <at> gmail.com."
   --  I want all my email to appear to come from this address.  I have
       set "From:" and "Reply-To:" fields in my "components" and other
       configuration files.  However, I have problems with the generated
       "Sender:" field (see below).
   --  I use fetchmail to POP email from this address.  (I mention this
       only in case it changes the setup.)
*  I send mail when connected to my ISP, but fetch/POP mail whenever
   I'm connected to the Internet.  It would be nice to be able to use NMH
   to send mail whenever I'm connected to the Internet, but I will settle
   for continuing to use the Google web interface for that.
*  I added to /etc/hosts a FQDN that I don't normally send email
   to ("mit.edu") because some mailers reject email that comes
   from "foo <at> localhost" or "foo <at> localhost.localdomain."  I didn't
   add "<ISP>" because then any email I send to "foo <at> <ISP>"
   appears to be for a "local user;" also "<laptop-userID> <at> <ISP>"
   is taken.

This has generally worked, although (because I use sendmail) this adds
the line

     Sender: <laptop-userID> <at> <ISP>

to all my message headers.  In the last few years, more and more mail
providers are keying off this as an indication of spam, and in recent
weeks my email doesn't even reach some recipients at all (not even
(Continue reading)

Permalink | Reply | 12 comments |
headers
Paul Fox | 1 May 2013 17:32
Picon
Favicon

another message corruption bug

hi --

sorry to have to report another corruption issue.  inc corrupts the
DKIM-Signature header in the attached message from:

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=x-received:sender:content-type:mime-version:subject:from
	:in-reply-to:date:cc:message-id:references:to:x-mailer;
	bh=9RvGuD7z0t+zYV3baoa1XJT3sSAnFive2ajfw7XzoAI=;
	b=oegx7thD9cv2dxX30/3vHXKritCxhrTIMIsAX0cBnt1C6JXWgq7sKD5M+w/+CrkJp1
	JqUHyVQnwSqMu03WfNBYdzAVrNc7Ask11AVp+GrwniRFfW6yGXzUh/okC/fAwS4U46sh
	tAeflp3+SiSKLuo6U+00jjH8ekhtYxmWSrXBvYHQgvsyqHd5CHvPThO4qxDUJ0Zx/4mj
	sU1fI9N5mBm27WkHFgFJbBgeMZViP9LDw3wapxHK0ABucKdEM6cqOrNn+cZVuVfysNXl
	53IWIWcIOMBwL5zlG6k7pdNm3OtCnn59RML9EIPfDv+Vuk8VfHfiP7Siz7kqPQVf+8ol
	/6QQ==

to: 

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=x-received:sender:content-type:mime-version:subject:from
	:in-reply-to:date:cc:message-id:references:to:x-mailer;
	bh=9RvGuD7z0t+zYV3baoa1XJT3sSAnFive2ajfw7XzoAI=;
	b=oegx7thD9cv2dxX30/3vHXKritCxhrTIMIsAX0cBnt1C6JXWgq7sKD5M+w/+CrkJp1
	JqUHyVQnwSqMu03WfNBYdzAVrNc7Ask11AVp+GrwniRFfW6yGXzUh/okC/fAwS4U46sh
	tAeflp3+SiSKLuo6U+00jjH8ekhtYxmWSrXBvYHQgvsyqHd5CHvPThO4qxDUJ0Zx/4mj
	sU1fI9N5mBm27WkHFgFJbBgeMZViP9LDw3wapxHK0ABucKdEM6cqOrNn+cZVuVfysNXl
53IWIWcIOMBwL5zlG6k7pdNm3OtCnn59RML9EIPfDv+Vuk8VfHfiP7Siz7kqPQVf+8ol
	/6QQ==

(i don't know whether the issue is this header, or something previous.)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Martin McCormick | 28 Apr 2013 13:41

Does maildrop work correctly with nmh?

	I am probably just setting up .mailfilter wrong, but so
far, it doesn't seem to understand that it should behave in an
mh way. It wants to put mail in a .mbox format in just about any
directory except $HOME/Mail/folder/message# in the normal mh
style.

	Right now, I use procmail but maildrop reportedly makes
filtering and sorting easier since it does better mime
expansions.

	Thanks for any good ideas.

Martin McCormick

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 11 comments |

Gmane