headers
Nelson Henry Eric | 7 Feb 2002 01:15
Picon

Re: Procmail development (Was: is this procmail rant justified?)

What's the problem?  Why does "relay1.rwth-aachen.de" say my domain does not
resolve?  If it doesn't resolve, how can I get the mail back?  As mentioned
in the message below, other lists let me (un)subscribe and post without
trouble.  There doesn't seem to be any networking problem here of any kind.
(Fingers crossed :)

henry nelson

> > Final-Recipient: RFC822; procmail <at> Lists.RWTH-Aachen.DE
> > Action: failed
> > Status: 4.4.7
> > Remote-MTA: DNS; relay1.rwth-aachen.de
> > Diagnostic-Code: SMTP; 451 4.1.8 Domain of sender address netb <at> irm.nara.kindai.ac.jp does not resolve
> > Last-Attempt-Date: Wed, 6 Feb 2002 11:02:42 +0900 (JST)
> 
> > Date: Fri, 1 Feb 2002 10:11:50 +0900
> > From: henry nelson <netb <at> irm.nara.kindai.ac.jp>
> > Subject: Re: Procmail development (Was: is this procmail rant justified?)
> > 
> > On Fri, Feb 01, 2002 at 12:04:28AM +0000, Martin McCarthy wrote:
> > > I was going to send this privately to Philip, but thought that others on
> > > the list might be interested in the answer (assuming the problem is not
> > > my stupidity! :-))
> > 
> > I am interested.  It has taken me more than a month to get back on the list
> > since a power outage on December 26th shut down our servers for four days,
> > and I was kicked off the list.
> > 
> > My requests to get on the procmail list either vanished or after about a
> > week's time came back with some comment to the effect that the domain name
(Continue reading)

Permalink | Reply | 0 comments |
headers
Professional Software Engineering | 7 Feb 2002 01:33

Re: Procmail development (Was: is this procmail rant justified?)

At 09:15 2002-02-07 +0900, Nelson Henry Eric did say:
>What's the problem?  Why does "relay1.rwth-aachen.de" say my domain does not
>resolve?  If it doesn't resolve, how can I get the mail back?

What address was the message From: ?  Your own mailserver perhaps?  The 
error you received was generated during the SMTP transaction, and 
therefore, wasn't "sent" by the remote (rwth-aachen.de) server.

There may have been a transient DNS or network problem preventing the 
server from resolving your host.

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
Permalink | Reply | 2 comments |
headers
Professional Software Engineering | 7 Feb 2002 03:37

Re: Procmail development (Was: is this procmail rant justified?)

At 02:34 2002-02-07 +0100, General P. Fault wrote:

> > There may have been a transient DNS or network problem preventing the
> > server from resolving your host.
>
>and thus the Aachen mail server sent back a 451 error message:
[snip]

Ya, I understand that - the question seemed to imply being puzzled that the 
message was returned to the sender when the machine issuing the error 
claimed it couldn't resolve the hostname.  What I was attempting to relate 
was that the error message was NOT delivered by the machine issuing the 
error, but rather by the machine which was attempting to pass the message 
along - that host should have been identified in the From: header of the 
bounce itself.

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
Permalink | Reply | 0 comments |
headers
Chuck Charlton | 7 Feb 2002 05:02
Picon

Adding a subject line

The first recipe in my .procmailrc captures mail from the
calendar program on my system.  This email has a From: attribute
which we will call root <at> able.com

This email has a null subject line.  I would like to add a
subject line of

	Baker

to this email before i process it further.  How could I do that?

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
Permalink | Reply | 0 comments |
headers
Professional Software Engineering | 7 Feb 2002 05:24

Re: Adding a subject line

At 20:02 2002-02-06 -0800, Chuck Charlton wrote:
>This email has a null subject line.  I would like to add a
>subject line of
>
>         Baker

Let's assume that your first recipe actually matches the message in 
question, and perhaps has similar conditions to the following:

:0fh
* From:[        ]*root <at> able\.com
* Subject:[     ]*$
| formail -I"Subject: Baker"

The 'f' flag says to FILTER this message, the 'h' flag says to diddle only 
with the header (you're not asking to mess with the body, so let's not do 
anything special with that if it isn't necessary), then piping it into 
formail with the appropriate argument will set/replace the Subject header.

Note that the above Subject condition says if the Subject header EXISTS, 
but is at most whitespace, nothing more.  If you want an ABSENCE of a 
subject header altogether, replace that with:

* ! ^Subject:

---
  Sean B. Straw / Professional Software Engineering

  Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
  Please DO NOT carbon me on list replies.  I'll get my copy from the list.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Matt of the Long Red Hair | 7 Feb 2002 10:03

"Suspicious rcfile" with virutal domains


I've got a question about how procmail determines what UID is supposed to own
an rcfile.  I've poked around in the list archive, but don't see anything that
relates to this situation.. apologies if this has been covered before.

I'm using procmail to handle delivery to virtual domains on my system.  Using
sendmail's 'mailertable' database, I direct the mail through the Mprocmail
mailer, using a procmailrc specific to the domain.  The rc file is owned by
the domain's admin user.

With older versions of procmail, this presented no problem -- the various
mailboxen delivered to by procmail would end up being owned by the admin user
for the domain, and all was well.  However, after testing an upgrade, I'm
running into problems with the "Suspicious rcfile" error.  Here's my test
case:

mailertable entry:
test.com        procmail:/usr/local/etc/conundrum/procmailrcs/test.com

the rcfile and containing directory:
drwxr-xr-x  2 root  wheel    512 Dec  5 08:08 procmailrcs/
-r--r--r--  1 test  virtdom  404 Nov 18 17:26 procmailrcs/test.com

And the domain's admin user passwd entry:
test:*:2000:100:test.com:/depot/virtual/test.com/:/bin/false

GID 100 == "virtdom", so I know there isn't a secondary GID problem, which
I've spotted being mentioned on the list.

It would appear that procmail doesn't believe UID 2000 is the appropriate
(Continue reading)

Permalink | Reply | 1 comment |
headers
Nelson Henry Eric | 7 Feb 2002 11:14
Picon

Re: Procmail development (Was: is this procmail rant justified?)

> There may have been a transient DNS or network problem preventing the
> server from resolving your host.

My point is that there are ALWAYS transient DNS or network problems, at
least from about January 4, 2002.

The procmail list will accept mail from user <at> nara.kindai.ac.jp, but not
user <at> irm.nara.kindai.ac.jp.  Those machines are on the same physical lan,
on the same ethernet (163.51.110.0/24) and under the authority of the same
DNS.  I'm just lucky to have had a defunct account on the former which I am
using to subscribe to the list, but it wouldn't surprise me if there are
many, many people worldwide who don't have that luxury and are being denied
access to the list.

I tried.  If no one cares or knows what to do about it, then that's the end
of it.  The problem is way out of my league.  Sorry to have bothered everyone.

henry nelson
_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
Permalink | Reply | 0 comments |
headers
Paul Chvostek | 7 Feb 2002 11:37
Picon
Favicon

Re: "Suspicious rcfile" with virutal domains


Hi Matt.  :)

On Thu, Feb 07, 2002 at 04:03:42AM -0500, Matt of the Long Red Hair wrote:
>
> running into problems with the "Suspicious rcfile" error.  Here's my test
...
> -r--r--r--  1 test  virtdom  404 Nov 18 17:26 procmailrcs/test.com
>
> It would appear that procmail doesn't believe UID 2000 is the appropriate
> owner for this rcfile.  Am I missing something here?

No, you're not missing anything, the user 'test' *is* unsafe as the
owner of a procmailrc that's run by root.

Looking at procmail(1),

       -m   Turns  procmail  into  a general purpose mail filter.
...
            unlimited number of arguments.  If the rcfile  is  an
            absolute  path starting with /usr/local/etc/procmail-
            rcs/ without backward  references  (i.e.  the  parent

> mailertable entry:
> test.com        procmail:/usr/local/etc/conundrum/procmailrcs/test.com

Your conundrum is caused by the conundrum in the directory in the
mailertable.  Wiser heads may give additional details, but this seems
pretty straightforward so far.  With the mismatched directory names,
the -m option hits one of its security checks, and fails with the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Professional Software Engineering | 7 Feb 2002 18:11

Re: Procmail development (Was: is this procmail rant justified?)

At 19:14 2002-02-07 +0900, Nelson Henry Eric wrote:

>My point is that there are ALWAYS transient DNS or network problems, at
>least from about January 4, 2002.

Talk to your network people and ask "what changed?"  Perhaps the host was 
moved, S/W upgraded, or the DNS altered (if you can trust the SOA serial 
number, which in this case is forunatley a dated format, then the most 
recent change was in late October 2001 - perhaps you had insane TTLs 
before, and they've been made reasonable, which then causes the underlying 
network connectivity problems to cause resolution troubles because the host 
isn't cached forever).

>The procmail list will accept mail from user <at> nara.kindai.ac.jp, but not
>user <at> irm.nara.kindai.ac.jp.  Those machines are on the same physical lan,
>on the same ethernet (163.51.110.0/24) and under the authority of the same
>DNS.

... but they're not SERVICED by the same DNS servers:

$ host -t NS irm.nara.kindai.ac.jp
irm.nara.kindai.ac.jp. name server ns.nara.kindai.ac.jp.

$ host -t NS nara.kindai.ac.jp
nara.kindai.ac.jp. name server ns.nara.kindai.ac.jp.
nara.kindai.ac.jp. name server rs6000.cc.kindai.ac.jp.

Okay, so the ONE server that services irm is also used by it's parent 
domain -- but irm only has *ONE*.  The parent domain, which you're capable 
of posting from, has a second NS.  Which means when the common NS is down,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Lars Hecking | 7 Feb 2002 18:39
Picon

Re: Procmail development (Was: is this procmail rant justified?)


> Call me skeptical, but I suspect that ns.nara.kindai.ac.jp has a serious 
> reliability issue.
> 
> Who runs a domain off of a SINGLE nameserver anyway?  Whoever manages the 
> domain is setting themselves up for problems like this.  THAT decision 
> certainly cannot be blamed on the procmail list...

 Even more off-topic, but most ns.*.jp hosts also appear to function
 as open relays. I have blacklisted over 60 so far, after receiving spam.

_______________________________________________
procmail mailing list
procmail <at> lists.RWTH-Aachen.DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
Permalink | Reply | 0 comments |

Gmane