> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Al Sparks
>
> So my question is, how do I know anything is happening?
Well, if you're using the stock setup and have put the entries into
sendmail.mc, then rebuild sendmail.cf and restarted sendmai
Lucas Albers wrote:
> Fred go do man mimedefang-filter and read about:
> PRESERVING RELAY INFORMATION
>
>This resets the relay address and hostname to the actual relay
> address and hostname, unless the message is coming from
>one of your other MX hosts.
Hello,
You mis-understood
New MIMEDefang user.
I've installed MIMEDefang on a system that already had sendmail
8.12.10 installed. I did the necessary changes to get milter going
and re-compiled. I hope.
I installed MIMEDefang using the CPAN install mechanism (i.e. I run
"perl -MCPAN -e shell" and at the prompt from ther
On Fri, 26 Mar 2004 12:18:59 -0500, Paul Whittney mentioned:
>Using the init script with mimedefang (versions 2.39, 2.40, and 2.41) I
>am able to start and stop the mimedefang processes (mainly because I'm
>testing all sorts of perl scripts away from the main system), however,
>mimedefang doesn't
Fred go do man mimedefang-filter and read about:
PRESERVING RELAY INFORMATION
This resets the relay address and hostname to the actual relay
address and hostname, unless the message is coming from
one of your other MX hosts.
Fred said:
> Hello,
> I'm wondering if it would be a goo
On Tue, 30 Mar 2004, Kevin A. McGrail wrote:
> #1 -- The mimedefang-init in the redhat dir still uses kill -INT for the
> re-read. I believe it should be changed to do the equivalent of
> /usr/local/bin/md-mx-ctrl reread.
OK; I will fix it.
> #2 -- You might want to add the Archive-Zip to your
I am happy to report we have only two minor comments for the Beta process:
#1 -- The mimedefang-init in the redhat dir still uses kill -INT for the
re-read. I believe it should be changed to do the equivalent of
/usr/local/bin/md-mx-ctrl reread. This was brought up by someone else and I
am sorry
You would need to contact the site that sent this to you. You can find
this by looking at the headers of the email (in various tools it is view
full headers under view or show. ) One of the machines in the
'Recieved:' list has installed mimedefang incorrectly as they should
have defined $AdminAdres
Hello everybody!
Well, I would like to know how can I stop receiving
the message below:
WARNING: This e-mail has been altered by MIMEDefang.
Following this
paragraph are indications of the actual changes made.
For more information about
your site's MIMEDefang policy, contact $AdminAdress.
For
At 07:02 AM 3/30/2004, [EMAIL PROTECTED] wrote:
In my mimedefang-filter, i have
if (filter_bad_filename($entity)) {
md_graphdefang_log('bad_filename', $fname, $type);
return action_bounce("$ext found in mail - rejected");
}
My problem is, the mail est rejecter and mimedefa
I guess I should have been more thorough before wasting a bunch of e-mails
in the mailing list. My sincere apologies.
In the error message that I previously posted, I noticed that it ended in
...mimedefang.sock' is unsafe. Notice the apostrophe after sock.
The issue turned out to be a typo in t
I've troubleshot this further and have additional information.
Permissions appear to be correct:
drwxr-xr-x 20 root root 4096 Mar 30 12:33 /
drwxr-xr-x 19 root root 4096 Mar 26 15:16 /var
drwxr-xr-x 15 root root 4096 Mar 30 08:14 /var/spool
drwx--2
Am Di, den 30.03.2004 schrieb Ken Morley um 20:05:
> I'm running Red Hat 8 patched to the latest rev, Sendmail 8.12.11 and
> MIMEDefang 2.41.
>
> I think that everything is installed correctly, but I have a problem that I
> can't seem to resolve:
>
> Upon each received e-mail, I see errors simila
On Tue, 30 Mar 2004, Lucas Albers wrote:
> Was this openlog/syslog multiplexor fix included in mimedefang 2.41?
No; it's in 2.42-BETA-1. If you want to stick with 2.41, just follow
Josh's fix:
> > Solution: Add a closelog() call to mimedefang-multiplexor.c's
> > activateSlave function, just be
Was this openlog/syslog multiplexor fix included in mimedefang 2.41?
> I think that I've found and fixed a problem in MIMEDefang's embedded
Perl mode.
>
> The problem: The MIMEDefang multiplexor uses the openlog and syslog
functions to write to the syslog. These functions use a file descriptor
Hi
In my mimedefang-filter, i have
if (filter_bad_filename($entity)) {
md_graphdefang_log('bad_filename', $fname, $type);
return action_bounce("$ext found in mail - rejected");
}
My problem is, the mail est rejecter and mimedefand send reject
notification with the attach
I'm running Red Hat 8 patched to the latest rev, Sendmail 8.12.11 and
MIMEDefang 2.41.
I think that everything is installed correctly, but I have a problem that I
can't seem to resolve:
Upon each received e-mail, I see errors similar to the following in maillog:
Mar 30 12:56:45 linux sendmail[11
Henrik,
> does mimedefang have any building ways for gathering
> statistics such as number of messages processed, messages
> discarded, rejected, etc?
See the contrib folder in the source, and http://www.bl.org/~jpk/graphdefang/ -
you can add logging entries into your filter which this will pic
Hello,
does mimedefang have any building ways for gathering statistics such as
number of messages processed, messages discarded, rejected, etc?
Sincerely,
- Henrik
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang maili
Hello,
I'm wondering if it would be a good idea to add a header for the primary MX
server for the domain in the From: header.
Adding this header might allow for some nice rules in SpamAssassin to be
developed.
I'm currently adding HELO, RCVD_IP and RCVD_HOST, and creating rules for
HELO with much
We started using "$MaxMIMEParts = 40;" after some trouble with a
user who had two accounts forwarding to each other. Once one side
filled its disk quota it started bouncing with the original as a
mime attachment, and after a while the mail system got bogged down.
It had a couple of hundred parts
Kaden Napper wrote:
Hi, I am currently trying to roll out Mimedefang + Vexira AV (milter
version) on a redhat 9 server.
Vexira runs fine by itself, but when I add the milter for mimedefang, I get:
An unknown error has occurred. Subject 'Test Message', Account:
'[EMAIL PROTECTED]', Server: '192.168
Dear all
Make sure that your Vexira pid and sock file exists /var/spool/MIMEDefang/
Try first stoping mimedefang
then start mimedefang and Vexira
so that socket is must be made btw mimedefang and Vexira
Regards
Muhammad Talha
> Hi, I am currently trying to roll out Mimedefang + Vexira AV
Make sure that you have enabled logging in clamav.conf
like that
LogSyslog
or
LogFile /var/log/clamd.log
Regards
Muhammad Talha
> I have justed installed Mimedefang 2.39 and Clamav on a RedHat 9 server.
> My problem is the server is not logging when a virus has been detected.
> Rig
Looking at the stuff you posted, and seeing that re-installing a basic filter
didn't help, my suspicion is that you also modified the memory limits in the
startup script and that you're hitting these almost immediately with the full
set of SA rules. With the cut-down version, you're OK - but if a
Bryce,
There's an error in your filter:
> if ($category eq "virus") {
> md_graphdefang('virus',$VirusName, $RelayAddr);
That should be:
md_graphdefang_log('virus',$VirusName, $RelayAddr);
Best Wishes,
Paul.
_
26 matches
Mail list logo
