Re: [Mimedefang] REPOST: SECURITY: MIME-tools patch

[Kevin A. McGrail]

David,

What is your opinion of the severity of the bug?  Does it crash MD?  Will an
A/V scan still detect the issue?

Regards,
KAM

___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

[Mimedefang] REPOST: SECURITY: MIME-tools patch

[David F. Skoll]

Hi,

I just realized that PGP mangles patches.  Oh, well.  Here it is unsigned;
check the signed message to make sure you're not being trojaned. :-)

Regards,

David.

===
RCS file: /home/cvsroot/MIME-tools/lib/MIME/Field/ParamVal.pm,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -p -r1.3 -r1.4
--- MIME-tools/lib/MIME/Field/ParamVal.pm   2004/10/06 18:55:27 1.3
+++ MIME-tools/lib/MIME/Field/ParamVal.pm   2004/10/27 01:41:02 1.4
@@ -236,7 +236,7 @@ sub parse_params {
$raw =~ m/\G$SPCZ\;$SPCZ/og or last; # skip leading separator
$raw =~ m/\G($PARAMNAME)\s*=\s*/og or last;  # give up if not a param
$param = lc($1);
-   $raw =~ m/\G(\"([^\"]+)\")|\G($ENCTOKEN)|\G($BADTOKEN)|\G($TOKEN)/g or last;   
# give up if no value"
+   $raw =~ m/\G(\"([^\"]*)\")|\G($ENCTOKEN)|\G($BADTOKEN)|\G($TOKEN)/g or last;   
# give up if no value"
my ($qstr, $str, $enctoken, $badtoken, $token) = ($1, $2, $3, $4, $5);
if (defined($badtoken)) {
# Strip leading/trailing whitespace from badtoken
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

[Mimedefang] SECURITY: Patch for MIME-tools

[David F. Skoll]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

There's a bug in MIME-tools:  It mis-parses things like

boundary=""

and apparently there's a virus that uses an empty boundary.  You probably
want to patch your MIME-tools installation with this patch; I'll be
releasing a new MIME-tools tomorrow.

Patch below is against MIME-tools 5.414.  Thanks to Stephane Lentz
and Julian Field for discovering the bug and bringing it to my attention.

Regards,

David.


===
RCS file: /home/cvsroot/MIME-tools/lib/MIME/Field/ParamVal.pm,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -p -r1.3 -r1.4
- --- MIME-tools/lib/MIME/Field/ParamVal.pm 2004/10/06 18:55:27 1.3
+++ MIME-tools/lib/MIME/Field/ParamVal.pm   2004/10/27 01:41:02 1.4
@@ -236,7 +236,7 @@ sub parse_params {
$raw =~ m/\G$SPCZ\;$SPCZ/og or last; # skip leading separator
$raw =~ m/\G($PARAMNAME)\s*=\s*/og or last;  # give up if not a param
$param = lc($1);
- - $raw =~ m/\G(\"([^\"]+)\")|\G($ENCTOKEN)|\G($BADTOKEN)|\G($TOKEN)/g or last;   
# give up if no value"
+   $raw =~ m/\G(\"([^\"]*)\")|\G($ENCTOKEN)|\G($BADTOKEN)|\G($TOKEN)/g or last;   
# give up if no value"
my ($qstr, $str, $enctoken, $badtoken, $token) = ($1, $2, $3, $4, $5);
if (defined($badtoken)) {
# Strip leading/trailing whitespace from badtoken




-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFBfv93dB1gkTPXMwsRAsrjAJ0fjmZasQ7pY/zFHHmPtPZfJm1SOQCfcYYi
oz3sasoVDlAl6Y1Wby+Ly1Q=
=J+wt
-END PGP SIGNATURE-
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] MIMEDefang 2.46-BETA-1 is available

[Aleksandar Milivojevic]

David F. Skoll wrote:
Hi,
MIMEDefang 2.46-BETA-1 is available at http://www.mimedefang.org/node.php?id=1
I've just compiled it.  However, I'm having two problems with it 
(regarding my previous mail about detecting content-type in filter_end).

First is that Content-Type (as present in $entity) still isn't as 
present in the email message itself.

For example, if Content-Type is:
   multipart/report; report-type=disposition-notification;
   boundary="mdn020605010008050205010504"
$entity->head->get("content-type") returns:
   multipart/report; boundary="mdn020605010008050205010504"
The report-type (which is mandatory for multipart/report type) is 
completely ommited, which makes the returned value unusable (I don't 
know if it is bounce generated by MTA, return receipt generated by MUA, 
or something else).

The second problem is that I can't seem to be able to check for presence 
of certain headers.  For example, this doesn't work:

   if ($entity->head->get("disposition-notification-to")) {
   ...
   }
(always returns undef).
--
Aleksandar Milivojevic <[EMAIL PROTECTED]>Pollard Banknote Limited
Systems Administrator   1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB  R3T 1L7
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] MIMEDefang 2.45 compile errors ??

[Brent J. Nordquist]

On Sun, Oct 24, 2004 at 12:47:45PM +1000, Bill Maidment wrote:
> Brent J. Nordquist wrote:
> >What I'm discovering about Perl under FC2 x86_64 is that things seem
> >to be split between /usr/lib and /usr/lib64.
> >[...]
> >Using --disable-check-perl-modules at least fixed the warning,
> 
> [...]
> but it still crashes, because the wrong modules are accessed at run time.
> 
> The only way is to go searching for the old modules and delete them.

I've now confirmed that this patch allows MD 2.45 to work fine on FC2
x86_64:

=== cut here ===
--- /usr/local/src/mimedefang-2.45/mimedefang.pl2004-10-23 11:19:22.0 
-0500
+++ mimedefang.pl   2004-10-26 10:20:46.0 -0500
@@ -24,6 +24,7 @@
 # Move site library directory ahead of default library directory in @INC.
 # That's so we can sanely package our own version of MIME::Base64 that
 # won't conflict with the built-in one on RPM-based platforms.
+use lib '/usr/lib64/perl5/site_perl/5.8.3';
 use lib '/usr/lib/perl5/site_perl/5.8.3';
 
 # MIME-Tools requires this?
=== cut here ===

I have some FC2 x86_64 RPMs (such as perl-MIME-Base64-3.05, which doesn't
conflict with Fedora's, so you don't have to "clean out old modules")
and other notes on my work-in-progress here:

http://kepler.its.bethel.edu/~bjn/spamassassin/

-- 
Brent J. Nordquist <[EMAIL PROTECTED]> N0BJN
Other contact information: http://kepler.its.bethel.edu/~bjn/contact.html
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

[Mimedefang] MIMEDefang 2.46-BETA-1 is available

[David F. Skoll]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

MIMEDefang 2.46-BETA-1 is available at http://www.mimedefang.org/node.php?id=1

The main change is a fix to the way messages are rebuilt.  Now,
filter_end sees the true type of the message (rather than always getting
a multipart/mixed entity).  Also, action_add_part won't break
PGP/MIME messages or other multipart messages that aren't multipart/mixed.

Complete changelog to 2.45 follows.

Regards,

David.

2004-10-26  David F. Skoll  <[EMAIL PROTECTED]>

* mimedefang-filter.5.in: Corrected an error in one of the examples

* mimedefang.c: Add IP address of scanning host to X-Scanned-By:
header.

* SECURITY FIX: mimedefang.c: Tempfail message if RESULTS file
doesn't terminate with 'F' line.  (Detects disk-full condition.)

* mimedefang.pl.in (rebuild_entity): Add a Content-Type: header
if MIME part lacks one.  Some marginal e-mail software chokes on
a part with a missing content-type header.

* mimedefang.pl.in: flatten_mime removed.  Support for
$Stupidity{"flatten"} removed.  *** NOTE INCOMPATIBILITY ***

* action_add_part revamped completely; we try to preserve original
multipart type of message.  action_add_part now simply keeps a list
of parts to be added.  At the end:

a) If original message was multipart/mixed, we simply add
the part.

b) Otherwise, we make a new multipart/mixed container, put
original message as the first part of this new container, and
then add part to the multipart/mixed container.

*** NOTE INCOMPATIBILITY ***

* Proper multipart type passed to filter_end.

* All mimedefang.pl-generated messages have an
Auto-Submitted: auto-generated header.

* mimedefang.pl.in: Return codes of I/O operations are checked; we
die if any fail.  This is a security fix.

* mimedefang.pl.in (interpret_trend_code): Treat any code from
1 to 9 as indicative of a virus, upon recommendation of Stephane Lentz.

* mimedefang.pl.in (spam_assassin_init): Add a
LOCAL_RULES_DIR => @CONFDIR@/spamassassin argument to SpamAssassin
constructor.

2004-09-22  David F. Skoll  <[EMAIL PROTECTED]>

* Version 2.45 RELEASED



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFBfpwTdB1gkTPXMwsRAmNWAJ4kwxg9ZW0gwyorLEkM0Kf4KpOQ0gCfSNJW
smd6Xv1QzHDpQostvyL6YYg=
=e4n7
-END PGP SIGNATURE-
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] FYI: SOCKETMAP added to Red Hat sendmail package

[Kenneth Porter]

--On Tuesday, October 26, 2004 7:50 PM +0200 Alexander Dalloz 
<[EMAIL PROTECTED]> wrote:

I didn't understand Thomas Wörner's WONTFIX bugzilla
closure.
He was probably new to packaging and didn't realize that the Perl 
dependency in the example code was a non-issue. That was my assumption when 
I wrote my counter-argument. (It was only in the last couple of years that 
RPM stopped evaluating dependencies on material in %doc, the usual place to 
put example code.)


___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] FYI: SOCKETMAP added to Red Hat sendmail package

[Alexander Dalloz]

Am Di, den 26.10.2004 schrieb Kenneth Porter um 18:42:

> 

That is good news! I didn't understand Thomas Wörner's WONTFIX bugzilla
closure. I had opened a different bugzilla entry, because in former
Sendmail 8.13 RPM the socketmap support already appeared as a new
feature in the changelog. He closed that by stating it was a changelog
bug only ;)

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp 
Serendipity 19:47:35 up 6 days, 16:27, load average: 0.34, 0.22, 0.35 

___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

[Mimedefang] FYI: SOCKETMAP added to Red Hat sendmail package

[Kenneth Porter]

___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Memory problems

[Mike Lambert]

I wrote:
I had MX_MAX_AS set to 6 and hit the limit within a few hours. MX_MAX_AS 
is now set to 10. SA is not definitely a memory pig.
Opps. s/not definitely/most definitely/
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Detecting content-type of message in filter_end

[David F. Skoll]

On Tue, 26 Oct 2004, Aleksandar Milivojevic wrote:

>   I guess the release that fixes this bug will be 2.46?

Yup.  It will be out very soon.

Regards,

David.
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Detecting content-type of message in filter_end

[Aleksandar Milivojevic]

David F. Skoll wrote:
There's a bug in MIMEDefang; the rebuilt entry that gets passed to filter_end
is always of type multipart/mixed, multipart/alternative or multipart/digest.
The next release will fix this.
I see there's MIMEDefang 2.45 on the web site (I was still using 2.44). 
 I guess the release that fixes this bug will be 2.46?

--
Aleksandar Milivojevic <[EMAIL PROTECTED]>Pollard Banknote Limited
Systems Administrator   1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB  R3T 1L7
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Gentoo packaging : mimedefang ebuild (for MIMEDefang 2.45)

[David F. Skoll]

Hi, Stephane.

> So find attached an alpha/beta mimedefang Gentoo ebuild (aka FreeBSD port)
> with the needed conf.d and init.d files.

Thanks!

> Please let me know how about bugs/enhancements so this either gets included
> in the Gentoo portage tree or in the next MIMEDefang tarball (David
> it's up to you to decice).

Well, there's a slight difficulty with including an ebuild in the tarball,
because one of the things in the ebuild is the MD5 sum of the tarball.
Once we work our way past this minor stumbling block... :-)

I might distribute the ebuild from the MIMEDefang site, though.
I plan on releasing 2.46 very soon, and after that, I'll accept the
ebuild and put it on the site.

Regards,

David.
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Memory problems

[Mike Lambert]

On Mon, 25 Oct 2004, David F. Skoll wrote:
On Mon, 25 Oct 2004, Rob MacGregor wrote:
MX_MAX_RSS=1
MX_MAX_AS=3
That's probably too low.  SA is a memory pig; I'd give the slaves 50MB
at least, and take out the RSS limit altogether.
I had MX_MAX_AS set to 6 and hit the limit within a few hours. 
MX_MAX_AS is now set to 10. SA is not definitely a memory pig.

Regards,
Mike Lambert
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Detecting content-type of message in filter_end

[David F. Skoll]

On Tue, 26 Oct 2004, Aleksandar Milivojevic wrote:

> BTW, while we are at it.  Is there a reason why $entity is not passed as
> an argument to filter_begin?  It could be usefull if it was possible to
> do some checks on the message before it is modified by MIMEDefang.  It
> would be more efficient if I don't need to wait until filter_end to do
> some simple checks.

It's for historical reasons; changing it now would break a lot of filters.
It's probably not more efficient anyway, because MIMEDefang always
loops through filter_begin / filter - filter - ... - filter / filter_end
anyway.  You can do a test in filter_begin and use the results of that
test to bail out of filter processing if you really need the speedup.

Regards,

David.
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Detecting content-type of message in filter_end

[Aleksandar Milivojevic]

David F. Skoll wrote:
There's a bug in MIMEDefang; the rebuilt entry that gets passed to filter_end
is always of type multipart/mixed, multipart/alternative or multipart/digest.
The next release will fix this.
BTW, while we are at it.  Is there a reason why $entity is not passed as 
an argument to filter_begin?  It could be usefull if it was possible to 
do some checks on the message before it is modified by MIMEDefang.  It 
would be more efficient if I don't need to wait until filter_end to do 
some simple checks.

--
Aleksandar Milivojevic <[EMAIL PROTECTED]>Pollard Banknote Limited
Systems Administrator   1499 Buffalo Place
Tel: (204) 474-2323 ext 276 Winnipeg, MB  R3T 1L7
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] MIMEDefang + spamd

[David F. Skoll]

On Tue, 26 Oct 2004, Steffen Kaiser wrote:

> Might spamc/spamd gains from the fact that spamd pre-loads more things and
> caches certain internal stuff, which is shared among multiple spamd
> slaves, instead of kept into each MIMEDefang slave?

Unlikely.  I think the real speedup comes if there are fewer spamd slaves
than MIMEDefang slaves.

> You've said to switch to embedded Perl to avoid those problems, so the
> answer probably is no.

Even embedded Perl doesn't help much, unfortunately.  Perl uses a
reference-counting mechanism for garbage collection, which virtually ensures
that every page of memory gets written to, meaning slaves cannot share much
data. :-(  It's a serious shortcoming of Perl.

> Anyway, would it be possible to use the spampd API directly, instead of to
> call spamc? That way one could measure the speed factor and useage of
> resources better. (No, I don't volunteer ;-)

Sure.

Regards,

David.
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Gentoo packaging : mimedefang ebuild (for MIMEDefang 2.45)

[TFL]

Oh.. great, a new version of MIME-Tools. I was thinking about the same project
and did not start because of the patched perlmodule.

Good news!

Regards, Mike


No Six <[EMAIL PROTECTED]> said:

> On Tue, Oct 26, 2004 at 07:24:55AM +0200, [EMAIL PROTECTED] wrote:
> > 
> > -
> > I've started working on making MIMEDefang installation on Gentoo Linux
> > easier
> > (we must contribute to OpenSource folks someway ...).
> > 
> > Please note that the MIME-tools MIME-Base64 ebuils in Gentoo are up to
> > date (respectively versions 5.414 and 3.05) so no manual perl 
> > 
> > -- 
> > 
> > Nice job. I think you should add the patched version of MIME-tools and
> > prevent the other one from emerging.
> > 
> > Regards, Mike
> > 
> > 
> I don't agree : we should now use MIME-tools 5.414 instead of the old
> patched version as mentioned on http://www.mimedefang.org/node.php?id=1
> 
> MIME-tools 5.414 is available in Portage so let's use it.
> 
> Number Six
> ___
> Visit http://www.mimedefang.org and http://www.canit.ca
> MIMEDefang mailing list
> [EMAIL PROTECTED]
> http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
> 
> 



-- 



___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] Gentoo packaging : mimedefang ebuild (for MIMEDefang 2.45)

[No Six]

On Tue, Oct 26, 2004 at 07:24:55AM +0200, [EMAIL PROTECTED] wrote:
> 
> -
> I've started working on making MIMEDefang installation on Gentoo Linux
> easier
> (we must contribute to OpenSource folks someway ...).
> 
> Please note that the MIME-tools MIME-Base64 ebuils in Gentoo are up to
> date (respectively versions 5.414 and 3.05) so no manual perl 
> 
> -- 
> 
> Nice job. I think you should add the patched version of MIME-tools and
> prevent the other one from emerging.
> 
> Regards, Mike
> 
> 
I don't agree : we should now use MIME-tools 5.414 instead of the old
patched version as mentioned on http://www.mimedefang.org/node.php?id=1

MIME-tools 5.414 is available in Portage so let's use it.

Number Six
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] MIMEDefang + spamd

[Steffen Kaiser]

On Wed, 22 Sep 2004, David F. Skoll wrote:
On Wed, 22 Sep 2004, John Scully wrote:
On any system with a lot of rule sets SA represents about 90% of the total
message prosessing time.  C vs perl makes a difference on that part.
Yes, but I fail to see how spamd helps -- it still must, ultimately,
call into the exact same Perl API as any other SA user.
Might spamc/spamd gains from the fact that spamd pre-loads more things and 
caches certain internal stuff, which is shared among multiple spamd 
slaves, instead of kept into each MIMEDefang slave?

You've said to switch to embedded Perl to avoid those problems, so the 
answer probably is no.

Anyway, would it be possible to use the spampd API directly, instead of to 
call spamc? That way one could measure the speed factor and useage of 
resources better. (No, I don't volunteer ;-)

Bye,
--
Steffen Kaiser
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

[Mimedefang] Brokwn Pipe

[Trevor Dodds]

Hi,

I've been receiving a few of these messages in my syslog.

Oct 25 17:43:15 crow sendmail[3932]: [ID 801593 mail.info] i9PFhEn7003932:
Milter (mimedefang): init success to negotiate
Oct 25 17:43:15 crow sendmail[3932]: [ID 801593 mail.info] i9PFhEn7003932:
Milter: connect to filters
Oct 25 20:34:38 crow sendmail[3932]: [ID 801593 mail.info] i9PFhEn7003932:
from=<[EMAIL PROTECTED]>, size=39505214, class=0, nrcpts=1,
msgid=<[EMAIL PROTECTED]>, proto=ESMTP,
daemon=MTA, relay=racine.hfp.fr [62.23.99.130]
Oct 25 20:34:38 crow sendmail[3932]: [ID 801593 mail.error] i9PFhEn7003932:
Milter (mimedefang): write(L) returned -1, expected 185: Broken pipe
Oct 25 20:34:38 crow sendmail[3932]: [ID 801593 mail.info] i9PFhEn7003932:
Milter (mimedefang): to error state
Oct 25 20:34:38 crow sendmail[3932]: [ID 801593 mail.info] i9PFhEn7003932:
Milter: data, reject=451 4.3.2 Please try again later
Oct 25 20:34:38 crow sendmail[3932]: [ID 801593 mail.info] i9PFhEn7003932:
to=<[EMAIL PROTECTED]>, delay=02:51:21, pri=39535214, stat=Please try again
later

My config is as follows:
/usr/local/bin/mimedefang-multiplexor -U defang -p
/var/run/mimedefang-multiplexor.pid -m 8 -x 12 -b 300 -i 600 -q 30 -Q120 -r
500 -E -l
/usr/local/bin/mimedefang -U defang -r -P /var/run/mimedefang.pid -p
/var/spool/MIMEDefang/mimedefang.sock -m
/var/spool/MIMEDefang/mimedefang-multiplexor.sock

Thanks
Trevor

___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang