On Wed, 27 May 2020, LuKreme wrote:
On May 27, 2020, at 20:08, John Hardin wrote:
On Wed, 27 May 2020, @lbutlr wrote:
On 27 May 2020, at 18:27, RW wrote:
I should have added that if whitelist_from_rcvd *@* server.example.com
(without the colon) is only only failing occasionally on mail fr
On 27.05.20 10:35, @lbutlr wrote:
What, if any, local SpamAssassin settings does spams-milter use when
processing incoming mail?
don't you mean spamass-milter?
For example, if I wanted to white list a sender or blacklist a domain, would
the general settings in /usr/local/etc/spamassasin/loca
On May 27, 2020, at 20:08, John Hardin wrote:
>
> On Wed, 27 May 2020, @lbutlr wrote:
>>> On 27 May 2020, at 18:27, RW wrote:
>>> I should have added that if whitelist_from_rcvd *@* server.example.com
>>> (without the colon) is only only failing occasionally on mail from
>>> server.example.com
On Wed, 27 May 2020, @lbutlr wrote:
On 27 May 2020, at 18:27, RW wrote:
I should have added that if whitelist_from_rcvd *@* server.example.com
(without the colon) is only only failing occasionally on mail from
server.example.com, it's probably just an rDNS lookup failure of some
sort.
Well,
On 27 May 2020, at 18:27, RW wrote:
> I should have added that if whitelist_from_rcvd *@* server.example.com
> (without the colon) is only only failing occasionally on mail from
> server.example.com, it's probably just an rDNS lookup failure of some
> sort.
Well, I do not get anything that I co
On Thu, 28 May 2020 01:04:20 +0100
RW wrote:
> On Wed, 27 May 2020 10:35:26 -0600
> @lbutlr wrote:
> > I am wondering because I have a server whitelisted in that file (or
> > do I?), but I am seeing occasional logs like:
> The lack of recorded rDNS is a common reason for failure.
I should have
On Wed, 27 May 2020 10:35:26 -0600
@lbutlr wrote:
> What, if any, local SpamAssassin settings does spams-milter use when
> processing incoming mail?
>
> For example, if I wanted to white list a sender or blacklist a
> domain, would the general settings in
> /usr/local/etc/spamassasin/local.cf be
On 27 May 2020, at 10:44, Robert Schetterer wrote:
> Am 27.05.20 um 18:35 schrieb @lbutlr:
>> # Allow all mailing list posts from example.com
>> whitelist_from_rcvd: *@* server.example.com
Actual file has "whitelist_from_rcvd *@* server.example.com" without the ':'.
Was hopeful that was the iss
Am 27.05.20 um 18:35 schrieb @lbutlr:
What, if any, local SpamAssassin settings does spams-milter use when processing
incoming mail?
For example, if I wanted to white list a sender or blacklist a domain, would
the general settings in /usr/local/etc/spamassasin/local.cf be the place?
I am wond
What, if any, local SpamAssassin settings does spams-milter use when processing
incoming mail?
For example, if I wanted to white list a sender or blacklist a domain, would
the general settings in /usr/local/etc/spamassasin/local.cf be the place?
I am wondering because I have a server whiteliste
Am 15.02.2015 um 19:35 schrieb LuKreme:
> On 15 Feb 2015, at 04:01 , Robert Schetterer wrote:
>> Am 15.02.2015 um 01:29 schrieb LuKreme:
>>> Spamass-milter is (as designed, I’m sure) checking outbound mail. When it
>>> does this, SPF checks fail and a lot of outbound mail is getting scored as
>>
On 15 Feb 2015, at 12:05 , Reindl Harald wrote:
> Am 15.02.2015 um 20:00 schrieb LuKreme:
>>
>> -o receive_override_options=no_milter
>
> sorry - copy&paste error
> no_milterS
Funny we were both making the same typo at the same time… Sigh.
Thanks, sorted now. Yay.
> http://www.postfix.org/p
Am 15.02.2015 um 20:00 schrieb LuKreme:
On 15 Feb 2015, at 11:44 , Reindl Harald wrote:
by set "-o receive_override_options=no_milter" for your submission service in
“master.cf"
I tried that already.
mail submit-tls/smtpd[46597]: fatal: unknown receive_override_options value "no_milter"
i
On 15 Feb 2015, at 11:44 , Reindl Harald wrote:
> by set "-o receive_override_options=no_milter" for your submission service in
> “master.cf"
I tried that already.
mail submit-tls/smtpd[46597]: fatal: unknown receive_override_options value
"no_milter" in "no_milter"
submission inet n
Am 15.02.2015 um 19:35 schrieb LuKreme:
On 15 Feb 2015, at 04:01 , Robert Schetterer wrote:
Am 15.02.2015 um 01:29 schrieb LuKreme:
Spamass-milter is (as designed, I’m sure) checking outbound mail. When it does
this, SPF checks fail and a lot of outbound mail is getting scored as spam
beca
On 15 Feb 2015, at 04:29 , Reindl Harald wrote:
> attached a "local.cf" from the submission server
I just have the one server handling submission and outbound mail.
# postconf -n | grep milter
milter_default_action = accept
smtpd_milters = unix:/var/run/spamass-milter.sock
# grep milter /etc
On 15 Feb 2015, at 04:01 , Robert Schetterer wrote:
> Am 15.02.2015 um 01:29 schrieb LuKreme:
>> Spamass-milter is (as designed, I’m sure) checking outbound mail. When it
>> does this, SPF checks fail and a lot of outbound mail is getting scored as
>> spam because of it.
>
> works like designed
Am 15.02.2015 um 12:20 schrieb Reindl Harald:
that's why we don't mix inbound and autobound mail
* SA is running on the MX
* mail is filtered and clean mail relayed over
100027 to the final server
* final server has "-o receive_override_options=no_milters" in master.cf
* the bayes is rsynced
Am 15.02.2015 um 01:29 schrieb LuKreme:
Spamass-milter is (as designed, I’m sure) checking outbound mail. When it does
this, SPF checks fail and a lot of outbound mail is getting scored as spam
because of it.
The domains in question *do* have SPF records
that's why we don't mix inbound and
Am 15.02.2015 um 01:29 schrieb LuKreme:
> Spamass-milter is (as designed, I’m sure) checking outbound mail. When it
> does this, SPF checks fail and a lot of outbound mail is getting scored as
> spam because of it.
works like designed
dont use spamass-milter for outbound ( or go the long way con
Spamass-milter is (as designed, I’m sure) checking outbound mail. When it does
this, SPF checks fail and a lot of outbound mail is getting scored as spam
because of it.
The domains in question *do* have SPF records.
--
Why can't you be in a good mood? How hard is it to decide to be in a
good m
21 matches
Mail list logo
