Jay Lee wanted us to know:
>Tinus Nijmeijers said:
>> any traffic coming into the internal interface on port 25 where
>> src!=mailserver gets redirected to the mailserver.
>> Your external interface does come into the picture.
>Yes, and in order for my mail server to accept the mail from
>[EMAIL P
Examine the following article?
http://www.macftphttp.serverbox.org/wiki/index.php?
title=Install_both_macosx
On Jan 04, 2005, at 03:51, Mr Mailing List wrote:
Hello,
On 22 Dec 2004, at 20:18, Cameron Bales wrote:
Hello.
I'm getting this string of errors during the ./configure stage of
installing
Tinus Nijmeijers said:
> any traffic coming into the internal interface on port 25 where
> src!=mailserver gets redirected to the mailserver.
> Your external interface does come into the picture.
Yes, and in order for my mail server to accept the mail from
[EMAIL PROTECTED] going out to [EMAIL PRO
On Tue, 2005-01-04 at 22:53, Jay Lee wrote:
> Tinus Nijmeijers said:
> > why not let the firewall redirect everything on port 25 && ! from the
> > mailserver to the mailserver?
>
> Because then my mail server would need to be an open relay and that is bad...
>
> Jay
no it would not.
any traffic
Tinus Nijmeijers said:
> why not let the firewall redirect everything on port 25 && ! from the
> mailserver to the mailserver?
Because then my mail server would need to be an open relay and that is bad...
Jay
--
Jay Lee
Network / Systems Administrator
Information Technology Dept.
Philadelphia Bi
On Tue, 2005-01-04 at 20:26, Jay Lee wrote:
> Right now, our organization's firewall blocks all outgoing
> connections to port 25 except directly from the mail server. Our
> mail server supports authenticated relaying and SMTP-SSL on port 465
> so this is not a problem in 99.9% of the cases.
Jay Lee wrote:
> What I'd like to do is configure a transparent SMTP proxy on port
> 25 of the firewall that send the outgoing message through ClamAV,
> allowing only clean messages to pass. User's wouldn't notice
> anything when they send out messages via port 25 but viruses would
> not get out
Right now, our organization's firewall blocks all outgoing
connections to port 25 except directly from the mail server. Our
mail server supports authenticated relaying and SMTP-SSL on port 465
so this is not a problem in 99.9% of the cases. The majority of port
25 outgoing traffic not coming
Lars Monsees wrote:
I thought that clamdscan isn't able to scan a scream as this isn't
stated in the man-pages.
Older versions had problems with clamdscan in stream mode, but it has
worked since version 0.70.
--
James Lick -- éåæ -- [EMAIL PROTECTED] -- http://jameslick.com/
___
Title: RE: [Clamav-users] Grepping of clamscan output (or use of returncodes)
> Try this:
> clamdscan wurm-mail.txt 2>&1 | fgrep FOUND
>
> Notes:
> 1) You were only looking at the output of stdout
that´s it =)
> 2) The cat command adds nothing so why use it
I just used this for
Lars Monsees wrote:
CMD => '/usr/local/bin/clamscan - | grep "FOUND"',
So, as you can see, grep isnÂt involved.
You probably want to add the --stdout flag to clamscan. clamscan writes
to stderr by default, so grep never sees the output. You'd also
probably be better off starting clamd a
On Tuesday 04 Jan 2005 09:15, Lars Monsees wrote:
>
> [EMAIL PROTECTED] root]# cat wurm-mail.txt | clamscan - | grep "FOUND"
Try this:
clamdscan wurm-mail.txt 2>&1 | fgrep FOUND
Notes:
1) You were only looking at the output of stdout
2) The cat command adds nothing so why use it
3) Consider us
Title: Grepping of clamscan output (or use of returncodes)
Hello,
I want to use ClamAV with OTRS an "Open source Ticket Request System" to filter wormmails.
OTRS uses a perl script to fetch mails via POP3. The mails can then be checked e.g. by executing a command:
$Self->{'PostMaster
Hello,
On 22 Dec 2004, at 20:18, Cameron Bales wrote:
Hello.
I'm getting this string of errors during the ./configure stage of
installing Clam AV 0.8 and the current CVS version as well. I'm
installing on OS X Server 10.3.6 gcc 3.3
--
checking resolv.h usability... no
checking reso
14 matches
Mail list logo