[Mimedefang] Restrictions on the use of stream_by_recipient()

Robert Clark clark at exiter.com
Mon Dec 13 22:12:33 EST 2004


In article <200412131225.iBDCPk0x007450 at vtn1.victoria.tc.ca>, John Nemeth
<jnemeth at victoria.tc.ca> wrote:

> On May 4,  2:41pm, "Robert J. Clark" wrote:
> }   Can I do these checks and bounce the message (call
> }   action_tempfail() or action_discard() and return) before I call
> }   stream_by_recipient()?
> 
>      Yes.

Cool. that makes my life easier.

> 
> }   Is there anything I need to watch out for when I do this?
> 
>      You need a way to detect if you've seen the message already.
> Luckily, MIMEDefang provides a way of doing this.  Here's my
> filter_begin():

[ ... chomp ... ]

Look good. I am now using a very similar layout an it seem to be working
well.
 
>      Read the section called, PRESERVING RELAY INFORMATION, in the
> mimedefang-filter manpage.

Hmmm, I though that was just for going from MX to MX. I did not realize that
it could be used for preserving info across stream_by_* calls. Of course,
since all it does is add a header, I guess I should have picked up on that.
Must be this cold ...

After a bit of a false start getting the /etc/mail/mimedefang-ip-key file in
place (a filter reload will not pick it up, you have to do a full restart
of MIMEDefang) everything seems to be working fine.

Thanks for information.

- Rob




More information about the MIMEDefang mailing list