On 3/7/2012 8:21 PM, Alex wrote:
> I've set this on both the primary and secondary MX servers now.
So now you only need to pay attention to non bulk senders to make sure
they're not delaying due to the 1 connection limit. It most likely
won't be a problem, but keep an eye on it just in case.
>
Hi,
>> Yes, understood. There are two MXs for the domain that has the bulk
>> mailing overload problem and the one I'm adjusting the
>> default_process_limit. There is one MX for the domain that has the
>> always_bcc issue and the submission port auth issue.
>
> Let's concentrate on the connection
On 3/7/2012 2:08 PM, Alex wrote:
> Okay, great. I don't think I understood your previous post regarding
> the IP list and the policy daemon. I'll have to research that further.
> All the connections from everbridge.net were from the same IP.
Yeah, smtpd_client_connection_count_limit=1 is the quic
Hi,
>>> -o smtpd_recipient_restrictions=permit_mynetworks,reject
>
>> Isn't this effectively what I already have? I must be missing
>> differences somewhere?
>
> You're missing a recipient_restrictions override. Without one, your
> submission connections are subject to dnsbl checks when au
Hi,
>> far-reaching solution. I've used tc and cbq for QoS a long time in the
>> past, but not sure I could now figure out how to use it to throttle
>> SMTP traffic now.
>
> If you want a global solution to the parallel client connection problem,
> this is it:
>
> smtpd_client_connection_count_lim
On 3/6/2012 8:49 PM, Alex wrote:
>>-o smtpd_recipient_restrictions=permit_mynetworks,reject
> Isn't this effectively what I already have? I must be missing
> differences somewhere?
You're missing a recipient_restrictions override. Without one, your
submission connections are subject to
On 3/6/2012 8:01 PM, Alex wrote:
> I don't recall seeing an email from you with that information. Can I
> ask you to resend, and I'll follow up with her?
It was delivered to your Gmail mailbox yesterday:
/var/log/mail.log:Mar 5 16:37:55 greer postfix/smtp[25300]: CB3636C052:
to=,
relay=gmail-sm
Hi,
--master.cf--
submission inet n - n - - smtpd
-o smtpd_tls_security_level=encrypt
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=permit_sasl_authenticated,reject
>>>
>>> -o smtpd_recipient_restrictions=
>>
>> This wil
Hi,
>> I've just noticed I'm using reject_rbl_client and have postscreen
>> using the RBLs as well. I'll remove the ones from the
>> smtpd_client_restrictions, but could this possibly be causing mail to
>> be rejected even when connecting via the submission port?
>
> My two cents on that: when imp
Hi,
>> My apologies; this is for a similar, but different system. It looks
>> like I've made the same mistake on multiple systems. I'm very
>
> Ahh, ok, that would explain the discrepancy.
>
>> appreciative that you remembered my similar issue from weeks ago :-)
>
> After helping you with that, an
On Tue, Mar 06, 2012 at 04:44:26PM -0600, Stan Hoeppner wrote:
> On 3/6/2012 2:25 PM, /dev/rob0 wrote:
> > On Tue, Mar 06, 2012 at 01:30:59PM -0600, Stan Hoeppner wrote:
> >> On 3/6/2012 11:03 AM, Alex wrote:
> >>
> >>> --master.cf--
> >>> submission inet n - n - - smt
On 3/6/2012 2:46 PM, Alex wrote:
>> On 2/23/2012 1:50 PM, Alex wrote:
>>
>>> I've removed the zen and psbl queries from smtpd and moved psbl to
>>> postscreen.
>>
>> You claimed to have made this change a couple of weeks ago per my
>> advice, and confirmed said change to Wietse. Did you change it
On 3/6/2012 2:25 PM, /dev/rob0 wrote:
> On Tue, Mar 06, 2012 at 01:30:59PM -0600, Stan Hoeppner wrote:
>> On 3/6/2012 11:03 AM, Alex wrote:
>>
>>> --master.cf--
>>> submission inet n - n - - smtpd
>>> -o smtpd_tls_security_level=encrypt
>>> -o smtpd_sasl_auth_enabl
Hi,
>> I've just noticed I'm using reject_rbl_client and have postscreen
>> using the RBLs as well. I'll remove the ones from the
>> smtpd_client_restrictions, but could this possibly be causing mail to
>> be rejected even when connecting via the submission port?
>
>> Any ideas greatly appreciated
On Tue, Mar 06, 2012 at 01:30:59PM -0600, Stan Hoeppner wrote:
> On 3/6/2012 11:03 AM, Alex wrote:
>
> > --master.cf--
> > submission inet n - n - - smtpd
> > -o smtpd_tls_security_level=encrypt
> > -o smtpd_sasl_auth_enable=yes
> > -o smtpd_client_restrictions=
On 3/6/2012 1:23 PM, /dev/rob0 wrote:
> My two cents on that: when implementing postscreen, leave your
> smtpd_*_restrictions alone. They were working before, so keep them in
> reserve. For example, when under stress, it is possible that DNSBL
> queries will not return before the 2-second timeo
On 3/6/2012 11:03 AM, Alex wrote:
> --master.cf--
> submission inet n - n - - smtpd
> -o smtpd_tls_security_level=encrypt
> -o smtpd_sasl_auth_enable=yes
> -o smtpd_client_restrictions=permit_sasl_authenticated,reject
-o smtpd_recipient_restrictions=
-o
Sorry for the long post, but I am leaving in the entire quoted
message.
On Tue, Mar 06, 2012 at 12:03:23PM -0500, Alex wrote:
> I have a postfix-2.8.7 system with amavisd on fedora15 and am
> having some problems with users being rejected by zen even when
> connecting to the server using the su
On 3/6/2012 11:03 AM, Alex wrote:
> I've just noticed I'm using reject_rbl_client and have postscreen
> using the RBLs as well. I'll remove the ones from the
> smtpd_client_restrictions, but could this possibly be causing mail to
> be rejected even when connecting via the submission port?
> Any i
Hi,
I have a postfix-2.8.7 system with amavisd on fedora15 and am having
some problems with users being rejected by zen even when connecting to
the server using the submission port. I believe this has to do with my
smtpd_client_restrictions being incorrect. Because of the way in which
I have the o
20 matches
Mail list logo
