I thought as much, unfortunately, since the local accounts have an '@' sign in them, using procmail as local delivery seems to not be happy.

So now the question becomes:
Is there a way to get postfix to allow '@' signs as part of a user name when using the local transport?

eg: for my email account which is:

[root@email postfix]# getent passwd brian.and...@firstspot.net
brian.and...@firstspot.net:x:7453:1500:Brian Andrus:/domains/firstspot.net/users/brian.andrus:/bin/bash


If I use local delivery, it bounces with:

This is the mail system at host smtp.firstspot.net.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<brian.and...@firstspot.net>: unknown user: "brian.andrus"



Brian Andrus


On 7/19/2011 9:09 AM, Victor Duchovni wrote:
On Tue, Jul 19, 2011 at 09:01:43AM -0700, Brian Andrus wrote:

I wanted to use one of the built-in variables for the user= portion of a
pipe in master.cf, but it seems postfix does not substitute it for that
part.
Correct, reasonable and not surprising. Only the "argv" list supports
variable interpolation.

Is this the case? Is it possible to do something like:

procmail  unix -        n       n       -       -       pipe
   -o flags=RO user=${recipient} argv=/usr/bin/procmail -t -d
EXTENSION=${extension}
No. However, you can use "procmail" via local(8), in mailbox_command
or mailbox_command_maps, (or via .forward files). All of these do run
as the target user.

In the end, I am just trying to get procmail to run as the user so I can
have individual .procmailrc files process their email rules.
Running code as the target user is local(8)'s job. You can have more
than one local(8) transport if your needs are sufficiently complex to
drive you in that direction (multiple groups of settings for aliases,
forward_path, ...)



--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply via email to