OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
RE: Message-id problem

From: Thomas A. Luther (tompnss.cc)
Date: Thu Apr 01 2004 - 19:32:05 CST


So far I have this in the header_checks file

/^Message-Id: <\([^]*\)spamfilterabc.com / Message-Id:
<\1spamfiltertest.com>

But it doesn't seem to work? Where did I go wrong? Any ideas?

Thanks,

-Tom

Thomas A. Luther
Practical Network Security Solutions, Inc.
1745 Hillside Road
Southampton, PA 18966
(215) 669-9094
"This email may contain material that is confidential, and proprietary
to Practical Network Security Solutions, Inc., for the sole use of the
intended recipient. Any review, reliance or distribution by others or
forwarding without express permission is strictly prohibited. If you are
not the intended recipient, please contact the sender and delete all
copies."

-----Original Message-----
From: Wietse Venema [mailto:wietseporcupine.org]
Sent: Thursday, April 01, 2004 7:04 PM
To: Thomas A. Luther
Cc: postfix-userspostfix.org
Subject: Re: Message-id problem

Thomas A. Luther:
> I have a customer who has a situation where they have 6 different
> companies/domains working out of the same office using same equipment.
> We've set up postfix and it's working great. The problem is that all
> 6 companies have to appear completely separate and not associated with

> each other in anyway. We've setup separate identities in outlook
> express for this purpose.
>
> We've registered a domain, for this example call it generic.com.
> Everything appears to be originating at generic.com. Everything
works
> fine except that the damn message-id in the outbound header is tagged
> with the domain, abc.com, of the client machines using outlook
express.
>
> So in a nutshell, I need to change every outbound message-id to have
> generic.com instead of abc.com.
>
> Take this: Message-ID: <000801c41838$8ac8d7f0$b301a8c0abc.com>
> And turn it into this: Message-ID:
> <000801c41838$8ac8d7f0$b301a8c0generic.com>
> Any ideas?

This would be a good reason to implement the "REPLACE" header_checks
action.

        Wietse