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'} =
Tony,
Nothing to do with OP's question, but I'd value particularly your answer
to the following question to do with the above:
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
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 the bounce
message back (double bounce) from one's own MTA
Tony,
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.
# telnet localhost submission
Trying 127.0.0.1...
Connected to localhost (127.0.0.1).
David,
I wanted to stop any JPEG's in my incomings mails. So I put :
$banned_filename_re = new_RE(
qr'.\.(jpg|jpeg)$'ix, qr'^image/'i);
Just fine when amavis stop it.
I was happy so I decided to stop all mails with a MIME-type that is not
known : qr'^application/octet-stream$'i, I tried
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 the
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
Marcus,
I dont want to disable notification completely, just the unnecessary
messages that are generated when blocked_filename messages are dilivered to
a blocked_filename_lover.
Newer versions of amavisd-new have separate controls for virus and banned
admin notifications, you can just turn
Luis,
I am running into a problem running the latest version of Amavisd from the
FreeBSD ports. The server is a running FreeBSD 4.11 + amavisd-new 2.3.1 +
perl 5.8.7
Sorry for a late reply. I think you just missed the discussion on the list
about the Perl 5.8.7 problem.
mime_decode-1
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
meow,
I setup PostgreSQL to store Log and it worked fine, but I found their is no
information in client_addr FIELD of msgs TABLE.
...
And my /etc/postfix/master.cf config contains -o
smtp_send_xforward_command=yes.
I thought if I use -o smtp_send_xforward_command=yes then postfix
will
Gary, Mike,
I should rephrase that. The score that is reported in the header (and
the log) is not correct for messages that are quarantined. Amavisd-new
still does the right thing as far as where the message should go.
This may also explain what happened in this thread:
Below taglevel but
Thanks a lot for all your comments. I have solved the problem and i
have also learnt a lot.
Just to finish the thread and document for others this post, i would
like to include the mail platform in use by my side:
Exim 4.50 + amavisd-new-20030616-p10 + ClamAV 0.86.1-0volatile +
SpamAssassin 3.0
Quick question...
I'm running amavisd-new-2.3.0 (20050424)
I have my whitelist file setup in /var/amavis/whitelist_sender
In /etc/amavisd.conf I have the following line :
read_hash(/var/amavis/whitelist_sender),
When I receive an email from address of [EMAIL PROTECTED] - it seems to match
I am using postfix as my mta. It is accepting messages on both ports 25 and
4025. The reason we are doing this is that we have a barracuda device that
forwards mail to this box on port 25 after it has scanned the messages for
both spam and viruses. However, we have laptops in the field that have
No, we are opening UDP reply from any host to our mailhost. When we open
specific UDP port 6277 it doesn't work, but when we open all UDP ports
gt 1023 it works.
Thanks,
MJ
---
SF.Net email is sponsored by: Discover Easy Linux Migration
Hi,
Is there any statistics script for reporting SPAM and Virus statistics
which can work with log_level=0 of amavis. I have tried the one
available at http://flakshack.com/anti-spam/wiki/index.php it works fine
only if the log_level = to 2.
Thanks,
MJ
mess-mate [EMAIL PROTECTED] 07/26/05 3:51 PM
Hi,
i'm using amavis (litte modified) with maia.
Virus and Spam must be quarantined
snip
But spam messages are bounced to [EMAIL PROTECTED]
What did i wrong ??
Thanks in advance for your help
mess-mate
You need to
Thx, that was it
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gary V
Sent: Tuesday, July 26, 2005 10:09 AM
To: Lee Strawther
Cc: amavis-user@lists.sourceforge.net
Subject: Re: [AMaViS-user] can amavis only scan incoming 4025
Lee wrote:
I am using
Joel,
Both user2 and userB received the emails that were sent. The problem,
however, is that user2 also received the email sent by userA. This is a
huge security risk. After looking through the logs, I discovered the
following (see attached). Any help would be appreciated.
Here is the
MJ,
1- Max number of incoming smtp session my server will accept is 20,
right?
smtp-amavis unix - - n - 20 smtp
Wrong, unless you also set the regular smtpd at port 25 to maxproc 20,
which you shouldn't. It is usual that the number of content filters
(20 in your case) is
Stephen Carter [EMAIL PROTECTED] wrote:
| mess-mate [EMAIL PROTECTED] 07/26/05 3:51 PM
| Hi,
| i'm using amavis (litte modified) with maia.
| Virus and Spam must be quarantined
|
| snip
|
| But spam messages are bounced to [EMAIL PROTECTED]
|
| What did i wrong ??
| Thanks in advance for
P.S. to my previous posting:
The most likely reason is that exec in a forked process fails,
and the forked process continues its cloned life instead of terminating.
The explanation and the cause I did right, but I failed to explain
why user2 got userA's message. Here is the rest:
Than its not a stateful firewall, and yes, you would need to open udp
ports 1024 to 32767 (or get a stateful firewall)
MAYBE limit it to the mail server as destination, MAYBE set up a group
of addresses (the public DCC servers) that would limit it somewhat.
Opening INCOMING port 6277 doesn't do
-Original Message-
Subject: Re: [AMaViS-user] AWL score not being added correctly?
|
| So, I agree we have a bug / feature request here.
|
| Mark M. - Any chance of updating the scores output on non-passed
| messages such that they reflect the true value used in
determining the
-Original Message-
I have my whitelist file setup in /var/amavis/whitelist_sender
In /etc/amavisd.conf I have the following line :
read_hash(/var/amavis/whitelist_sender),
When I receive an email from address of [EMAIL PROTECTED] - it
seems to match the whitelist, yet
Joel,
I've upgraded to amavis-2.3.2 and the latest SpamAssassin from CPAN and
the issue is still happening but is much less frequent(2-3/day for ~1
Million emails from 70/day). I was using amavis-2.2.1 and SpamAssassin
3.0.1 or 3.0.2. I haven't been able to reproduce the error but I will
Scott,
I have my whitelist file setup in /var/amavis/whitelist_sender
In /etc/amavisd.conf I have the following line :
read_hash(/var/amavis/whitelist_sender),
To which variable (lookup table) are you reading the whitelist_sender file?
When I receive an email from address of [EMAIL
Hi all,
The amavis schema for LDAP requires the attribute 'mail'. All of our
users have virtual mailboxes (a bunch of domains) that eventually map to
their REAL email address, which is [EMAIL PROTECTED]
So for instance, a postfix virtual user table could be:
[EMAIL PROTECTED] [EMAIL
On Tue, Jul 26, 2005 at 04:53:56PM -0400, Matt Juszczak wrote:
Hi all,
The amavis schema for LDAP requires the attribute 'mail'. All of our
users have virtual mailboxes (a bunch of domains) that eventually map to
their REAL email address, which is [EMAIL PROTECTED]
So for instance, a
-Original Message-
From: Clifton Royston [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 26 July 2005 6:49 a.m.
To: Stuart Johnston
Cc: [EMAIL PROTECTED]; amavis-user@lists.sourceforge.net
Subject: Re: [AMaViS-user] FINAL DECISION: Will our machine handle it
I thought that rejecting
Hi all,
the /var/run/clamav/clamd.ctl is no more there :(
And couldn't find on what package it's attached to restore it.
Any hint ?
mess-mate
--
Good news. Ten weeks from Friday will be a pretty good day.
---
mess-mate wrote:
Hi all,
the /var/run/clamav/clamd.ctl is no more there :(
And couldn't find on what package it's attached to restore it.
Any hint ?
mess-mate
This will not exists when clamd is not running. Try:
/etc/init.d/clamav-daemon stop
/etc/init.d/clamav-daemon start
ls -l
Is it possible I amavisd-new to specify which users get notifications
when a mail message was blocked or banned? I'd rather not turn on admin
notifications and get a notice every single time there's a virus sent to
one of our users. We have some users who wish to receive blocked/banned
Matt wrote:
Hi all,
I'm developing a portal for our users to increase/decrease spam levels.
I'm wondering what good levels are for the users.
I'd like to start them at 6.31, and allow them to drag the bar down to
4, and up to 15.
Basically, the levels would be like this:
3.0 - RED
37 matches
Mail list logo
