Am 30.04.2015 um 17:06 schrieb Benny Pedersen:
Matus UHLAR - fantomas skrev den 2015-04-30 12:55:
no, it's the "dig" command that does the trace, not the nameserver.
This says nothing about your nameserver configuration, and it can't since
nameserver does not provide that info.
dig respects
Matus UHLAR - fantomas skrev den 2015-04-30 12:55:
no, it's the "dig" command that does the trace, not the nameserver.
This says nothing about your nameserver configuration, and it can't
since
nameserver does not provide that info.
dig respects resolv.conf with nameserver 127.0.0.1
try it :
Tom Robinson skrev den 2015-04-30 04:35:
Finally that makes sense. I will add the forwarding in as per the
documentation.
remove forwarding is safe, only use forward dns on zones you self build
or have rsync access to
Tom Robinson skrev den 2015-04-30 04:14:
Actually, looking for this config I can't seem to find it. My
spamassassin is linked in with qmail
using qmail-scanner-queue.pl. That script looks in
/home/qscand/.spamassassin/user_prefs but I also
have configs in /etc/mail/spamassassin. What am I lookin
On 4/30/15, 5:55 AM, "Matus UHLAR - fantomas" wrote:
>no, it's the "dig" command that does the trace, not the nameserver.
>This says nothing about your nameserver configuration, and it can't since
>nameserver does not provide that info.
I stand corrected-- I had tested on another machine that us
On 30/04/15 09:56, Marieke Janssen wrote:
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more informa
Am 30.04.2015 um 12:55 schrieb Matus UHLAR - fantomas:
On 4/30/15, 12:16 AM, "Tom Robinson" wrote:
BTW, where can I see the results of my configuration changes? It
would be
nice to confirm that my
changes have rectified the situation.
On 30.04.15 01:38, Dave Pooser wrote:
On the server (via
>On the server (via SSH or console) use the +trace argument to dig, and
>then look for lines starting with ';;':
>postmstr@smtp:~$ dig +trace example.com.multi.uribl.com | grep ';;'
>;; global options: +cmd
>;; Received 913 bytes from 127.0.0.1#53(127.0.0.1) in 8 ms
>;; Received 760 bytes from 199
On 4/30/15, 12:16 AM, "Tom Robinson" wrote:
BTW, where can I see the results of my configuration changes? It would be
nice to confirm that my
changes have rectified the situation.
On 30.04.15 01:38, Dave Pooser wrote:
On the server (via SSH or console) use the +trace argument to dig, and
then
On 4/30/15, 12:16 AM, "Tom Robinson" wrote:
>BTW, where can I see the results of my configuration changes? It would be
>nice to confirm that my
>changes have rectified the situation.
On the server (via SSH or console) use the +trace argument to dig, and
then look for lines starting with ';;':
p
Am 30.04.2015 um 07:16 schrieb Tom Robinson:
On 30/04/15 15:09, Reindl Harald wrote:
Am 30.04.2015 um 04:10 schrieb Tom Robinson:
Is it correct that currently, because I'm forwarding, the DNSBL query is
denied because the DNSBL server thinks I'm the ISP making a query? Sorry, I'm
not under
On 30/04/15 15:09, Reindl Harald wrote:
>
>
> Am 30.04.2015 um 04:10 schrieb Tom Robinson:
>> Is it correct that currently, because I'm forwarding, the DNSBL query is
>> denied because the DNSBL server thinks I'm the ISP making a query? Sorry,
>> I'm not understanding the
>> mechanism
>
> it is th
Am 30.04.2015 um 04:10 schrieb Tom Robinson:
Is it correct that currently, because I'm forwarding, the DNSBL query is
denied because the DNSBL server thinks I'm the ISP making a query? Sorry, I'm
not understanding the
mechanism
it is the ISP making the query for you and thousands of other of
Am 30.04.2015 um 04:10 schrieb Tom Robinson:
I have the mail server and a separate name server set up in a DMZ. The name
server already runs as a
caching nameserver but does forwarding to our ISP
don't do that when you are running mailservers or for whateverer reason
rely on trustable names
On 30/04/15 12:15, Kevin A. McGrail wrote:
> On 4/29/2015 10:10 PM, Tom Robinson wrote:
>> I have the mail server and a separate name server set up in a DMZ. The name
>> server already runs as a
>> caching nameserver but does forwarding to our ISP.
> Hi Tom,
>
> Your ISP is doing too many queries
On 4/29/2015 10:10 PM, Tom Robinson wrote:
I have the mail server and a separate name server set up in a DMZ. The name
server already runs as a
caching nameserver but does forwarding to our ISP.
Hi Tom,
Your ISP is doing too many queries to the services exceeding free
limits. You are being l
Tom Robinson
IT Manager/System Administrator
MoTeC Pty Ltd
121 Merrindale Drive
Croydon South
3136 Victoria
Australia
T: +61 3 9761 5050
F: +61 3 9761 5051
E: tom.robin...@motec.com.au
On 30/04/15 10:10, Benny Pedersen wrote:
> Tom Robinson skrev den 2015-04-30 01:38:
>
>> 0.0 URIBL_BLOCK
On 30/04/15 09:56, Marieke Janssen wrote:
> Hi,
>
> Besides your awl problem, you have other problems.
>
> 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
> blocked.
> See
>
> http://wiki.apache.org/spamassassin/D
Tom Robinson skrev den 2015-04-30 01:38:
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL
was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
did you read the url here ?
well if yes, show your AWL config for the AWL
Hi,
Besides your awl problem, you have other problems.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was
blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for
Hi,
Below is the source from an email that is clearly spam but the AWL is -1.3
defeating the spam classification. How can I best adjust the AWL to get this
classified as SPAM.
Kind regards,
Tom
--
Tom Robinson
IT Manager/System Administrator
MoTeC Pty Ltd
121 Merrindale Drive
Croydon South
21 matches
Mail list logo
