zahn skrev den 2018-10-08 12:49:
amavis[14826]: (14826-10) SA info: dns: new_dns_packet: domain is utf8
flagged: ns2.yandex.net
Is this an error message or can I ignore it - thanks for the reply.
SA info, in case of error imho it would say SA error
its harmless info
You can ignore I believe. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7632
On Mon, Oct 8, 2018, 06:49 zahn wrote:
> Hello
>
> I migrated spamassassin from 3.4.1 to 3.4.2 and now I get the following
> message
> in the logfile.
>
> amavis[14826]: (14826-10) SA info: dns: new_dns_packet
Will probably have to wait some time to ensure all is now together.
On 11/20/2014 08:46 AM, Robert Moskowitz wrote:
On 11/20/2014 07:45 AM, Robert Moskowitz wrote:
Looks like I left out all the mysql stuff from amavis.conf that I had
in my old server. Sigh. I now have to reconcile the differ
On 11/20/2014 07:39 AM, Mark Martinec wrote:
Robert Moskowitz wrote:
I am running a new mailserver virtual domain environment with postfix
and mysql for the virtual domain definitions. amavis-new seems to be
rejecting all emails for my one domain not a sub domain of my main
one. That is, my
On 11/20/2014 07:45 AM, Robert Moskowitz wrote:
Looks like I left out all the mysql stuff from amavis.conf that I had
in my old server. Sigh. I now have to reconcile the differences and
figure this out.
I am now seeing in the maillog:
Nov 20 08:36:20 z9m9z postfix/error[2698]: C379D620F2:
Looks like I left out all the mysql stuff from amavis.conf that I had in
my old server. Sigh. I now have to reconcile the differences and
figure this out.
On 11/20/2014 06:21 AM, Robert Moskowitz wrote:
Don't know where better to ask this...
I am running a new mailserver virtual domain envi
Robert Moskowitz wrote:
I am running a new mailserver virtual domain environment with postfix
and mysql for the virtual domain definitions. amavis-new seems to be
rejecting all emails for my one domain not a sub domain of my main
one. That is, my domain (as you can see from my email addr) is
h
On Mon, 18 Jul 2011 15:40:51 -0500, Max Dunlap wrote:
Hey guys, I followed https://help.ubuntu.com/community/PostfixAmavisNew
to get Spamassasin working with some virus checking. I'm getting
"X-Virus-Scanned: Debian amavisd-new" in my headers but no
"X-Spam-Status: No"
Any ideas?
Benny Pedersen
On Mon, 18 Jul 2011 15:40:51 -0500, Max Dunlap wrote:
Hey guys, I followed
https://help.ubuntu.com/community/PostfixAmavisNew
to get Spamassasin working with some virus checking. I'm getting
"X-Virus-Scanned: Debian amavisd-new" in my headers but no
"X-Spam-Status: No"
Any ideas?
see Troublesh
* Max Dunlap :
> Hey guys, I followed https://help.ubuntu.com/community/PostfixAmavisNew
> to get Spamassasin working with some virus checking. I'm getting
> "X-Virus-Scanned: Debian amavisd-new" in my headers but no
> "X-Spam-Status: No"
> Any ideas?
1. wrong list ;)
2. setup destination (mynetwo
On 7/18/11 4:40 PM, Max Dunlap wrote:
Hey guys, I followed https://help.ubuntu.com/community/PostfixAmavisNew
to get Spamassasin working with some virus checking. I'm getting
"X-Virus-Scanned: Debian amavisd-new" in my headers but no
"X-Spam-Status: No"
Any ideas?
amavisd users group will help
Michael:
Yes, I've been using SpamCop with Amavisd-new and SpamAssassin.
I wrote a simple shell script to report spam to Spamcop for me. I remove
the markups from Spam Assassin before reporting the email to Spamcop.
This is the part of my script that does the work:
...
spamassassin --remove-mar
> Michael:
>
> Yes, I've been using SpamCop with Amavisd-new and SpamAssassin.
>
> I wrote a simple shell script to report spam to Spamcop for me. I remove
> the markups from Spam Assassin before reporting the email to Spamcop.
> This is the part of my script that does the work:
Reporting works
> -Original Message-
> From: Michael Scheidell [mailto:scheid...@secnap.net]
> Sent: Sunday, January 25, 2009 11:51 PM
>
> A long time ago, and in a galaxy far away, I used to use spamcop.
> Since moving to SpamAssassin, (which I thought spamcop, sorta thinks
> they support, sorta, maybe,
Rocketmail isn't new. I've had a rocketmail account since the 1990's.
--Quanah
--On Thursday, June 19, 2008 6:40 PM -0400 Michael Scheidell
<[EMAIL PROTECTED]> wrote:
As if email from freebie @yahoo.com addresses isn't enough, Yahoo has
now announces two new domains that the freebie spammer
Quanah Gibson-Mount wrote:
Rocketmail isn't new. I've had a rocketmail account since the 1990's.
yes, and now you belong to yahoo
read the story.
--
Michael Scheidell, President
Main: 561-999-5000, Office: 561-939-7259
> *| *SECNAP Network Security Corporation
Winner 2008 Technosium hot co
>
> If whoever's responsible for the proxy is not able to
> implement normal recipient validation, I think this makes a
> good case that they aren't able to keep it running adequately.
Its worse, we have to feed it to 'yap' (yet another proxy) and THAT
proxy also does no recipient validation,
On Sun, Sep 23, 2007 at 08:31:04PM -0400, Michael Scheidell wrote:
> One thing I would like to see (and this is a different subject:
> Marc: take note: Id like to NOT BOUNCE an email back to the victim of
> backscatter if they bothered to publish SPF or SENDER ID records that
> don't match the inc
Marc, you shouldn't be bouncing e-mails back at all. Use D_REJECT
and make sure you're doing it at the SMTP layer. SPF or DKIM is
irrelevant in this situation.
On Sep 23, 2007, at 5:31 PM, Michael Scheidell wrote:
One thing I would like to see (and this is a different subject:
Marc: take n
On Sep 23, 2007, at 5:17 PM, Michael Scheidell wrote:
Anyone have an answer that isn't obvious?
I already said I can't put it on the proxy.
No, you didn't. You mentioned that as an option.
And stop being rude to people who answer the question you asked.
--
Jo Rhett
Net Consonance : consona
Michael Scheidell wrote:
One thing I would like to see (and this is a different subject:
Marc: take note: Id like to NOT BOUNCE an email back to the victim of
backscatter if they bothered to publish SPF or SENDER ID records that
don't match the incoming.
It's the other way around. you shoul
One thing I would like to see (and this is a different subject:
Marc: take note: Id like to NOT BOUNCE an email back to the victim of
backscatter if they bothered to publish SPF or SENDER ID records that
don't match the incoming.
(and, yes, this would NOT work behind a proxy)
I would like the pr
Anyone have an answer that isn't obvious?
I already said I can't put it on the proxy.
--
Michael Scheidell, CTO
Office: 561-999-5000 x 1259
Direct: 561-939-7259
Real time security alerts: http://www.secnap.com/news
_
This em
On Sun, Sep 23, 2007 at 01:50:43PM -0400, Michael Scheidell wrote:
> Sometimes a large company will have a proxy server set up in the DMZ and
> then send it to their internal mail server.
...
> #1, SPF. SPF helo, SENDERID
> The proxy will be adding a received header, and announcing 'HELO/EHLO'
>
Every problem you've named here is solved by putting Amavis/SA on the
proxy instead of the internal system.
If the proxy doesn't do the spam-checking, and the internal system does
I can name a dozen other problems that will occur, the most important of
which will be backscatter. 2-step relay
On 29.07.07 09:29, Michael Scheidell wrote:
> Followup to my post:
>
> I upgraded all the dependencies and while it still complains, SA no
> longer Segv's
I'd say it should score, not complain about forged domainkeys signature :)
--
Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantoma
Followup to my post:
I upgraded all the dependencies and while it still complains, SA no
longer Segv's
drwxr-xr-x 2 root wheel 512 Jul 29 09:13 p5-Digest-SHA-5.45
drwxr-xr-x 2 root wheel 512 Jul 29 09:13
p5-Crypt-OpenSSL-RSA-0.25
drwxr-xr-x 2 root wheel 512 Jul 29 09:13
p5-Cr
Michael Scheidell wrote:
Don't know if anyone has mentioned this, if so, I missed it.
Potential DOS in spamassassin if perl-Net-DNS < .60. (previously
recommended version was .58)
Freebsd ports has .60, for the last two weeks.
Thanks for the FYI.
MrC
-Original Message-
From: rPath U
From: "Leon Kolchinsky" <[EMAIL PROTECTED]>
I've never run amavisd-new in chroot, but may be you'll find some tips
here - http://www.ijs.si/software/amavisd/README.chroot Seems to me
like a resolver issue (probably need to configure FreeBSD a little
different than OpenBSD). Best Regards,
Well
>
> What would a perl command look like to resolve a host? Because I think it
> is
> a perl issue.
>
> Helmut
I've never run amavisd-new in chroot, but may be you'll find some tips here -
http://www.ijs.si/software/amavisd/README.chroot
Seems to me like a resolver issue (probably need to co
From: "Helmut Schneider" <[EMAIL PROTECTED]>
[problems resolving a host]
Damn!!
[EMAIL PROTECTED] ~]# cat /var/amavis/test2.pl
#!/usr/bin/perl -w
use Net::DNS;
my $res = Net::DNS::Resolver->new;
my $query = $res->search("www.google.de");
if ($query) {
foreach my $rr ($query->answer
From: "Leon Kolchinsky" <[EMAIL PROTECTED]>
Stupid question, but $MYHOME = /var/amavis ?
Yes
Also you can try to debug it with strace.
Look for all the files you're missing in the jail and copy them into it.
(here is a little example on how to use strace to find requirements
outside the jail
> >> I tried to set up SA with AMaViS in a chrooted environment
> >> ($daemon_chroot_dir = $MYHOME). I (thought I) copied all necessary
> files
> >> to
> >> the jail but when SA is starting I get an error:
> >> Jul 10 10:44:02 TEG /usr/local/sbin/amavisd[6817]: SpamControl:
> >> initializing
> >> M
From: "Leon Kolchinsky" <[EMAIL PROTECTED]>
I tried to set up SA with AMaViS in a chrooted environment
($daemon_chroot_dir = $MYHOME). I (thought I) copied all necessary files
to
the jail but when SA is starting I get an error:
Jul 10 10:44:02 TEG /usr/local/sbin/amavisd[6817]: SpamControl:
init
> Hi,
>
> I tried to set up SA with AMaViS in a chrooted environment
> ($daemon_chroot_dir = $MYHOME). I (thought I) copied all necessary files
> to
> the jail but when SA is starting I get an error:
>
> Jul 10 10:44:02 TEG /usr/local/sbin/amavisd[6817]: SpamControl:
> initializing
> Mail::SpamAs
Hi
It works fine on several Freebsd 5.x i386 machines. sa-compile works
too. No problem so far after a few million scans. Thank you. I will try
your updated version for amd64 at the end of this week.
Regards,
Thomas
Michael Scheidell wrote:
> If anyone wants a 'pre release' of the Freebsd sa 3
I can't resolve them here (tried on two different co-located servers as
well)
On Tue, 2007-05-01 at 21:05 +0200, Oenus Tech Services wrote:
> Hello. I know this is a little off-topic, but I'm having this problem
> and I guess this is a good place to ask for this kind of help. Today,
> 1st of May,
On 3/29/07, Jonathan M Metts <[EMAIL PROTECTED]> wrote:
How many people use an Amavis setup to send messages through SA and
possibly ClamAV? Over the past month I have been trying to tweak my
setup that has been running Postfix, SA, Cyrus-IMAP, and Sieve for
awhile (running Debian), but wanted t
Michael wrote:
> Using sql based AWL, this target:
> select * from awl where email like "%peppers%";
> +--+---++---+---
> ---+
> | username | email | ip | count |
> totscore |
> +--+---
On Thu, Aug 03, 2006 at 11:47:58AM -0500, Stuart Johnston wrote:
> I'm a little confused about this as well. When I run spamassassin -D, it
> shows rules being loaded from /var/lib/spamassassin/3.001003 and
> /etc/mail/spamassassin but NOT /usr/share/spamassassin/
That sounds correct.
> Also,
Gary V wrote:
Mark wrote:
Theo,
to change Mail::SpamAssassin to provide a suitable default
for LOCAL_STATE_DIR. Please consider this a feature request.
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4952 :)
Appreciated!
# sa-update --updatedir /usr/local/share/spamassassin
From: Juan Machado [mailto:[EMAIL PROTECTED]
>
> Any Amavis-new expert here ?
There may be, but you'd be better off asking on the Amavis list.
http://lists.sourceforge.net/lists/listinfo/amavis-user
Bowie
On Sep 22, 2004, at 7:15 PM, Ken Versteeg wrote:
How will these changes affect the way the functions are called from
amavisd-new? Has anyone successfully upgraded SpamAssassin to 3.0?
Is my
current version of Amavisd-new sufficient?
make sure you have version of amavisd-new that understands SA
- Original Message -
From: "Ken Versteeg" <[EMAIL PROTECTED]>
> I'm currently running Amavis-new-20030616-p5 with SpamAssassin-2.55,
Postfix
> and Perl_5.6.1. I'd like to upgrade to SpamAssassin 3.0 (released today),
> but I'm concerned about some of the changes made to the interface. T
44 matches
Mail list logo
