785 243 via Postfix-users:
> I want to implement rate limiting based on the target server rather
> than by recipient domain. Specifically, I want to rate limit email
> sent to domains like yahoo.com, ymail.com, aol.com, myyahoo.com, and
> verizon.net as a group, since these domains a
I want to implement rate limiting based on the target server rather
than by recipient domain. Specifically, I want to rate limit email
sent to domains like yahoo.com, ymail.com, aol.com, myyahoo.com, and
verizon.net as a group, since these domains appears to be handled by
the same servers. This
On Wed, Oct 04, 2023 at 04:18:43PM +0200, Kevin Cousin via Postfix-users wrote:
> > We have a solution for that, and that is not slowing down message
> > arrivals or speeding up deliveries.
>
> Mails are arriving fast, they arrive quicly enough to fill the active
> queue.
SHOULD all these messa
Hi
> Can you answer one question: is mail arriving too fast, or are
>
> deliveries too slow? If the problem is the latter, then your queue
>
> may be full of MAILER-DAEMON messages.
>
> We have a solution for that, and that is not slowing down message
>
> arrivals or speeding up deliveries.
M
Wietse Venema via Postfix-users:
> Viktor Dukhovni via Postfix-users:
> > On Tue, Oct 03, 2023 at 06:29:08PM -0400, Wietse Venema via Postfix-users
> > wrote:
> >
> > > > My first wild guess is setting in_flow_delay to a higher value might
> > > > help. Note this may be completely inappropriate
Viktor Dukhovni via Postfix-users:
> On Tue, Oct 03, 2023 at 06:29:08PM -0400, Wietse Venema via Postfix-users
> wrote:
>
> > > My first wild guess is setting in_flow_delay to a higher value might
> > > help. Note this may be completely inappropriate for your specific
> > > application.
> > >
On Tue, Oct 03, 2023 at 06:29:08PM -0400, Wietse Venema via Postfix-users wrote:
> > My first wild guess is setting in_flow_delay to a higher value might
> > help. Note this may be completely inappropriate for your specific
> > application.
> > http://www.postfix.org/postconf.5.html#in_flow_del
Noel Jones via Postfix-users:
> My first wild guess is setting in_flow_delay to a higher value might
> help. Note this may be completely inappropriate for your specific
> application.
> http://www.postfix.org/postconf.5.html#in_flow_delay
That, and reducinig the number of smtpd processes if the
On 10/3/2023 2:11 PM, Kevin C via Postfix-users wrote:
Hi Matthew, Hi Wietse,
Our postfix servers are only MTAs who transfer mails from internal IT apps to
end users over Internet. We don't receive mails from Internet.
Sometimes, an abnormal activity can fill active queue unitl it's full, and i
Hi Matthew, Hi Wietse,
Our postfix servers are only MTAs who transfer mails from internal IT apps to
end users over Internet. We don't receive mails from Internet.
Sometimes, an abnormal activity can fill active queue unitl it's full, and it
slow down all mail delivery. We had some rules to s
I might had used the wrong terminology. I was mainly referencing delayed
email that occurs with Grey listing. Most of the delay email for me is
either Google or Yahoo.
Matthew
On 9/29/2023 7:40 PM, Wietse Venema via Postfix-users wrote:
Matthew McGehrin via Postfix-users:
Hi Kevin.
If the del
Matthew McGehrin via Postfix-users:
> Hi Kevin.
>
> If the delays are being caused by bounce message processing, you could
Then you should configre Postfix to block undeliverable mail.
- Don't accept mail for non-existent recipients.
- Don't forward SPAM to other systems.
Wietse
_
Hi Kevin.
If the delays are being caused by bounce message processing, you could
run a second instance dedicated to just processing delayed messages
using fallback_relay.
You can also make adjustments to the individual queues in master.cf, one
tweak I use is increasing the flush rate to 1800
Wietse Venema via Postfix-users:
> Kevin Cousin via Postfix-users:
> > Greetings List,
> >
> > We recently had an issue and the active queue was full and slowed
> > down all new mail delivery. Is it possible to rate limit the mail
> > flow to protect smtpd from a massive mail input ?
>
> By defa
Kevin Cousin via Postfix-users:
> Greetings List,
>
> We recently had an issue and the active queue was full and slowed
> down all new mail delivery. Is it possible to rate limit the mail
> flow to protect smtpd from a massive mail input ?
By default, the Postfix SMTP server enforces in_flow_del
Greetings List,
We recently had an issue and the active queue was full and slowed
down all new mail delivery. Is it possible to rate limit the mail
flow to protect smtpd from a massive mail input ?
Regards
Kevin
___
Postfix-users mailing list -- po
Dnia 22.08.2023 o godz. 18:27:40 Wietse Venema via Postfix-users pisze:
>
> Unfortunatey, the Postfix schedulerisn't smart enough to figure out
> that a domain is hosted at google. Even if the doain is not google,
> it may be hosted there and add to your rate limit. I'm not claiming
> that gmail
On Tue, Aug 22, 2023 at 03:41:43PM -0400, Alex via Postfix-users wrote:
> I'm hoping I could ask what is probably an FAQ but I haven't seen
> anything on it recently. I've already implemented some type of rate
> limiting for delivering to gmail, but it's apparently
Jaroslaw Rafa via Postfix-users:
> Dnia 22.08.2023 o godz. 15:41:43 Alex via Postfix-users pisze:
> > This mail server unfortunately has quite a few users who use ~/.forward to
> > forward mail through to their personal gmail account from their corporate
> > account.
> >
> > Aug 22 15:33:08 cipher
Dnia 22.08.2023 o godz. 15:41:43 Alex via Postfix-users pisze:
> This mail server unfortunately has quite a few users who use ~/.forward to
> forward mail through to their personal gmail account from their corporate
> account.
>
> Aug 22 15:33:08 cipher postfix-gmail/smtp[2551987]: 5EF9820E0E1E8:
Hi,
I'm hoping I could ask what is probably an FAQ but I haven't seen anything
on it recently. I've already implemented some type of rate limiting for
delivering to gmail, but it's apparently not working satisfactorily for
them. Notice it's already going through my thrott
On Mon, Mar 27, 2023 at 11:21:15AM +, Gino Ferguson via Postfix-users wrote:
> How can one set up outbound rate limiting for a certain mail service
> provider?
Postfix rate limiting is implemented in the queue manager, which does
not (and cannot without a major redesign) know the MX
Gino Ferguson via Postfix-users:
> Hi,
>
> How can one set up outbound rate limiting for a certain mail service
> provider?
Did you mean concurrency limit (number of parallal deliveries)
or rate limit (for example, number of deliveries per minute)?
> Can postfix &
Hi
Try postfwd for postfix
http://postfwd.org/ratelimits.html
W dniu 27.03.2023 o 13:21, Gino Ferguson via Postfix-users pisze:
Hi,
How can one set up outbound rate limiting for a certain mail service provider?
Can postfix 'recognise' that recipientdomainA, recipientd
On 2023-03-27 19:21, Gino Ferguson via Postfix-users wrote:
Hi,
How can one set up outbound rate limiting for a certain mail service
provider?
Can postfix 'recognise' that recipientdomainA, recipientdomainB and
recipientdomainC are hosted at the same mail servic
Hi,
How can one set up outbound rate limiting for a certain mail service provider?
Can postfix 'recognise' that recipientdomainA, recipientdomainB and
recipientdomainC are hosted at the same mail service provider
(bigmxprovider.com) so this limiting must be applied automatica
On 4/01/23 19:33, Hébergement Arbre Binaire wrote:
I just don't understand the process: if a local client uses sendmail to
enqueue an email, that client is not expecting much more than a zero or
non-zero response code. If the shim is set up to communicate using SMTP
and Postfix responds that i
On Wed, 4 Jan 2023 at 00:52, Hébergement Arbre Binaire
wrote:
>
> I really appreciate your (very) thorough answer. I'll use it to search for a
> solution or devise a homemade one.
>
> The problem I'm describing affects so many web hosts... I'm surprised that
> this security problem has not bee
Thanks, I'll check postfwd in details too and see what fits best to my use
case.
All the best,
François
H?bergement Arbre Binaire:
> >As far as I know, "msmtp" can be used >as a replacement for
> >/usr/sbin/sendmail to submit mail via >SMTP instead of writing it directly
> to
> >the queue
>
> That was a suggestion of Viktor too, but I did not investigated further
> after reading the outdated descrip
>As far as I know, "msmtp" can be used >as a replacement for
>/usr/sbin/sendmail to submit mail via >SMTP instead of writing it directly
to
>the queue
That was a suggestion of Viktor too, but I did not investigated further
after reading the outdated description of a piece of software that seemed
o
Dnia 3.01.2023 o godz. 19:20:30 Hébergement Arbre Binaire pisze:
>
> Aside from creating a "shim" of some sort to catch sendmail calls made by
> random malicious scripts and that uses SMTP to route mail to the local MTA,
> I don't see any solution. It's a bit above my paygrade since any and all
I just don't understand the process: if a local client uses sendmail to
enqueue an email, that client is not expecting much more than a zero or
non-zero response code. If the shim is set up to communicate using SMTP
and Postfix responds that it will not enqueue mail from localhost because
of "Too
On Wed, Jan 04, 2023 at 12:25:47AM -0500, Hébergement Arbre Binaire wrote:
> I don't know if this could be put to consideration by your dev team (or
> not, because of technical considerations above my knowledge), but a single
> door to a barn makes a more secure barn.
My "dev" team is just me, an
>The real "only" way to enqueue mail for local delivery via Postfix is
>postdrop(1), which is "setgid" to a group that can write to the
>"maildrop" queue. If you set "authorized_submit_users" to a restricted
>set of trusted system accounts, then all users would have to use your
>shim, a postdrop(1
On Tue, Jan 03, 2023 at 07:50:19PM -0500, Hébergement Arbre Binaire wrote:
> Maybe I should ask another question: is sendmail the ONLY way for a local
> script (be it any kind of script: PHP or otherwise) to queue a mail for
> delivery?
All that applications can portably expect to work for local
>Otherwise, the script can just send mail directly
As far as my experience goes, abusive scripts depend on the local MTA to
relay abusive mail. They would need to crack two hosts instead of a single
one to route bad mail.
Maybe I should ask another question: is sendmail the ONLY way for a local
On Tue, Jan 03, 2023 at 07:20:30PM -0500, Hébergement Arbre Binaire wrote:
> >If submission rate limits are required, use SMTP instead of the Postfix
> sendmail command.
>
> Aside from creating a "shim" of some sort to catch sendmail calls made by
> random malicious scripts and that uses SMTP to
On 1/3/23 19:20, Hébergement Arbre Binaire wrote:
>> If submission rate limits are required, use SMTP instead of the Postfix
> sendmail command.
>
> Aside from creating a "shim" of some sort to catch sendmail calls made by
> random malicious scripts and that uses SMTP to route mail to the local MT
>If submission rate limits are required, use SMTP instead of the Postfix
sendmail command.
Aside from creating a "shim" of some sort to catch sendmail calls made by
random malicious scripts and that uses SMTP to route mail to the local MTA,
I don't see any solution. It's a bit above my paygrade s
re required, use SMTP instead of the
Postfix sendmail command.
Then you can use rate limiting policies in postfwd and the like.
Wietse
d projects now.
The other way I was looking into was this conf:
smtp_destination_rate_delay = 2s
By checking the queue size at regular intervals it could be possible to
detect abuse, find the abusive source and at the same time limit the damage
an abusive script could do to a server reputation
On Tue, Jan 03, 2023 at 06:03:29PM -0500, Hébergement Arbre Binaire wrote:
> Local clients (bash scripts and PHP mailers in particular) are still not
> rate limited at all. How can I accomplish this?
The simple answer is that You can't, without replacing sendmail(1), with
something that submits
in maillog, I cannot find the "Too many
mails" error the client receives upon being rate limited. How can I
configure Postfix to leave a more recognizable error? Without a specific
message it will be difficult to fix abuse in an efficient way.
Background information: rate limitin
On 8/1/2018 12:43 PM, Durga Prasad Malyala wrote:
> Hello all,
> To overcome scam due to compromised accounts,Currently we are using a
> beautiful software https://github.com/MirLach/ratelimit-policyd
>
> However we have a few issues. Generally spammers dont put a lot of
> peple in cc or bcc. they
Hello all,
To overcome scam due to compromised accounts,Currently we are using a
beautiful software https://github.com/MirLach/ratelimit-policyd
However we have a few issues. Generally spammers dont put a lot of
peple in cc or bcc. they send individual mails to a lot of users. This
software counts
nch.com
Cc: postfix-users@postfix.org
Subject: Re: Rate-limiting access to postfix on the firewall, what are decent
numbers (depending on overall traffic)?
On 4 January 2017 at 08:53, wrote:
> Reread. I don't not block port 25.
>
> I assure you, OVH has been used for C&C by h
postfix.org; li...@lazygranch.com
> Subject: Re: Rate-limiting access to postfix on the firewall, what are decent
> numbers (depending on overall traffic)?
>
> On 4 January 2017 at 02:16, <
> li...@lazygranch.com> wrote:
>>
>> http://bgp.he.net/AS16276#_prefixes
>
Reread. I don't not block port 25.
I assure you, OVH has been used for C&C by hackers. Angler comes to mind.
Original Message
From: Dominic Raferd
Sent: Tuesday, January 3, 2017 11:42 PM
To: postfix-users@postfix.org; li...@lazygranch.com
Subject: Re: Rate-limiting access to postf
On 4 January 2017 at 02:16, <
li...@lazygranch.com> wrote:
>
> http://bgp.he.net/AS16276#_prefixes
> I'd switch to 587 and block everything OVH. Actually I do just that since OVH
> is on my Web Access blocking list, which I also use to block all mail ports
> other than 25.
>
> OVH VPS are often
From: John Fawcett
Sent: Tuesday, January 3, 2017 6:46 AM
To: postfix-users@postfix.org
Subject: Re: Rate-limiting access to postfix on the firewall, what are decent
numbers (depending on overall traffic)?
On 01/03/2017 01:37 PM, Gerben Wierda wrote:
> My postfix MTA has been under a lot of D
On 01/03/2017 01:37 PM, Gerben Wierda wrote:
> My postfix MTA has been under a lot of DOS-like attention. Such as a botnet
> sending many EHLO-requests, then password attempts:
> ...
> It does the first part from a multitude of machines.
>
> I want to stop this by setting a rat
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Gerben Wierda
Sent: Tuesday, January 3, 2017 7:37 AM
To: Postfix users
Subject: Rate-limiting access to postfix on the firewall, what are decent
numbers (depending on overall
t part from a multitude of machines.
>
> I want to stop this by setting a rate limiting rule in my firewall. I was
> wondering what rate to set if I want to limit access by the same IP. The
> first pattern, I could stop by rate-limiting to maximally 3 per second or 180
> per minute. T
setting a rate limiting rule in my firewall. I was
wondering what rate to set if I want to limit access by the same IP. The first
pattern, I could stop by rate-limiting to maximally 3 per second or 180 per
minute. That is already pretty high. What MTA is going to send me 180 per
minute and still be
y much for your answer. I understand.
> Apart from the MX dynamic information, is there a way within Postfix to
> specify that specific rate limiting toward that specific hostname/ip
> address ?
Rate limits are implemented by the scheduler. As mentioned in my
earlier reply, the scheduler doe
of course it sees too many sending at a time
> > from me.
> >
> > I know I could just use the transport map for all of these target domains
> > and defining rate limiting configuration for all of them, but I am not in
> > control of the target domain list, so it c
the transport map for all of these target domains
> and defining rate limiting configuration for all of them, but I am not in
> control of the target domain list, so it could change in the near future.
>
> Is there a way to implement a transport map for that specific target MTA
> in
defining rate limiting configuration for all of them, but I am not in
control of the target domain list, so it could change in the near future.
Is there a way to implement a transport map for that specific target MTA
instead of listing all the domains and periodically keeping that list
updated
On 10/18/2016 9:32 AM, Fazzina, Angelo wrote:
> Noel, I'm confused.
> What you say seems to contradict this:
>
> The default_destination_concurrency_limit parameter (default: 20) controls
> how many messages may be sent to the same destination simultaneously
> FROM : http://www.postfix.org/TUNING
Fazzina, Angelo:
> Noel, I'm confused.
> What you say seems to contradict this:
>
> The default_destination_concurrency_limit parameter (default: 20) controls
> how many messages may be sent to the same destination simultaneously
> FROM : http://www.postfix.org/TUNING_README.html
As documented t
-486-9075
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Noel Jones
Sent: Tuesday, October 18, 2016 9:50 AM
To: postfix-users@postfix.org
Subject: Re: Rate Limiting & 'destination_concurrency_limit'
On 10/18/20
On 10/18/2016 3:39 AM, David Byrne wrote:
> Hi all,
> We need a way to limit outbound mails to a specific domain to just 10 mails
> in 10minutes. The issue I’m having is that I can only get it to send 1 email
> every queue run, so 1 email every 10minutes. I can set the
> destionation_rate_delay
David Byrne:
> Hi all,
> We need a way to limit outbound mails to a specific domain to just
> 10 mails in 10minutes. The issue I?m having is that I can only get
> it to send 1 email every queue run, so 1 email every 10minutes. I
> can set the destionation_rate_delay to 1minute, and have 10 of
> the
Hi all,
We need a way to limit outbound mails to a specific domain to just 10 mails in
10minutes. The issue I’m having is that I can only get it to send 1 email every
queue run, so 1 email every 10minutes. I can set the destionation_rate_delay to
1minute, and have 10 of them send in 10minutes, b
> I'm wondering what to do in case of future attacks like this.
I'm using a fail2ban+ipsets to catch these quickly & ban them efficiently.
Works well. Simply use a regex like in those grep commands to match.
Make sure you test your matches -- using a combo or online regex tester &
fail2ban-re
Vincent Lefevre:
> [...]
> 130 [75.147.78.177]
> 366 [213.193.32.35]
> 492 [193.189.117.148]
> 100543 [108.245.138.130]
>
> So, this was due to a single IP address, which did more than 100,000
> connections within 15 hours!
fail2ban
Wietse
On 2016-04-09 18:51:00 -0400, Wietse Venema wrote:
> jaso...@mail-central.com:
> > conitinues on for a total of (in this case) 237 attempts in one
> > continuous string over a few minutes.
>
> All connections are blocked after 0.1 second, as the client fails
> both the DNSBL and the pregreet tests
Thanks, Curtis. We have taken all that in to consideration. I'll spare
you the long story, but we are testing somewhat specific things. :-) -c
If you are trying to simulate a very busy mailserver, then you should
be concerned about connections to it from multiple hosts per second
most sending
In message <5707263d.7000...@caseyconnor.org>
Casey Connor writes:
>
> Thank you -- will it accept decimal seconds?
>
> We are sending on the order of 50-200+ messages per second in this
> stress test, so the delay between messages could be smaller than .005
> seconds.
If you are trying to si
In message <1460213048.1937714.573722321.23756...@webmail.messagingengine.com>
jaso...@mail-central.com writes:
> With postscreen in place, bad bots arr getting fended off.
>
> Many give up and go away after a couple of tries.
>
> Some, these days mostly 'ymlf-pc' bots, are more persistent.
>
jaso...@mail-central.com:
> conitinues on for a total of (in this case) 237 attempts in one
> continuous string over a few minutes.
All connections are blocked after 0.1 second, as the client fails
both the DNSBL and the pregreet tests. At one connection per second,
this uses very few resources, s
I use a script which greps for repeated HANGUPS (and non-SNMP commands,
etc) and adds them to a postscreen access file (a separate blacklist
file chat can be re-compiled as and when). The black-list entry is
retracted after a day or so.
A second script looks for repeated black-list refusals and
With postscreen in place, bad bots arr getting fended off.
Many give up and go away after a couple of tries.
Some, these days mostly 'ymlf-pc' bots, are more persistent.
Eg, this one
Apr 8 04:17:20 mail01 postfix/postscreen[20412]: CONNECT from
[37.49.226.17]:52066 to [192.0.2.17]:25
> On Apr 7, 2016, at 11:57 PM, Casey Connor
> wrote:
>
> Please consider decimal-second rate limiting as a feature request. :-)
It is very unlikely to happen. To deliver much more than one message per
second, given typical message transaction latencies, delivery concurrency
is r
;> be delivered faster than it comes in (unless a backlog develops
>> and clears when downstream conditions improve).
>
> We don't have a tool to inject at a particular rate, but maybe we can
> find one or make one. I was hoping we could handle it in postfix, but it
> so
downstream conditions improve).
We don't have a tool to inject at a particular rate, but maybe we can
find one or make one. I was hoping we could handle it in postfix, but it
sounds like a no.
Please consider decimal-second rate limiting as a feature request. :-)
Thanks,
-c
> On Apr 7, 2016, at 11:32 PM, Casey Connor
> wrote:
>
> Thank you -- will it accept decimal seconds?
No.
> We are sending on the order of 50-200+ messages per second in this stress
> test, so the delay between messages could be smaller than .005 seconds.
Inject 50-200 messages per second i
Thank you -- will it accept decimal seconds?
We are sending on the order of 50-200+ messages per second in this
stress test, so the delay between messages could be smaller than .005
seconds.
On 04/07/2016 06:19 PM, Wietse Venema wrote:
See:
http://www.postfix.org/postconf.5.html#default_tran
See:
http://www.postfix.org/postconf.5.html#default_transport_rate_delay
http://www.postfix.org/postconf.5.html#default_destination_rate_delay
The names are similar but things work differently.
Wietse
Hello -- we're sending from a postfix instance as part of our
stress-testing infrastructure.
We need to limit the rate of outbound messages per second: sometimes to
a particular slow rate, sometimes to a medium speed, sometimes "as fast
as possible".
I found no easy way to do that; have I mi
Am 21.09.2015 um 08:25 schrieb Kianoosh Kashefi:
I use Postfix with Postfwd as policy service. and I want to limit all
outgoing messages with exceptions for several SASL users with HOLD
verdict. I'm new to postfwd so I need configuration example for
rate-limiting with HOLD verdict
> > I'm new to postfwd so I need configuration example for rate-limiting with
> > HOLD verdict (for instance limit all users outgoing messages to 10 messages
> > per minute and HOLD messages exceeding that limit) also I need the same
> > configuration to apply only t
On Mon, Sep 21, 2015 at 07:25:53AM +0100, Kianoosh Kashefi wrote:
> I use Postfix with Postfwd as policy service. and I want to limit all
> outgoing messages with exceptions for several SASL users with HOLD verdict.
> I'm new to postfwd so I need configuration example for rate
wd so I need configuration example for
> > rate-limiting with HOLD verdict (for instance limit all users outgoing
> > messages to 10 messages per minute and HOLD messages exceeding that
> > limit) also I need the same configuration to apply only to certain SASL
> > users ag
On 09/21/2015 06:25 PM, Kianoosh Kashefi wrote:
> I use Postfix with Postfwd as policy service. and I want to limit all
> outgoing messages with exceptions for several SASL users with HOLD
> verdict. I'm new to postfwd so I need configuration example for
> rate-limiting with H
I use Postfix with Postfwd as policy service. and I want to limit all outgoing
messages with exceptions for several SASL users with HOLD verdict. I'm new to
postfwd so I need configuration example for rate-limiting with HOLD verdict
(for instance limit all users outgoing messages
On 07/03/2015 07:20 PM, Alex Regan wrote:
We are not the originators of these messages. The users on this system
have a .forward file that's forwarding these messages through to gmail.
Then if you or your customers didn't originate them, then they should
not have been sent from your server. I
Hi,
How do people generally deal with these?
They, and the some of the network around them, are promoted to my
packet filter for a few months. If I see nothing in 3 months or so,
they get unblocked. To easy the load on my packet filter, not on the
spammers.
These are messages being forwarded
On 07/03/2015 04:07 PM, Marius Gologan wrote:
You forward messages repeatedly, flooding this mailing list too.
I received a Wietse automated message saying they were rejected for
various reasons pertaining to words in the body and was told to retry.
Google it doesn't think differently, bu
On Jul 3, 2015, at 2:06 PM, Alex Regan wrote:
> How do people generally deal with these?
They, and the some of the network around them, are promoted to my packet filter
for a few months. If I see nothing in 3 months or so, they get unblocked. To
easy the load on my packet filter, not on the s
uly 3, 2015 11:06 PM
To: Marius Gologan; 'postfix users list'
Subject: Re: Outbound rate limiting
On 07/03/2015 03:23 PM, Marius Gologan wrote:
> As per your errors, you send Unsolicited Messages. If that is the
> case then is not related to sending rates, but to spam complaints
&g
s...@postfix.org] On Behalf Of Alex Sent:
Friday, July 3, 2015 8:05 PM To: postfix users list Subject: Outbound
rate limiting
Hi,
Some time ago I had asked a question about rate limiting email to
sites like gmail and yahoo using transport maps and
destination_concurrency_limit, but I still can't
n - is built in time based on quality (engagement), not quantity.
Is not a technical tweak.
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Alex
Sent: Friday, July 3, 2015 8:05 PM
To: postfix users list
Subject: Outbound rate
Hi,
Some time ago I had asked a question about rate limiting email to
sites like gmail and yahoo using transport maps and
destination_concurrency_limit, but I still can't get it right. I'm
trying to throttle traffic to avoid the following restrictions from
sites like google:
Jul
Hi,
If it's possible to throttle based on MX record for a domain, I'd
really appreciate your help.
Hi, Alex. I don't do it that way, but that sounds simpler than the way I
do it! Interested to see what others come up with.
I didn't receive any other responses. Is that because it's not
cket shaping with tc/htb on fedora. Can you share how you're
doing it with iptables? Is this using fwmark?
I shuttle incoming packets of the different protocols to individual
chains, then use the 'recent' module to do rate limiting on the that
protocol.
I'm using it for outb
to individual chains,
then use the 'recent' module to do rate limiting on the that protocol.
It works pretty well. Sometimes somebody gets a little 'trigger happy' checking
email or something. But if you like them, their IP (or their ISP) can just be
whitelisted.
If you&#x
On Thu, Jun 4, 2015 at 4:02 PM, Alex Regan wrote:
> If it's possible to throttle based on MX record for a domain, I'd really
> appreciate your help.
>
Hi, Alex. I don't do it that way, but that sounds simpler than the way I do
it! Interested to see what others come up with.
> If you have a lis
Alex Regan:
> Hi,
>
> I posted the message below a few days ago, and haven't seen any
> responses. Were my questions too confusing or did I otherwise not
> provide the info necessary to help with my problem?
This is a frequent topic on this mailing list.
Wietse
1 - 100 of 189 matches
Mail list logo
