|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Always Bcc and discard difficulty
From: Greg Wood (greg
woodtech.biz)
Date: Thu Nov 02 2006 - 10:15:47 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I spoke too soon :-(
I have eliminated the mailer-daemon and copy of email being sent to
admin
example.com.
But a copy is still going to always_bcc (I guess the clue is in the
"always")
I would prefer if there was a way to prevent this but I am guessing I
need to use recipient_bcc_maps and sender_bcc_maps.
If so, I would like to know if I can point the maps to the unix user
list (and later to ldap) so that updating user changes only need be done
in one place. I expect something like sender_bcc_maps =
hash:/etc/postfix/sender_bcc.
But I am not sure of the syntax for the :/etc/postfix/sender_bcc file
to point to unix users.
Thanks in anticipation.
Greg
Greg Wood wrote:
> Hello mouss,
>
> Absolutely spot on. Apparmor blocking the transport. (2nd time it's
> caught me out. It blocked cyrus as well.) Was easily reset to allow
> access.
>
> Thank you to all on a great forum.
>
> Greg
>
> mouss wrote:
>
>> Greg Wood wrote:
>>
>>> Hello mouss,
>>>
>>> Thank you for the help thus far. I have a further problem.
>>>
>>> I am now getting a mail log file:
>>> " warning: connect to transport discard: Operation not permitted "
>>
>>
>>
>> Is this box running linux? if so, disable selinux/apparmor/$friends
>> (check /var/log/messages, /var/log/secure, /var/log/audit, ... for
>> "signs")
>>
>>
>>
>>
>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]