aboutsummaryrefslogtreecommitdiffstats
path: root/contrib/novell
blob: 1e549aedafe584d71b488f575af1fea7e6422569 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
From newcombe@mordor.clayton.edu  Thu Jun 12 15:56:44 1997
Return-Path: <newcombe@mordor.clayton.edu>
Received: from imap.ccil.org (snark [10.0.2.15])
	by snark.thyrsus.com (8.8.5/8.8.5) with ESMTP id PAA11433
	for <esr>; Thu, 12 Jun 1997 15:56:43 -0400
Received: from thrush.clayton.edu (thrush.clayton.edu [168.28.242.117])
	by locke.ccil.org (8.8.5/8.8.5) with ESMTP id LAA17702
	for <esr@snark.thyrsus.com>; Thu, 12 Jun 1997 11:29:02 -0400 (EDT)
Received: from mordor.clayton.edu (root@mordor.clayton.edu [168.28.241.16]) by thrush.clayton.edu (8.8.5/8.7.6) with SMTP id LAA22880 for <esr@snark.thyrsus.com>; Thu, 12 Jun 1997 11:11:51 -0400 (EDT)
Date: Thu, 12 Jun 1997 11:28:05 -0400 (EDT)
From: Dan Newcombe <newcombe@mordor.clayton.edu>
X-Sender: root@mordor.clayton.edu
Reply-To: newcombe@mordor.clayton.edu
To: esr@snark.thyrsus.com
Subject: Novell Procmail recipie/problem
Message-ID: <Pine.LNX.3.96.970612112225.14988A-100000@mordor.clayton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Status: RO

Eric,

  As per your request, here is my recipie for dealing with e-mail popped
off of a Novell server and told to be domanified.
And example of the problem I used to have when I popped mail off of
aa.clayton.edu   From: User <AA/USER@aa.clayton.edu>
Sendmail did not like that.  Now it converts the above to
From: User <USER@AA.clayton.edu>

However, the To: and CC: lines still can get messed up
To: aa/user2,@aa.clayton.edu aa/newcombe

I'm not going to worry about that!!!

I fixed it with this recipie in my .procmailrc
:0
* ^From:.*<.*/.*@
{
:0 fhw
|sed -e 's/^From:\(.*\)<\(.*\)\/\(.*\)@.*/From:\1<\3@\2.clayton.edu>/'
}

It may not be the best, prettiest, or most efficient, but it works.

Also, you'd asked me to send you the sometimes error message I get
from fetchmail.  I don't see one in my Mail/From file, so it must not
have happened for a while.  It looked something like
Subject: Cron <root@mordor> /usr/local/bin/fetchmail: 29483

Hope your flight back was good.
	-Dan

--
Dan Newcombe                                      newcombe@mordor.clayton.edu
"The fool who escaped from paradise will look over his shoulders and cry...So
I'll hold my peace forever when you wear your bridal gown."   -Marillion
d a compiler that isn't lying about being ANSI-compliant (such as gcc). Some SunOS users have had this problem. 3. INSTALL Lastly, become root and run make install This will install fetchmail. By default, fetchmail will be installed in /usr/local/bin, with the man page in /usr/local/man/man1. If you wish to change these defaults, edit the Makefile AFTER you run "configure" but BEFORE you run "make install." You can easily choose a prefix other than /usr/local, or you can choose completely different directories for each item. NOTE: If you are using exim, you must configure it to accept local addresses as valid RCPT TO lines. 4. SET UP A RUN CONTROL FILE See the man page or the file sample.rcfile for a description of how to configure your individual preferences. If you're upgrading from popclient, see question F4 in the FAQ file. 5. TEST I strongly recommend that your first fetchmail run use the -v and -k options, in case there is something not quite right with your server, your local delivery configuration or your port 25 listener. Also, beware of aliases that direct your local mail back to the server host! This software is known to work with the qpop/popper series of freeware POP3 servers; also with the IMAP2bis and IMAP4 servers that are distributed with Pine from the University of Washington. A couple of users have reported that some recent (post-2.7.2) versions of gcc seem to have an optimizer bug that affects fetchmail. If your fetchmail core dumps (especially near startup) try recompiling without -O. Alternatively, you can drop back to gcc 2.7.2 or below. 6. REPORTING BUGS You should read the FAQ file question G1 before reporting a bug. 7. USE IT Enjoy!