li...@mbchandler.net:
> Most of the time, this is not a problem. This IP for example is a
> spammer and I want them to be limited. But I have a legitimate server
> that needs to send a lot of email at once. Can I bypass this limit by
> adding the sender's IP to postscreen_access.cidr? I've alrea
Noel Jones:
> On 11/10/2017 10:33 AM, li...@mbchandler.net wrote:
> > I have postscreen setup according to the how-to. I use the following
> > configuration for the access list. As I understand it, I can only
> > add IP addresses or ranges to this list. Is it possible to whitelist
> > the domain na
Thanks, I thought that might be the case.
The problem I'm trying to solve is these messages in the log file:
postfix/postscreen[2938]: NOQUEUE: reject: CONNECT from
[91.238.9.63]:38101: too many connections
I think this must be from the limit I set up with
smtpd_client_connection_count_limit
On 11/10/2017 10:33 AM, li...@mbchandler.net wrote:
> I have postscreen setup according to the how-to. I use the following
> configuration for the access list. As I understand it, I can only
> add IP addresses or ranges to this list. Is it possible to whitelist
> the domain name in the from address
On 10.11.17 10:33, li...@mbchandler.net wrote:
I have postscreen setup according to the how-to. I use the following
configuration for the access list. As I understand it, I can only add
IP addresses or ranges to this list. Is it possible to whitelist the
domain name in the from address?
no. p
On 1 Jun 2016, at 9:29, @lbutlr wrote:
On May 31, 2016, at 8:30 PM, Steve Jenkins
wrote:
A quick way to do this is to download postwhite and add web.com to
the list of queried hosts. All their known (published) IPs and CIDRs
wlll be added to your Postscreen whitelist.
Post white looks inter
> On May 31, 2016, at 7:24 PM, Michael Orlitzky wrote:
>
> With that in mind, you're putting way too much faith in dnsbl.sorbs.net
> and hostkarma.junkemailfilter.com. For a reference point, I have the
> same threshold as you (3) but score them each one point.
Thanks Michael. I've backed off on
On Wed, Jun 1, 2016 at 6:29 AM, @lbutlr wrote:
> On May 31, 2016, at 8:30 PM, Steve Jenkins wrote:
> > A quick way to do this is to download postwhite and add web.com to the
> list of queried hosts. All their known (published) IPs and CIDRs wlll be
> added to your Postscreen whitelist.
>
> Post
On May 31, 2016, at 8:30 PM, Steve Jenkins wrote:
> A quick way to do this is to download postwhite and add web.com to the list
> of queried hosts. All their known (published) IPs and CIDRs wlll be added to
> your Postscreen whitelist.
Post white looks interesting, but what is web.com? It looks
On Tue, May 31, 2016 at 7:24 PM, Michael Orlitzky
wrote:
> On 05/31/2016 08:16 PM, Terry Barnum wrote:
> >
> > Since web.com probably has a fleet of mail servers, do I need to find
> and enter all their IPs into my postscreen_access.cidr? Is there an easier
> way?
> >
>
> That's generally what yo
On 05/31/2016 08:16 PM, Terry Barnum wrote:
>
> Since web.com probably has a fleet of mail servers, do I need to find and
> enter all their IPs into my postscreen_access.cidr? Is there an easier way?
>
That's generally what you have to do. Postscreen is meant to catch the
most obvious offenders
11 matches
Mail list logo
