On 14/08/18 10:36, Matus UHLAR - fantomas wrote:
so, what is the problem?
On 14.08.18 11:22, Danny Horne wrote:
None as far as I'm aware, but this is my first time using Postscreen, so
wanted to check that I hadn't messed anything up
aha. You'll find that from:
"postfix/postscreen[...]: NOQ
On 14/08/18 10:36, Matus UHLAR - fantomas wrote:
>
> so, what is the problem?
>
None as far as I'm aware, but this is my first time using Postscreen, so
wanted to check that I hadn't messed anything up
On 13.08.18 21:36, Danny Horne wrote:
I'm trying out Postscreen after having used Postgrey for some time. The
reason for the switch is that Postgrey can cause emails from Google etc.
to take a long time to come through due to the large number of IP
addresses they use (and I don't want to whiteli
Hi all,
I'm trying out Postscreen after having used Postgrey for some time. The
reason for the switch is that Postgrey can cause emails from Google etc.
to take a long time to come through due to the large number of IP
addresses they use (and I don't want to whitelist the GMail addresses).
Here'
On 26 May 2018, at 23:27, Voytek wrote:
> On Sun, May 27, 2018 3:22 am, /dev/rob0 wrote:
>
>> The obvious solution, if dnsbl.spfbl.net is blocking real mail, is to
>> stop using that list, or possibly to lower its score below your [unstated]
>> threshold score.
>
> Thanks for all replies and com
On Sun, May 27, 2018 3:22 am, /dev/rob0 wrote:
> The obvious solution, if dnsbl.spfbl.net is blocking real mail, is to
> stop using that list, or possibly to lower its score below your [unstated]
> threshold score.
Thanks for all replies and comments!
I guess my starting point should be that, lo
On 2018-05-26 (11:22 MDT), /dev/rob0 wrote:
>
> If you're not going to take the advice above, your only other option
> would be to whitelist the IP address[es]. Oh, also, you could talk
> to the DNSBL operator about theit listing criteria, and/or to the
> sending site about getting delisted.
On Sat, May 26, 2018 at 01:22:01PM +1000, Voytek wrote:
> I've recently updated Postfix from 2.1, and, enabled postscreen,
> all's working well, though, just picked up a false positive:
>
> several users inbound mail blocked with dnsbl.spfbl.net
>
> I have like:
>
> # grep spfbl.net main.cf
> p
@lbutlr:
> On 2018-05-25 (21:22 MDT), "Voytek" wrote:
> > # grep health.gov.au /var/log/maillog | grep block
> > May 21 08:49:16 geko postfix/postscreen[23877]: NOQUEUE: reject: RCPT from
> > [152.91.65.145]:57512: 550 5.7.1 Service unavailable; client
> > [152.91.65.145] blocked using dnsbl.spfbl
On 2018-05-25 (21:22 MDT), "Voytek" wrote:
> # grep health.gov.au /var/log/maillog | grep block
> May 21 08:49:16 geko postfix/postscreen[23877]: NOQUEUE: reject: RCPT from
> [152.91.65.145]:57512: 550 5.7.1 Service unavailable; client
> [152.91.65.145] blocked using dnsbl.spfbl.net;
> from=, to=,
I've recently updated Postfix from 2.1, and, enabled postscreen, all's
working well, though, just picked up a false positive:
several users inbound mail blocked with dnsbl.spfbl.net
I have like:
# grep spfbl.net main.cf
postscreen_dnsbl_sites = zen.spamhaus.org*5, psbl.surriel.com*2,
bl.spamcop.
Thanks for all the help.
John A
sure you don't want any mail from any host on that list. I
keep a "reject_rbl_client zen.spamhaus.org" in my restrictions, and
then I have an insanely complex mess of restriction classes which
might call other DNSBLs based on recipient domain.
My postscreen setup would be so
e you don't want any mail from any host on that list. I
keep a "reject_rbl_client zen.spamhaus.org" in my restrictions, and
then I have an insanely complex mess of restriction classes which
might call other DNSBLs based on recipient domain.
> My postscreen setup would be somet
On Thu, Mar 31, 2016 at 02:01:57PM -0400, John Allen wrote:
> From everything I had read I expected the smtp entry in master to be
>
> smtp inet n - n - 1postscreen
> -o cleanup_service_name=pre-cleanup
>
> But you are saying it should be
>
> smtp
On Mar 31, 2016, at 1:32 PM, John Allen wrote:
I have read the documentation and it would appear that I don't need to do very
much to get postscreen working. Which makes me think I have got it wrong.
So I have some questions:
1) I have to change smtp ... smtpd to smtp ... postscreen. As my
John Allen:
> As postscreen does dnsbl lookups do I still need the reject_rbl_client
> entries in smtpd_recipient_restrictions? Do the latter entries do more
> than the dnsbl entries?
It does not hurt. The DNS reply is cached in the DNS server.
> My postscreen setup would be so
> On Mar 31, 2016, at 1:32 PM, John Allen wrote:
>
> I have read the documentation and it would appear that I don't need to do
> very much to get postscreen working. Which makes me think I have got it
> wrong.
>
> So I have some questions:
>
> 1) I have to change smtp ... smtpd to smtp ...
_client
entries in smtpd_recipient_restrictions? Do the latter entries do more
than the dnsbl entries?
My postscreen setup would be something like:
# postscreen_access_list = permit_mynetworks do I need this
postscreen_bare_newline_action = enforce
postscreen_bare_n
19 matches
Mail list logo
