Am 23.11.2020 um 17:29 schrieb Philip Paeps via mailop:
This is all empirical guesswork.
This is my personal experience with deliverability to Google:
- Please read the M³AAWG's "Email Authentication Recommended Best
Practices" very very carefully
I host 200+ servers at Linode, most of them are email/web server combinations
hosted in European data centres.
Interestingly, I have the exact opposite experience, google accepts all mail
without a problem. But I receive lots of spam from them. See attached
screenshot as an example.
My
On 23.11.20 17:29, Philip Paeps via mailop wrote:
On 2020-11-21 22:02:19 (+0800), Luke via mailop wrote:
The system is clearly better adapted to dealing with large, steady,
volumes of email from bulk senders. Small organisations or individuals
running their own email seem to be an
On 2020-11-21 22:02:19 (+0800), Luke via mailop wrote:
Why hasn't anyone mentioned the mythic-beasts.com stuff being
potentially
problematic? The host name, A record, mx record, ptr record are all
mythic-beast.com. If Google doesn't like them, all this stuff you're
doing
is a moot point.
On Mon, 2020-11-23 at 10:15 +0100, Ewald Kessler | Webpower wrote:
> Hi Jim,
>
> There's one 'e' too many
>
> > googleemail.com smtp-v4:
Heh, Thanks. I've had that like that for close to a decade now and
never realized that.
-Jim P.
___
Hi Jim,
There's one 'e' too many
googleemail.com smtp-v4:
>
Kind regards,
Ewald Kessler
--
Deliverability & Abuse Management, www.webpower-group.com
ewald.kess...@webpower.nl
t: +31 342 423 262
li: www.linkedin.com/in/ewaldkessler
___
mailop
Hi Paul,
I have the same problem for years. Even more, I get dmarc messages from
google that everything is pass but the mails are delivered to spam box.
I resigned. There is nothing, one can do to get mails delivered not to
spam. Maybe you have to bribe google or such. I don't know.
When I send
On 2020-11-21 at 14:31 +, Stuart Henderson via mailop wrote:
> On 2020/11/21 13:59, Thomas Walter via mailop wrote:
> > On 21.11.20 12:54, Jaroslaw Rafa via mailop wrote:
> > > You can configure your MTA to disable IPv6 only for delivery to Google -
> > > at
> > > least with Postfix it should
Why hasn't anyone mentioned the mythic-beasts.com stuff being potentially
problematic? The host name, A record, mx record, ptr record are all
mythic-beast.com. If Google doesn't like them, all this stuff you're doing
is a moot point.
On Sat, Nov 21, 2020, 6:49 AM Jim Popovitch via mailop
wrote:
On Sat, Nov 21, 2020 at 08:35:26AM -0500, Jim Popovitch via mailop wrote:
> > We don't know all domains that sue Google MXs, we don't know all MXs
> > Google uses and they might change. Do we know Google's IPv6 addresses?
> > Do those change?
>
> It's done by destination domain, not IP address.
On 2020/11/21 13:59, Thomas Walter via mailop wrote:
> Hello,
>
> On 21.11.20 12:54, Jaroslaw Rafa via mailop wrote:
> > You can configure your MTA to disable IPv6 only for delivery to Google - at
> > least with Postfix it should be possible.
>
> how would one do that?
Dnia 21.11.2020 o godz. 13:59:48 Thomas Walter via mailop pisze:
>
> how would one do that?
>
> We don't know all domains that sue Google MXs, we don't know all MXs
> Google uses and they might change. Do we know Google's IPv6 addresses?
> Do those change?
If I remeber correctly, this has been
On Sat, 2020-11-21 at 13:59 +0100, Thomas Walter via mailop wrote:
> Hello,
>
> On 21.11.20 12:54, Jaroslaw Rafa via mailop wrote:
> > You can configure your MTA to disable IPv6 only for delivery to Google - at
> > least with Postfix it should be possible.
>
> how would one do that?
With a
Hello,
On 21.11.20 12:54, Jaroslaw Rafa via mailop wrote:
> You can configure your MTA to disable IPv6 only for delivery to Google - at
> least with Postfix it should be possible.
how would one do that?
We don't know all domains that sue Google MXs, we don't know all MXs
Google uses and they
Dnia 20.11.2020 o godz. 17:44:21 Paul Waring via mailop pisze:
>
> That is my final option if all else fails. I don't really want to
> disable IPv6 but if it's a trade-off between v6 and Google the latter
> will win.
You can configure your MTA to disable IPv6 only for delivery to Google - at
Hi Paul, I've migrated a couple of mail servers over to hosts on mythic
beasts in the last few months. Both have been working fine with gmail
address delivery.
I have been using the Sympl software scripts and Mailman on v4 an
v6. I've used existing domains that have been registered and used for
On Thu, Nov 19, 2020 at 01:58:38PM +, Stuart Henderson via mailop wrote:
> If you're sending into them over v6 I would disable that too,
> most of the common open source MTAs have a feature to prevent sending
> over v6 exactly because of gmail.
That is my final option if all else fails. I
On Thu, 19 Nov 2020 at 12:30, Paul Waring via mailop
wrote:
> On Thu, Nov 19, 2020 at 11:37:35AM +, Rob Kendrick via mailop wrote:
> > On Thu, Nov 19, 2020 at 11:21:19AM +, Paul Waring via mailop wrote:
> > > Before I change any more settings, I was wondering if there was a time
> > >
On Thu, November 19, 2020 09:47, Al Iverson via mailop wrote:
> Test forcing your MTA to send to Gmail over IPv4 instead of IPv6.
> Gmail's filtering is much more harsh on IPv6. This has actually bit me
> before in the past.
!00% agree. Easy to do with Postfix and probably other MTAs.
John Capo
(Sorry for double reply...)
On Thu, 19 Nov 2020 at 13:29, Chris Woods <
christopherwoods+list-mai...@gmail.com> wrote:
> Correct the PTR, it's currently "romana.vs.mythic-beasts.com".
>>
>
Unless it's out of preference you're leaving it like that - I do similarly
with a domain distinct from
On Thu, 19 Nov 2020 at 13:58, Paul Waring wrote:
> No, they say:
>
> SPF:PASS with IP 2a00:1098:82:b3:0:0:0:1
> DKIM: 'PASS' with domain xk7.net
> DMARC: 'PASS'
>
> There is no warning about no authentication (and there shouldn't be).
>
> > My SPFs tend to be slightly more verbose,
Test forcing your MTA to send to Gmail over IPv4 instead of IPv6.
Gmail's filtering is much more harsh on IPv6. This has actually bit me
before in the past.
Cheers,
Al Iverson
On Thu, Nov 19, 2020 at 8:11 AM Stuart Henderson via mailop
wrote:
>
> On 2020/11/19 13:47, Paul Waring via mailop
On 2020/11/19 13:47, Paul Waring via mailop wrote:
> On Thu, Nov 19, 2020 at 01:29:48PM +, Chris Woods wrote:
> > I dropped the TTL on the MX, SPF, DKIM and DMARC records to 300 about 36
> > hours before starting the migration, and published the new DKIM key as
> > well. I left the
On Thu, Nov 19, 2020 at 01:47:57PM +, Chris Woods wrote:
> On Thu, 19 Nov 2020 at 13:29, Chris Woods <
> christopherwoods+list-mai...@gmail.com> wrote:
>
> Correct the PTR, it's currently "romana.vs.mythic-beasts.com".
>
>
> Unless it's out of preference you're leaving it like that
On Thu, Nov 19, 2020 at 01:29:48PM +, Chris Woods wrote:
> I dropped the TTL on the MX, SPF, DKIM and DMARC records to 300 about 36
> hours before starting the migration, and published the new DKIM key as
> well. I left the records at 300 for about 72 hours after the migration
>
On Thu, Nov 19, 2020 at 11:37:35AM +, Rob Kendrick via mailop wrote:
> On Thu, Nov 19, 2020 at 11:21:19AM +, Paul Waring via mailop wrote:
> > Before I change any more settings, I was wondering if there was a time
> > period during which Google treats a new server that it hasn't seen
> >
On Thu, Nov 19, 2020 at 11:21:19AM +, Paul Waring via mailop wrote:
> Before I change any more settings, I was wondering if there was a time
> period during which Google treats a new server that it hasn't seen
> before as a spam source? If this is something that will go away after a
> few more
In the last week or so, I migrated my xk7.net email from one self-hosted
server to another. Both servers were setup in a similar way and adhered
to all the email best practice guidelines I could find (DKIM, SPF and
DMARC all pass, the server isn't on any public blocklists, and there are
no mailing
28 matches
Mail list logo
