I normally don't handle the office infrastructure and wasn't even aware
of this until this thing happened. We disabled all external forwards
and only allow pop3 fetch now if somebody wants or needs to use his own
mailbox. Thx for the advice.
On 3 Jun 2016 17:14:46 -
"John Levine"
Thx, the problem was solved on friday evening.
On Fri, 3 Jun 2016 11:50:51 -0700
Brandon Long via mailop wrote:
> This throttle seems excessive, even though it's only temporary. I've
> filed a bug against our spam team to take a look.
>
> Brandon
>
> On Fri, Jun 3, 2016 at
This throttle seems excessive, even though it's only temporary. I've filed
a bug against our spam team to take a look.
Brandon
On Fri, Jun 3, 2016 at 4:30 AM, wrote:
> Hi,
>
> I'm currently seeing only this error
>
> 421-4.7.0 Our system has detected an unusual rate
>relay setting for an external user who is hosting his mail on Google
>apps and besides simple spam filtering we relayed everything.
You don't want to do that. The approach I've found that works least
badly is to do stringent spam filtering (spamassassin with a threshold
of about 4), forward the
Hi,
I'm currently seeing only this error
421-4.7.0 Our system has detected an unusual rate of unsolicited mail
originating from your IP address. To protect our users from spam, mail
sent from your IP address has been temporarily rate limited. Please
visit