Hi Gary,
Now then I've read your reply and gave it another thought, I think you're
right. This is not the right tool for whitelisting internal server users.
I'll try one of your bypassing examples on
http://www200.pair.com/mecham/spam/bypassing.html
Best Regards,
Leon Kolchinsky
-Origin
Vincent wrote:
> Here is the output of
> # amavisd debug
> Dec 2 19:09:42 fyma.fyma.ucl.ac.be /usr/local/sbin/amavisd[32314]:
> starting. /usr/local/sbin/amavisd at fyma.fyma.ucl.ac.be
> amavisd-new-2.3.3 (20050822), Unicode aware, LANG=en_US.UTF-8
> Dec 2 19:09:42 fyma.fyma.ucl.ac.be /usr/loc
I moved /var/lib/amavis/tmp to /var/lib/amavis/tmp2 (because the
number of files was to huge)
I downgraded to Net::Server-0.90 restarted amavis, now all is ok :)
On 12/2/06, Vincent Boucher <[EMAIL PROTECTED]> wrote:
> Here is the output of
>
> # amavisd debug
> Dec 2 19:09:42 fyma.fyma.ucl.ac.be
Leon wrote:
> Hi,
> I've used this syntax to avoid spam/header/banned_files checks for selected
> e-mail adrr.:
> @spam_lovers_maps
> = @bypass_spam_checks_maps
> = @banned_files_lovers_maps
> = @bypass_banned_checks_maps
> = @bad_header_lovers_maps
> = @by
Leon wrote:
> So, if I got you right
> If I want to whitelist_from_rcvd to work for users of my own server I should
> delist it from trusted_networks and internal_networks (i.e. 127/8 should
> never be included)?
> This way the first untrusted server would be my own, right?
> # Internal
> clear_i
I've been using amavisd-new with postfix for several years with no
problems until this new installation I just setup. There are now two
problems, that are probably inter-related.
Problem 1: after an 'amavisd reload' or 'amavisd stop' command, not
all child processes die. The main server thread exi
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of MrC
> Sent: Saturday, December 02, 2006 12:58 PM
> To: amavis-user@lists.sourceforge.net
> Subject: Re: [AMaViS-user] spam reports get spam
> treatment,how to workaround ?
>
>
> Btw. You might want
> From: Michael Scheidell
> >
> > Btw. You might want to obfuscate your email if you post it
> on the web
> > - crawlers routinely collect obvious email addresses and
> add them to
> > spam address books.
>
> We have amavisd-new, we want spammers to TRY. It helps feed
> DCC, Razor and spamc
Here is the output of
# amavisd debug
Dec 2 19:09:42 fyma.fyma.ucl.ac.be /usr/local/sbin/amavisd[32314]:
starting. /usr/local/sbin/amavisd at fyma.fyma.ucl.ac.be
amavisd-new-2.3.3 (20050822), Unicode aware, LANG=en_US.UTF-8
Dec 2 19:09:42 fyma.fyma.ucl.ac.be /usr/local/sbin/amavisd[32314]:
user
> btw, in a couple of logs, I cam across some stuff like below,
> any thoughts where that came from???:
>
> ===
> Nov 25 22:09:20 koala postfix/pickup[11442]: F0A04238960:
> uid=103 from=<[EMAIL PROTECTED]> orig_id=9639A238966 Nov
> 25 22:09:21 koala postfix/pickup[11442]: 8D3F8238966: uid=
>
> MrC,
> if you feel your scripts are idiot-proof, pls send to
> [EMAIL PROTECTED] many thanks in advance
>
> as the reports are generated/emailed from the report
> generator (Postconf'
> spamreport) not sure if this writer is sufficiently capable
> of hacking spamrep script, though, the scr
So, if I got you right
If I want to whitelist_from_rcvd to work for users of my own server I should
delist it from trusted_networks and internal_networks (i.e. 127/8 should
never be included)?
This way the first untrusted server would be my own, right?
# Internal
clear_internal_networks
internal_n
Hello,
Yesterday I restarted spamassassin and amavisd
(/etc/init.d/spamassassin restart and amavisd reload) after a change
in the /etc/mail/spamassassin/local. cf file (I add a host in the
whitelist).
Since this restart the server do not deliver incomming and outgoing
mails, /var/log/maillog:
..
Gary wrote:
> In this particular header, the sender and the rDNS of the relay host
> must (at least partially) match the the sender and host in
> whitelist_from_rcvd.
Actually I think the sender would be retrieved from a different
header. The thing is, whitelist_from_rcvd might be useful in a
sit
Leon 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.
No, if I am not mistaken there is one specific received header that is
looked at to determine whether there is a ma
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
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 people but functionality that is not working.
Correct me if I wrong.
Hi,
I've used this syntax to avoid spam/header/banned_files checks for selected
e-mail adrr.:
@spam_lovers_maps
= @bypass_spam_checks_maps
= @banned_files_lovers_maps
= @bypass_banned_checks_maps
= @bad_header_lovers_maps
= @bypass_header_checks_maps = (
rea
On Sat, December 2, 2006 5:11 am, MrC wrote:
> Gary's solutions have been good ones.
> additional setup of postfix/amavis. If you're interested, I'll send you
> the mime-encoding script and source to mini_sendmail.
MrC,
if you feel your scripts are idiot-proof, pls send to [EMAIL PROTECTED]
m
On Sat, December 2, 2006 2:40 am, Gary V wrote:
> Voytek wrote:
> your webmail program uses smtp also but your logs should tell you. You can
> probably grep your mail log for 'pickup' to get an idea what senders use
> it. You could simply send something from webmail and watch the log to see
> if
Jo,
> So, I'm confused. The release notes say:
> - AM.PDP/milter setup: new configuration setting
> $prepend_header_fields_hdridx,
>also a member of policy banks, with a default value of 0.
> But amavisd.conf-default has this line:
> # $prepend_header_fields_hdridx = 1;
> Am I misunderstandin
Mark Martinec wrote:
> If not quarantining to PostgreSQL, the 2.4.4 is fully compatible
> with 2.4.3, no changes in amavisd.conf file are necessary,
> just replacing a file amavisd with a new version and restarting
> the daemon would suffice.
So, I'm confused. The release notes say:
- AM.PDP/mil
22 matches
Mail list logo
