lau den 05.11.2005 Klokka 08:22 (-0700) skreiv Gary V:
[ qr'.\.(doc|ppt|xls|pdf)$'i = 0 ], # allow these before we ban any
# more stuff (notably archives)
qr'.\.(zip|rar)$'i, # more banned file
ty den 11.10.2005 Klokka 14:41 (-0400) skreiv Pierre Girard:
I run 2 rigs, Postfix 2.1.5 (1150 users) and 2.2.5 (test/semi-
production, 4 users). Both run amavisd-new for virus scanning (Sophos
SAV) and neither run SpamAssassin. Both run dspam 3.6 (beta/CVS) as
daemon and both (MySQL 4.0.20
Jochen Seifarth wrote:
I do use SquirrelMail, but still AFAIK it's only a web interface to email,
i.e. it displays on a Web UI what's in my mail folders (via IMAP). No idea
if/how you could get SquirrelMail to move your mail items to different
folders. Isn't that an LDA (e.g. procmail) job ?
tir, 06.09.2005 kl. 12.07 skrev Mark Martinec:
Hmmm ... I do that with Postfix header_ and mime_header_check PCRE
content filters in cleanup, after all the amavisd-new filtering.
amavisd-new discards only 8-bit non-mime shit (and does it very well,
Postfix doesn't).
Postfix
tir, 06.09.2005 kl. 14.50 skrev Gregory Mokhin:
I've got a mail server where mostly spam in Russian is coming. It
never gets through SpamAssassin. There is nothing special in
SpamAssassin rules to block it - it just works. Make sure if
everything is fine with your installation and bayes
man, 05.09.2005 kl. 18.03 skrev Gary V:
[...]
Matt found that proper indexing helped LDAP queries:
http://marc.theaimsgroup.com/?l=amavis-userm=112377681617056w=2
Indexing (or not) of OpenLDAP attributes will *not* help the number of
connections to the slapd server. It *will* help the speed
fre, 02.09.2005 kl. 22.34 skrev Brian Stamper:
I recently started getting reports that there is a bunch of spam of the
Stock and finance degree getting through my spam server. Anyone else seeing
this if so any pointers on how to stop it.
Thanks,
Postfix 2.1/2.2 and dspam 3.5/3.6.
Well, you
ons, 31.08.2005 kl. 15.59 skrev Mark Martinec:
I have seen a couple of spams bypass our spamassassin scan because they
are larger than the 200KB default $sa_mail_body_size_limit. I'm thinking
about raising that limit to 512KB. If anyone have raised it, what size
have you configured it to?
ons, 31.08.2005 kl. 15.39 skrev Adrian Mak:
my scenario is when amavisd found a virus from received email, it
should bounce the email and a email should return to sender saying
that your email cannot be deliveried due to a virus.
This is my amavisd configuration
$mailfrom_notify_admin
tir, 30.08.2005 kl. 15.53 skrev Stuart Johnston:
Sigh ... what amavisd-new, what Postfix, what OS/distro, what
configurations?
amavisd-new-2.1.2 (slightly customized), postfix-2.0.16, RHEL3.
Standard postfix/amavisd-new configuration, I suppose. After-queue
filtering, spamassassin
man, 29.08.2005 kl. 18.22 skrev Stuart Johnston:
Occasionally amavisd-new crashes or locks-up and postfix sends messages
to the deferred queue with connect to 127.0.0.1[127.0.0.1]: Connection
refused.
What is the best way to get postfix to try connecting to amavis again
after amavis has
tir, 23.08.2005 kl. 00.45 skrev email builder:
[...]
Everyone seems to use LMTP to connect to amavis, but is there a good reason
for this?
Hmmm ... thanks for detailing all your software versions (not).
I use smtp from Postfix 2.2.5 to amavisd-new 2.3.2 and from amavisd-new
2.3.2 back to
søn, 21.08.2005 kl. 14.11 skrev Dale Walsh:
There doesn't seem to be any US mirrors for amavisd-new I see.
480 million people (or thereabouts) are happy living in Europe, why not
emigrate?
I have (Netherlands) no problems ever with www.ijs.si, what are yours?
--Tonni
--
To Liza Picquard
lør, 20.08.2005 kl. 16.06 skrev [EMAIL PROTECTED]:
Zitat von Michael Scheidell [EMAIL PROTECTED]:
According to the auto-ignore I just got from msn.com, it looks like they
will be ignoring complaints about spaces msn com spam because it doesn't
originate from an msn.com email address:
søn, 31.07.2005 kl. 02.15 skrev GM:
[...]
s av-scanner FAILED:
/usr/local/bin/f-prot DIED on signal 11 (008b) at (eval 54) line 423.
Can someone perhaps point me into the right direction to get this
issue resolved ?
The fprot scanner software failed because of a serious OS or
lør, 30.07.2005 kl. 13.40 skrev GM:
I have a freeBSD server running with amavisd-new ,, f-prot ,, spamassassin
installed from the ports collection.
Everything installed fine, except that when a message is scanned, it seems
like there is a problem with the Anti-Virus Scanning :-
Jul 30
tor, 28.07.2005 kl. 20.24 skrev Matthew D. Sill:
This is sort of off topic, however, I thought that since people are on
this list to fight spam, that others could benefit. I am running dual
sendmail + amavis on two machines, and my job, like yours I assume, is
to keep spam out of our
ons, 27.07.2005 kl. 13.48 skrev Brian Schonecker:
amavisd-new-20030616p9-3.6
I've got a few emails that had a EXE contained in a zip that were quarantined
on my email server. I do need these attachements but am unable to figure out
how to get them back into a 'usable' format.
I've
tir, 26.07.2005 kl. 05.29 skrev Gary V:
[...]
You have misunderstood what $sa_dsn_cutoff_level = 12.0; does.
If you were to use $final_spam_destiny = D_BOUNCE; amavisd-new would
send a bounce notice to the sender once the spam score reached your
$sa_kill_level_deflt (8.0).
Nothing to do
List,
Postfix 2.2.5
amavisd-new 2.3.2
Both work nearly perfectly together. However, I have a scenario (on a
test rig) where I want to simulate Internet mail from a Postfix smtpd
listener through amavisd-new to a postfix listener.
I have a policy_bank setting for amavis:
$policy_bank{'MYNETS'} =
tir, 26.07.2005 kl. 10.33 skrev Stephen Carter:
Tony Earnshaw [EMAIL PROTECTED] 07/26/05 6:32 AM
What is your (and possibly others') experience with sending bounce
notices to spammers? In my experience, not far from all spammer
addresses are forged, meaning either that one would get
tir, 26.07.2005 kl. 10.27 skrev Mark Martinec:
[...]
IOW, my advice at the moment would be: Don't bounce spam.
My current choice is to bounce a small range of spammy messages
just above the kill threshold, just in case they are false positives:
$sa_kill_level_deflt = 6.71;
tir, 26.07.2005 kl. 10.36 skrev Mark Martinec:
[...]
The message should be sent to port 10026, but is in fact sent to port
10025, as per the ALT policy_bank setting, since the message is coming
from localhost. IOW, XFORWARD and XCLIENT do not work as I interpret
they should, or am I
tir, 26.07.2005 kl. 11.36 skrev Tony Earnshaw:
You need to use XCLIENT instead of XFORWARD in your connection
to Postfix, to simulate a smtp client IP address.
Exactly the same happens when I use XCLIENT ... amavid-new still sends
mail to 10026 istead of 10025.
This is not correct
fre, 22.07.2005 kl. 02.22 skrev Gary V:
[...]
Nice work, looks like you have something in common with SuSE 9.1:
From http://www.ijs.si/software/amavisd/#faq-trouble :
Michael W Cocke writes: the reason DB_PRIVATE was enabled is that
SuSE 9.1 ships with BDB built wrong! Download BDB 4.2.52
lør, 23.07.2005 kl. 02.39 skrev Javier Carlos Viegas:
Hi, im havving this error, when i receive any
email,
im testing
amavisd-new to see if i can use it for spam
filtering
with SA.
This is on my logs:
Jul 22 21:05:27 vida amavis[4619]: DENIED ACCESS
from
IP
26 matches
Mail list logo
