Well I have been speaking to 2 different vendors on this so hopefully they can
get this straightened out. It sucks having no control and having to wait on
vendors, who where supposed to have already done this.
From: mailop On Behalf Of Mark Alley via mailop
Sent: Tuesday, June 20, 2023 1:05 PM
Interesting find, thanks!
On Tue, Jun 20, 2023 at 10:35 AM Mark Alley via mailop
wrote:
> Looks specific to several of their NS' in the "u06" subdomain. Everything
> returned from the "r06" servers resolves correctly.
>
> a.u06.twtrdns.net
>
> b.u06.twtrdns.net
>
> c.u06.twtrdns.net
>
>
It appears that Klaus Ethgen via mailop said:
>Well, it is for a reason. Microsoft is one of the most prominent spam
>sender. I don't want that they try to deliver mar...@ethgen.ch or
>k...@ethgen.ch, they do not exist as well as all that other spammers.
Well, yeah, they send me almost as much
On 6/20/2023 12:20 PM, Benny Pedersen via mailop wrote:
Mark Alley via mailop skrev den 2023-06-20 19:05:
You'll need to add the DKIM selector (and key) Sophos generated for
you to your external DNS provider so that other receivers can resolve
the key, which enables them to validate messages
Mark Alley via mailop skrev den 2023-06-20 19:05:
You'll need to add the DKIM selector (and key) Sophos generated for
you to your external DNS provider so that other receivers can resolve
the key, which enables them to validate messages signed by your email
filter.
if sophos like to change
You'll need to add the DKIM selector (and key) Sophos generated for you
to your external DNS provider so that other receivers can resolve the
key, which enables them to validate messages signed by your email filter.
- Mark Alley
On 6/20/2023 11:53 AM, Salvatore Jr Walter P via mailop wrote:
OK, we are still having issues with this.
We are using Sophos as an email gateway.
They generated a DKIM record and are telling us we need to send that to our
domain registrar to add it to our DNS records?
Is this correct? I understood DKIM was server side only?
From: mailop On Behalf Of
Looks specific to several of their NS' in the "u06" subdomain.
Everything returned from the "r06" servers resolves correctly.
a.u06.twtrdns.net
b.u06.twtrdns.net
c.u06.twtrdns.net
d.u06.twtrdns.net
On 6/20/2023 11:17 AM, Tom Bartel via mailop wrote:
Twitter seems to have copy/pasted quoted
Twitter seems to have copy/pasted quoted string into "some" of the DNS
servers such that were logging copious errors. Anyone else seeing this?
Bad record:
dig dkim-201406._domainkey.twitter.com txt
; <<>> DiG 9.10.6 <<>> dkim-201406._domainkey.twitter.com txt
;; global options: +cmd
;; Got
It appears that Mike Hillyer via mailop said:
>There is nothing broken about it, any large-scale sending environment has
>pools of IP addresses for deliveries, and when a message comes
>out of the delayed queue it is typically loaded back into the pool, where it
>is randomly assigned to an IP
Jay Hennigan via mailop skrev den 2023-06-20 17:46:
On 6/19/23 13:55, Michael Wise via mailop wrote:
If you're using GreyListing, know that a given email will not be
coming from the same IP address twice.
The outgoing IP address is randomized for ... reasons.
Because if you reuse the same
On 6/19/23 13:55, Michael Wise via mailop wrote:
If you're using GreyListing, know that a given email will not be coming
from the same IP address twice.
The outgoing IP address is randomized for ... reasons.
Because if you reuse the same IP address, your legs will sink through
the snow past
On Tue, 20 Jun 2023 10:26:22 -0400, Bill Cole via mailop
wrote:
>> That is absolutely ignorant to tell the people that you do mail in a
>> broken way and tell them it is for a reason, you don't want to tell.
>
>Sharing an outbound queue amongst many different machines is not
>"broken" in any
There is nothing broken about it, any large-scale sending environment has pools
of IP addresses for deliveries, and when a message comes out of the delayed
queue it is typically loaded back into the pool, where it is randomly assigned
to an IP for its delivery attempt.
The only time you should
Thanks everyone. This has both clarified the question and answered it
(them).
Mike: Yes, 'host' is the term I should have used.
Denny: That very well might be what the mailer was referring to. I'll read
up on it before answering them
John
On Mon, Jun 19, 2023 at 8:46 AM Denny Watson via
On 2023-06-20 at 02:45:04 UTC-0400 (Tue, 20 Jun 2023 07:45:04 +0100)
Klaus Ethgen via mailop
is rumored to have said:
Am Mo den 19. Jun 2023 um 21:55 schrieb Michael Wise via mailop:
If you're using GreyListing, know that a given email will not be
coming from the same IP address twice.
The
Hi Mailop community,
You may have noticed that libero and virgilio suffered an incident last week
that have raised bounces and latency when trying to deliver emails at their
domains.
The situation is now back to normal, you can send normally.
Mathieu on behalf of the Italiaonline team
Am Di den 20. Jun 2023 um 3:21 schrieb Ángel via mailop:
> I blame them by using a big amount of IPs to deliver mails even for
> > the same mail and for giving a host for malicious hosts that try to
> > get spam out. I blame them also for doing connections that are
> > absolute not needed and a
Am Mo den 19. Jun 2023 um 21:55 schrieb Michael Wise via mailop:
> If you're using GreyListing, know that a given email will not be coming from
> the same IP address twice.
>
> The outgoing IP address is randomized for ... reasons.
I substitute "no".
That is absolutely ignorant to tell the
19 matches
Mail list logo
