On Nov 12, 2004, at 4:15 PM PST, [EMAIL PROTECTED] wrote:
From: Sam Varshavchik <[EMAIL PROTECTED]>
Date: November 12, 2004 4:15:58 PM PST
To: [EMAIL PROTECTED]
Subject: Re: [courier-users] Can Courier call external mailers for
certain outgoing addresses?
Greg Earle writes:
overloaded central se
On Nov 20, 2004, at 2:33 AM, [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
Date: November 20, 2004 2:33:04 AM PST
To: courier-users <[EMAIL PROTECTED]>
Subject: Re: [courier-users] Re: Can Courier call external mailers for
certain outgoing addresses?
Reply-To: [EMAIL PROTECTED]
-
Greg Earle writes:
Hmmn, OK. I *did* read dot-courier(5), from head to toe, and am
looking at it now, again. All I saw was
RUNNING AN EXTERNAL PROGRAM
Lines that begin with a single | character run an external
program. The rest of the line specifies the command to be
exe
On Nov 21, 2004, at 7:14 AM, [EMAIL PROTECTED] wrote:
Greg Earle writes:
Hmmn, OK. I *did* read dot-courier(5), from head to toe, and am
looking at it now, again. All I saw was
RUNNING AN EXTERNAL PROGRAM
Lines that begin with a single | character run an external
program. The r
Greg Earle writes:
If so, should I be using something like "$USER"@"$LOCAL" instead (to get
just-plain "[EMAIL PROTECTED]" fed to the external X.500
mailer)? Or perhaps "$EXT"@"$LOCAL"? (I'm a bit confused by the
"EXT"/"EXT2"/"EXT3"/"EXT4" stuff in dot-courier(5), to be honest -
perhaps an examp
On Nov 21, 2004, at 3:03 PM, [EMAIL PROTECTED] wrote:
Greg Earle writes:
If so, should I be using something like "$USER"@"$LOCAL" instead (to
get just-plain "[EMAIL PROTECTED]" fed to the external
X.500 mailer)? Or perhaps "$EXT"@"$LOCAL"? (I'm a bit confused by
the "EXT"/"EXT2"/"EXT3"/"EXT4" stu
Greg Earle writes:
@domain: user
This special entry results in any recipient address of the
form [EMAIL PROTECTED] to be rewritten as [EMAIL PROTECTED], where me is
the hostname of the machine, which we expect to be a local
domain.
The trouble is, I don't want vir
On Nov 24, 2004, at 11:48 AM, [EMAIL PROTECTED] wrote:
I traced the output of the "couriertcpd" process that accepted
the outgoing mail, and curiously, I saw the ".courier-x500-default"
file accessed, but never read!
Correct. The job of the process kicked off by couriertcpd is to
accept a message
On Nov 23, 2004, at 4:31 PM, [EMAIL PROTECTED] wrote:
Greg Earle writes:
@domain: user
This special entry results in any recipient address of the
form [EMAIL PROTECTED] to be rewritten as [EMAIL PROTECTED], where me is
the hostname of the machine, which we expect to be a
--On 19. November 2004 21:34 -0800 Greg Earle <[EMAIL PROTECTED]>
wrote:
Finally had a chance to try it out and got some strangeness:
isolar:1:81 [/opt/courier/etc/aliasdir] # cat .courier-x500-default
'|/usr/local/sbin/mail500 -f "$SENDER" -h "$HOST" -m
[EMAIL PROTECTED] "$RECIPIENT"'
drop the s
10 matches
Mail list logo
