W dniu 2015-05-05 o 22:07, Benny Pedersen pisze:
> Marcin Mirosław skrev den 2015-05-05 21:21:
>
My goal is to configure SA to not check IP of client (in this example
31.61.129.221).
>>>
>>> Can you elaborate about what's going on here? What do the two hand-overs
>>> represent? What do y
On Tue, 05 May 2015 21:21:58 +0200
Marcin Miros?aw wrote:
>
> So it's not important for my if address 31.61.129.221 is on any rbl
> because I'm not getting email directly from this ip. It's important
> for me if server 89.161.182.208 (which directly connects to my mta)
> is in any RBL. I'd like S
Marcin Mirosław skrev den 2015-05-05 21:56:
RCVD_IN_SBL_CSS. It looks that "lastexternal" is what I'm looking for.
Is it possible to add '-lastexternal' to all RBL?
would be contra productive
in local.cf:
internal_networks
trusted_networks
# whitelist rbl ips that hits to much on rbl when
Marcin Mirosław skrev den 2015-05-05 21:21:
My goal is to configure SA to not check IP of client (in this example
31.61.129.221).
Can you elaborate about what's going on here? What do the two
hand-overs
represent? What do you mean by "real MTA"?
Thanks for both answers. I'll try to describ
W dniu 2015-05-05 o 21:47, Kevin A. McGrail pisze:
> On 5/5/2015 3:38 PM, Marcin Mirosław wrote:
>> I'm thinking about removing all Received headers from email except added
>> by my MTA, storing it, sending email to spamd and restoring headers. But
>> it looks like using a sledgehammer to crack a n
On 5/5/2015 3:38 PM, Marcin Mirosław wrote:
I'm thinking about removing all Received headers from email except added
by my MTA, storing it, sending email to spamd and restoring headers. But
it looks like using a sledgehammer to crack a nut:)
What RBL are you concerned about specifically because s
Am 05.05.2015 um 21:38 schrieb Marcin Mirosław:
W dniu 2015-05-05 o 21:28, Reindl Harald pisze:
Am 05.05.2015 um 21:21 schrieb Marcin Mirosław:
Thanks for both answers. I'll try to describe it using ascii art:
----
|random user
W dniu 2015-05-05 o 21:28, Reindl Harald pisze:
>
>
> Am 05.05.2015 um 21:21 schrieb Marcin Mirosław:
>> Thanks for both answers. I'll try to describe it using ascii art:
>> ----
>> |random user sending email |sends email |89.161.1
Am 05.05.2015 um 21:21 schrieb Marcin Mirosław:
Thanks for both answers. I'll try to describe it using ascii art:
----
|random user sending email |sends email |89.161.182.208 from this |
|(in my case: 31.61.129.221) |--->
W dniu 2015-05-05 o 20:29, RW pisze:
> On Tue, 05 May 2015 10:51:22 +0200
> Marcin Miros?aw wrote:
>
>> Hi!
>> I'm ashamed to ask because this problem is like boomerang but still
>> can't find solution. I'm reading e.g.:
>> http://spamassassin.1065346.n5.nabble.com/How-to-ignore-multiple-Received-
On Tue, 05 May 2015 10:51:22 +0200
Marcin Miros?aw wrote:
> Hi!
> I'm ashamed to ask because this problem is like boomerang but still
> can't find solution. I'm reading e.g.:
> http://spamassassin.1065346.n5.nabble.com/How-to-ignore-multiple-Received-headers-td52450.html
>
> I set trusted_network
On 5/5/2015 10:12 AM, J.J. Day wrote:
It seemed simpler so I selected Choice A. This is the diff of
Diff looks good.
and restarted mimedefang. But the logs still look the same.
Wherever you normally get the unintialized errors prior...
This and the patch to TxRep are currently the only code
Marcin Mirosław skrev den 2015-05-05 10:51:
My goal is to configure SA to not check IP of client (in this example
31.61.129.221).
local.cf:
trusted_networks 31.61.129.221/32
reload spamd or other glue for spamassassin
On 5/5/2015 1:54 PM, Carlos Velasco wrote:
Yes, spamc/spamd.
Ahh. What MTA are you using?
And if you are getting the uninitialized warnings, can you send me an
example email off list?
regards,
KAM
Yes, spamc/spamd.
Regards
Original Message
Subject: Re: TxRep $msgscore warning
From: Kevin A. McGrail
To: Carlos Velasco ,
users@spamassassin.apache.org
Date: 5/5/2015 19:53:00
> On 5/5/2015 7:59 AM, Carlos Velasco wrote:
>> Hi,
>>
>> After activating TxRep I always receive t
On 5/5/2015 7:59 AM, Carlos Velasco wrote:
Hi,
After activating TxRep I always receive these warnings.
I use mysql for TxRep and I see a lot of "@sa_generated"
entries in the database, don't know if they are right.
I have activated all spamd debugs and included your block in TxRep.
T
Hi KAM,
It seemed simpler so I selected Choice A. This is the diff of
mimeassassin.pl:
6839a6840,6856
#***
> # %spam_assassin_init debug channel mod
> # From: "Kevin A. McGrail"
> # Subject: Re: TxRep $msgscore warning
>
Hi,
After activating TxRep I always receive these warnings.
I use mysql for TxRep and I see a lot of "@sa_generated" entries
in the database, don't know if they are right.
I have activated all spamd debugs and included your block in TxRep. This
is the output:
===
rules: running one_line_
Hi!
I'm ashamed to ask because this problem is like boomerang but still
can't find solution. I'm reading e.g.:
http://spamassassin.1065346.n5.nabble.com/How-to-ignore-multiple-Received-headers-td52450.html
I set trusted_networks but I can't see how can it helps (and it doesn't
work as I wish). I'm
19 matches
Mail list logo
