Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: jeff donovan (donovanbeth.k12.pa.us)
Date: Mon May 12 2008 - 08:51:20 CDT
On May 9, 2008, at 2:00 PM, Noel Jones wrote:
> jeff donovan wrote:
>> On May 9, 2008, at 11:11 AM, Wietse Venema wrote:
>>> jeff donovan:
>>>> can I do this without an if then endif?
>>>> /^to: *friendpublic\.com$ && ^from: *usernameexample.com/ WARN
>>> man header_checks
>>> All supported behavior is documented.
>> Ah yes,..
>> okay did a bunch of reading. and the reoccurring theme is ;
>> Header (and body) checks process one header (or line, with body
>> checks) at a time.
>> So my question is.
>> is there a better way to reject/bounce/warn when a message from
>> user1domain to user2domain shows up?
>> simliar to this, although I know this wont work.
>> if /^To:.*postmasterexample\.com/ /^From: user2example\.com/ WARN
> Yes, but do it with smtpd restrictions rather than header_checks.
> Please see:
> Noel Jones
thanks for the reply Noel,
i read through this but I still did not see any method of denying
access from one user to another within the same domain.
like if I had a test group that i did not want to be able to send
messages to. without creating another domain name. ( these are all
internal only )
i was hoping to do something like this within the recipient
/^to: joeusermy\.domain\.com$ | ^from: someusermy\.domain\.com/ REJECT
would I need the " \ " before the " . " guess not if i use a regular
access data base.