Dnia 30.12.2023 o godz. 22:58:25 Simon Wilson via mailop pisze:
>
> The error message from Google is specifically:
>
> 421-4.7.28 Gmail has detected an unusual rate of unsolicited mail
> originating from your SPF domain [howiesue.net 35]. To protect our
> users from spam, mail sent from
Dnia 30.12.2023 o godz. 15:57:45 Richard Rognlie via mailop pisze:
> I'm not seeing deferrals but some of my users are reporting that they're
> not seeing emails coming from my play by email service. I've double
> checked the logs and gmail is accepting the messages. So anything
> happening to
I'm not seeing deferrals but some of my users are reporting that they're
not seeing emails coming from my play by email service. I've double
checked the logs and gmail is accepting the messages. So anything
happening to user mail is under the covers on the gmail side.
Richard
On Sat, Dec 30,
.
From: mailop on behalf of Randolf Richardson,
Postmaster via mailop
Sent: Saturday, December 30, 2023 12:48 PM
To: mailop
Subject: Re: [mailop] Gmail now deferring email which meets their published reqs
Iron Wolf Technology EmployeeShield
Warning: The sender
I've added a gmail.com-specific transport, with a recipient_limit set to 2 (so
it does not become per-recipient instead of per-domain), a concurrency limit of
1 and a 10s rate delay. For the amount of email we send this should not be
problematic. I'll see if we can then build up a better rep
On Sat, 2023-12-30 at 12:48 -0800, Randolf Richardson, Postmaster via
mailop wrote:
> If that's what the problem is, then that can easily be set with the
> following Postfix setting without the need for customization scripts:
>
> default_destination_recipient_limit = 1
>
>
If that's what the problem is, then that can easily be set with the
following Postfix setting without the need for customization scripts:
default_destination_recipient_limit = 1
Documentation for this setting is available at:
I have nearly the exact same setup and usage you do. I got the same deferral
when sending an email to <20 friends, of which about 15 were on Gmail. Exactly
the same results as you got.
Fortunately, I found I could schedule one recipient at a time (using opensmtpd)
and each message went
Thanks all. I'll answer comments here in one email.
I use a single mail host (mail.simonandkate.net) as MX for a range of family
domains on a fixed/business IP address through a high quality ISP (not a
variable IP, not in a dial-up block). I've had the same IP address for about 7
years. It has
I've seen problems like this because of ISP listing large net locks as "dialup"
and not supposed to send email directly.
Check spamhaus' PBL:
https://www.spamhaus.org/pbl/
Best regards
El 30 de diciembre de 2023 7:40:59 CET, Simon Wilson via mailop
escribió:
>I know, I'm not alone in
It's definitely worth it to run your own eMail system (in my
opinion). I think people should be able to do this if they want to,
although one of the challenges that sometimes arises is which IP
netblocks their eMail servers are in.
If your server is operated at home, you may
On Sat, Dec 30, 2023 at 9:52 AM Simon Wilson via mailop
wrote:
> I know, I'm not alone in this... :(
>
> I like to think that it's still feasible to run one's own email. I have
> for many years, and currently manage about a dozen email domains for family
> and friends. Most of the time all good.
I know, I'm not alone in this... :(
I like to think that it's still feasible to run one's own email. I have for
many years, and currently manage about a dozen email domains for family and
friends. Most of the time all good.
Then today my dad says to me "Why am I getting these bounce
13 matches
Mail list logo
