On 11/4/2013 9:47 PM, inteq wrote:
> Decided to tar my log and send it.
> Tested with the yesterday log containing malware links and it works.(so far)
>
> Thank you for your input
>
> My approach:
>
> #!/bin/bash
> # Use apt-get install sendemail (this is NOT sendmail) if you do not have it
> /u
Decided to tar my log and send it.
Tested with the yesterday log containing malware links and it works.(so far)
Thank you for your input
My approach:
#!/bin/bash
# Use apt-get install sendemail (this is NOT sendmail) if you do not have it
/usr/sbin/pflogsumm -d today --problems_first --smtpd-sta
inteq skrev den 2013-11-05 02:26:
Another workaround I was thinking is to compress the log file before
sending.
should then be something clamav cant unpack :)
eg lzip
Manuel Bieling skrev den 2013-11-05 01:21:
Sorry, I'm not as familiar with clam*. But why do you assume the mails
coming from a localhost sender?
i dont trust, its 127.0.0.1 networking with is always me, why should i
block myself ?
i did not write root@localhost as sender
Thank you for your replies.
The message is from localhost, not from another postfix machine, but the
machine has multiple virtual servers/aliases.
The reason behind a log file containing no malware but still being flagged
as virus, is because the scanner is configured to check links also (links
t
On 2013.11.05 00:29:41 +0100, Benny Pedersen wrote:
> Manuel Bieling skrev den 2013-11-05 00:22:
>
> >What the others said. That shouldn't happen. It's a problem with
> >clamav.
>
> incorrect, clamsmpt is at fault here, mails should not block on
> localhost, its fault is that clamsmtp is only for
Manuel Bieling skrev den 2013-11-05 00:22:
What the others said. That shouldn't happen. It's a problem with
clamav.
incorrect, clamsmpt is at fault here, mails should not block on
localhost, its fault is that clamsmtp is only for proxy scaning with
postfix, not usable as a global content fil
inteq skrev den 2013-11-04 20:42:
Any hints how to whitelist emails sent from r...@ns4.example.com, or
bypass
somehow the virus checks for some addresses?
life would be more simple if you change from clamsmtp to clamav-milter,
after that you can disable virus scanning on localhost senders, j
On 2013.11.04 11:42:51 -0800, inteq wrote:
> Nov 4 21:36:52 ns4 postfix/smtp[9383]: 338E14303B: to=,
> relay=127.0.0.1[127.0.0.1]:10025, delay=0.14, delays=0.06/0/0.05/0.03,
> dsn=2.0.0, status=sent (250 Virus Detected; Discarded Email)
> Nov 4 21:36:52 ns4 clamsmtpd: 100013: from=r...@ns4.exampl
On 11/4/2013 3:54 PM, Noel Jones wrote:
> On 11/4/2013 1:42 PM, inteq wrote:
>> Hello
>>
>> For some time now I was wondering why some of my pflogsumm emails were not
>> received.
>> Digging deeper into the problem today, I can see the emails are being
>> blocked by Postfix because it "contains"
On 11/4/2013 1:42 PM, inteq wrote:
> Hello
>
> For some time now I was wondering why some of my pflogsumm emails were not
> received.
> Digging deeper into the problem today, I can see the emails are being
> blocked by Postfix because it "contains" a virus.
>
> Nov 4 21:36:52 ns4 postfix/smtp[93
On 04 Nov 2013, at 12:42 , inteq wrote:
> Nov 4 21:36:52 ns4 clamsmtpd: 100013: from=r...@ns4.example.com,
> to=t...@example.com, status=VIRUS:Sanesecurity.Jurlbl.3425.UNOFFICIAL
Nothing to do with postfix, clamsmtpd is blocking your email.
--
I thought that they were angels, but to my surpr
12 matches
Mail list logo