On 7/23/07, Daniel J McDonald <[EMAIL PROTECTED]> wrote:
>
> clamd stopped. Restart the clamd service and you should be fine.
>
Thanks Guys! I restarted clamav-daemon, the log looks fine now, I'll
check it a while.
Thanks
-
I have made no changes at all, and today amavis stopped to work, so my
mail server (Postfix) is not delivering email, this is the log file:
ul 23 10:50:03 pc009 amavis[11600]: (11600-01) ClamAV-clamscan
av-scanner FAILED: /usr/bin/clamscan unexpected exit 50,
output="LibClamAV Error: Can't load /v
On 7/17/07, Gary V <[EMAIL PROTECTED]> wrote:
> Yes, I think you can. Are you using mbox or maildir mail storage?
>
> If necessary you should be able to edit the file and do a copy and
> paste of a needed message. I personally would use WinSCP for a task
> like that. Copy the message to the clipboa
On 7/16/07, Gary V <[EMAIL PROTECTED]> wrote:
>
> This was a bug in some early versions of amavisd-new on Debian.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=350917
>
> I suggest changing:
> $QUARANTINEDIR = "$MYHOME/quarantine";
> to
> $QUARANTINEDIR = "$MYHOME/virusmails";
>
> (this may
Hi all ;)
I have been using postfix-amavis one year and I am pretty happy with them.
I have this setup on a 50-user file:
$virus_quarantine_to = "[EMAIL PROTECTED]";
(I download every week the messages contained in that email address
with no problem.)
Today an email was quarantined because it
fix/smtpd[29043]: DF2BE324825:
client=unknown[192.168.1.117], sasl_method=CRAM-MD5,
sasl_username=andres
So, it is being authenticated by SASL. What could possible be
happening? I fully understand you and your solution. (Do you need more
detailed log?)
> If this IS from a SASL AUTH user, I would sa
On 12/14/06, Gary V <[EMAIL PROTECTED]> wrote:
> I would get rid of this:
>
> smtpd_client_restrictions =
> reject_rbl_client sbl.spamhaus.org,
> reject_rbl_client relays.ordb.org,
> reject_rbl_client blackholes.easynet.nl
>
> and move these to after reject_unauth_destination
>
> smtpd_recipient
eceive 4hs later an advice from postfix.
I will be monitoring this and tell you if something different happens.
Thanks for all your help!!
Andres
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net'
On 12/14/06, Mark Martinec <[EMAIL PROTECTED]> wrote:
> Here is the patch that should apply cleanly to 2.3.3:
>
> Mark
Mark, this is the output of the error with the patch applied:
Dec 14 14:12:27 pc009 postfix/smtp[5276]: 5E08039A34D:
to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1], delay=22
On 12/14/06, Mark Martinec <[EMAIL PROTECTED]> wrote:
> My choice of OS is FreeBSD :-)
>
>
Hey That's my choice too :) ! I have a 4.10 server with jboss running
since 2 years with no problem, I do not know why I tried ubuntu, maybe
I can switch in the future...
I found perl-net 0.94 and I will t
On 12/14/06, Mark Martinec <[EMAIL PROTECTED]> wrote:
> Which version is that? 2.3.3? That's more than a year old.
> Are you sure you want to bother with it?
>
> Make sure you have Net::Server version compatible with
> your version of amavisd-new. The latest Net::Server still
> compatible with amav
On 12/14/06, Andres <[EMAIL PROTECTED]> wrote:
> Thanks Mark for your answer, my amavisd file has 14938 lines, it does
> not reach 16290...
> (amavisd-new from ubuntu packages)
> I do have this line
> defined $ln || $!==0 || $!==EAGAIN
>
> But at other location... Can
nswer, my amavisd file has 14938 lines, it does
not reach 16290...
(amavisd-new from ubuntu packages)
I do have this line
defined $ln || $!==0 || $!==EAGAIN
But at other location... Can I apply your patch manually ?
Thanks
Andres
On 12/14/06, Leon Kolchinsky <[EMAIL PROTECTED]> wrote:
> >
> > Sorry, but, what 'file' ? amavisd-new ?
> > It started to work bad from time to time, no changes were made...
> >
>
> "file" is just a utility.
> # man file
>
> FILE(1) FILE(1)
> NAME
>
On 12/14/06, Michael Scheidell <[EMAIL PROTECTED]> wrote:
> Try a newer version of 'file' and make sure its first in the path?
>
Sorry, but, what 'file' ? amavisd-new ?
It started to work bad from time to time, no changes were made...
--
On 12/13/06, Gary V <[EMAIL PROTECTED]> wrote:
>
> If you do have whitespace where the directive continues on to the next
> line, maybe you need to show 'postconf -n'. Are you sure the client in
> question was authenticated?
>
> Gary V
Gary, I do have pcre support, I installed postfix-pcre package
On 11/29/06, Gary V <[EMAIL PROTECTED]> wrote:
> If it continues to happen, either run amavisd-new in debug mode until
> it crashes (if it does), then show the last half dozen or so entries
> or *temporarily* set $log_level to 5 and look for error messages from
> amavisd-new in your log. It's not i
On 12/13/06, Gary V <[EMAIL PROTECTED]> wrote:
> >> etc/postfix/main.cf:
> >> smtpd_data_restrictions =
> >> reject_unauth_pipelining
> >> permit_sasl_authenticated
> >> check_client_access pcre:/etc/postfix/add_auth_header.pcre
> >>
> >> /etc/postfix/add_auth_header.pcre
> >> /^/ PREPE
On 11/30/06, Gary V <[EMAIL PROTECTED]> wrote:
> Here is another idea on a way possible to do this (if you don't have
> Postfix 2.3.x). This should add and 'X-SMTP-Auth: no' header to all
> messages except authenticated. The spamassassin rule then adds -15
> points if this header is missing. Requir
On 12/2/06, Leon Kolchinsky <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I think that Anders has a point here.
> whitelist_from_rcvd should add -100 points to any scanned e-mail, so
> theoretically it should pass at any condition.
>
> Why is this not happening is a mystery to me.
> He isn't blaming SA p
On 11/29/06, Gary V <[EMAIL PROTECTED]> wrote:
> > The user could send emails before with no problem...
> > Thanks!
>
> This may give you some ideas:
> http://www200.pair.com/mecham/spam/bypassing.html#10
>
> Gary V
Hey Gary, what is the objetive of setting whitelist and
trusted_networks if them w
On 11/29/06, Clifton Royston <[EMAIL PROTECTED]> wrote:
> If these scores are correct, and you did indeed receive it from an
> employee machine on your network, your employee has a really-truly
> badly compromised machine on your network which is being actively used
> to send spam.
> -- Clifton
Hi !
I know that this is more a spamassassin-related question but I found
here smart guys who also work with it, and maybe experienced this,
I added this to local.cf at /etc/spamassassin
whitelist_from_rcvd [EMAIL PROTECTED] domain.com
(domain.com is my domain)
and:
trusted_networks 127.0.0.
On 11/29/06, Gary V <[EMAIL PROTECTED]> wrote:
> Then you ARE using 0.90 (provided you have not installed Net::Server
> from source or CPAN). If you are using 0.90, then this is probably
> not related to Net::Server.
>
> What version does amavisd-new say it's using when you start it up in
> debug m
> > I read that this is some problem with Net::Server library how can I
> > revert back to 0.90? I use packages based software...
>
> Instead of downgrading, you could try patching amavisd-new:
> http://marc.theaimsgroup.com/?l=amavis-user&m=114350834132044
>
> Gary V
>
Hi, thanks for your answer,
Hi
My setup is this:
I am using amavis - mysql - postfix and spamassassin.
- version of amavis 1:2.3.3-3
- version of MTA 2.2.10-1ubuntu0.1
Mails are being deferred with this error log:
Nov 29 14:38:29 pc009 postfix/smtp[29347]: 1500B3245D1:
to=<[EMAIL PROTECTED]>, relay=127.0.0.1[127.0.0.1],
Off Site?
:)
Well, I have this on my 50-user file config
$warn_offsite = 1;
Is this a good practice ? Or should I shut this down to lower the load
on the MTA? (the load of sending warn emails to outside)
Thanks
-
Take Surv
On 11/10/06, Jakob Curdes <[EMAIL PROTECTED]> wrote:
> ... and it is a 100 % postfix and 0 % amavis question. Postfix alone is
> responsible for verification of valid recpients. I am sure we have the
> people who can answer this on this list but I would really encourage
> everybody to post questi
Hi :)
I am using pretty much this setup: http://flurdy.com/docs/postfix/
(Postfix - Amavis - SpamAssassin) and I noticed this behavior:
If i receive spam messages to unknown users at my site, for example:
[EMAIL PROTECTED] <- Mail is sent to quarantine
if I send a regular email to [EMAIL PROTEC
29 matches
Mail list logo