Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
Hi Rob This works like a charm, blocking a lot of: bounces+8465718 atm. Thank you for your excellent plugin! Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G-Leiter Commerce Kunden __ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 PrattelnFax +41 61 826 93 01 Schweiz Web http://www.imp.ch __ ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
On 2020-08-22 at 12:46 -0400, Chris via mailop wrote: (...) > This is, I think, the inject-to-google point: > > > - IP address in X-Received header is different (first message: > > 2002:a0c:f9cd:: ; second message: 2002:a2e:b4e1::) > > - X-Google-DKIM-Signature, X-Gm-Message-State and X-Google-Smtp-Source > > headers are different > > > > Looks like Google duplicated this message somehow > Right at the injection point. Which is odd if Google has only one copy > in the sent box. Not really. Do remember that gmail heavily deduplicates mail. Even if you received an email twice (such as received directly + through a mailing list), it will only show one in the mailbox. In this case we are probably seeing the same thing, although in the Sent folder. So if Al sent the email through SMTP (as may be the case by the presence of X-Google-Smtp-Source), and it timed out and was resent, but it was actually accepted by gmail, it would be a classical email duplication. On the other hand, if he was using gmail webmail UI (the @mail.gmail.com at the Message-ID does not look like a local client), this might have happened between two gmail servers, making it much more interesting. Best regards ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
On 2020-08-22 10:08, Jaroslaw Rafa via mailop wrote: Dnia 21.08.2020 o godz. 23:00:23 Chris via mailop pisze: Belay that, it appears to have been received by google twice - different timestamps on the X-Received. I compared the two messages I received. Right, this is the first thing I noticed: - timestamp is different - sending host within Google is different (first message: 2607:f8b0:4864:20::f2a, helo=mail-qv1-xf2a.google.com; second message: 2a00:1450:4864:20::229, helo=mail-lj1-x229.google.com) - SMTP id indicated by Received and X-Received headers within Google is different This is, I think, the inject-to-google point: - IP address in X-Received header is different (first message: 2002:a0c:f9cd:: ; second message: 2002:a2e:b4e1::) - X-Google-DKIM-Signature, X-Gm-Message-State and X-Google-Smtp-Source headers are different Looks like Google duplicated this message somehow Right at the injection point. Which is odd if Google has only one copy in the sent box. ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
Dnia 21.08.2020 o godz. 23:00:23 Chris via mailop pisze: > Belay that, it appears to have been received by google twice - > different timestamps on the X-Received. I compared the two messages I received. - timestamp is different - sending host within Google is different (first message: 2607:f8b0:4864:20::f2a, helo=mail-qv1-xf2a.google.com; second message: 2a00:1450:4864:20::229, helo=mail-lj1-x229.google.com) - SMTP id indicated by Received and X-Received headers within Google is different - IP address in X-Received header is different (first message: 2002:a0c:f9cd:: ; second message: 2002:a2e:b4e1::) - X-Google-DKIM-Signature, X-Gm-Message-State and X-Google-Smtp-Source headers are different Looks like Google duplicated this message somehow. -- Regards, Jaroslaw Rafa r...@rafa.eu.org -- "In a million years, when kids go to school, they're gonna know: once there was a Hushpuppy, and she lived with her daddy in the Bathtub." ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
I've only got one copy in sent email here. Al On Fri, Aug 21, 2020 at 10:07 PM Chris via mailop wrote: > > Belay that, it appears to have been received by google twice - different > timestamps on the X-Received. > > On 2020-08-21 22:03, Michael Rathbun via mailop wrote: > > On Sat, 22 Aug 2020 00:52:10 +0200, Bjoern Franke via mailop > > wrote: > > > >> Did you send this mail two times or is something wrong again with the > >> listserver? > > > > The message ID strings are identical. > > > > mdr > > > > > > ___ > > mailop mailing list > > mailop@mailop.org > > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > > > > > ___ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- Al Iverson // Wombatmail // Chicago Song a day! https://www.wombatmail.com Deliverability! https://spamresource.com And DNS Tools too! https://xnnd.com ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
Belay that, it appears to have been received by google twice - different timestamps on the X-Received. On 2020-08-21 22:03, Michael Rathbun via mailop wrote: On Sat, 22 Aug 2020 00:52:10 +0200, Bjoern Franke via mailop wrote: Did you send this mail two times or is something wrong again with the listserver? The message ID strings are identical. mdr ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
On Sat, 22 Aug 2020 00:52:10 +0200, Bjoern Franke via mailop wrote: >Did you send this mail two times or is something wrong again with the >listserver? The message ID strings are identical. mdr ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
Am 21.08.20 um 23:33 schrieb Al Iverson via mailop: This is interesting. At first I thought Rob's intent was to just facilitate the blocking of that one ESP fully, but I see that he is trying hard here to avoid collateral damage and that's admirable. Good luck with this, Rob! Did you send this mail two times or is something wrong again with the listserver? Regards Bjoern ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
This is interesting. At first I thought Rob's intent was to just facilitate the blocking of that one ESP fully, but I see that he is trying hard here to avoid collateral damage and that's admirable. Good luck with this, Rob! Cheers, Al Iverson On Fri, Aug 21, 2020 at 2:40 PM Rob McEwen via mailop wrote: > > ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for > Sendgrid-spams! > > ...a collection of a new TYPE of DNSBL, with the FIRST of these having a > focus on Sendgrid-sent spams. AND - there is a FREE version of this - that > can be used NOW! (well... might need a SpamAssassin rule or two! Your help > appreciated!): > > INFO AND INSTRUCTIONS HERE: > > https://www.invaluement.com/serviceproviderdnsbl/ > > This provides a way to surgically block Sendgrid's WORST spammers, yet > without the massive collateral damage that would happen if blocking Sendgrid > domains and IP addresses. But we're NOT stopping at the phishes and viruses - > and we're not finished! There will be some well-deserved economic pain, that > puts the recipients' best interests at heart. Therefore, flagrant "cold > email" spamming to recipients who don't even know the sender - is also being > targeted - first with the absolute worst - and then progressing to other > offenders as we make adjustments in the coming weeks. > > -- > Rob McEwen > https://www.invaluement.com > > > ___ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- Al Iverson // Wombatmail // Chicago Song a day! https://www.wombatmail.com Deliverability! https://spamresource.com And DNS Tools too! https://xnnd.com ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
[mailop] ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams!
ANNOUNCEMENT: The NEW invaluement "Service Provider DNSBLs" - 1st one for Sendgrid-spams! ...a collection of a new TYPE of DNSBL, with the FIRST of these having a focus on Sendgrid-sent spams. AND - there is a FREE version of this - that can be used NOW! (/well... might need a SpamAssassin rule or two! Your help appreciated!)/: INFO AND INSTRUCTIONS HERE: https://www.invaluement.com/serviceproviderdnsbl/ This provides a way to surgically block Sendgrid's WORST spammers, yet without the massive collateral damage that would happen if blocking Sendgrid domains and IP addresses. But we're NOT stopping at the phishes and viruses - and we're not finished! There will be some well-deserved economic pain, that puts the recipients' best interests at heart. Therefore, flagrant "cold email" spamming to recipients who don't even know the sender - is also being targeted - first with the absolute worst - and then progressing to other offenders as we make adjustments in the coming weeks. -- Rob McEwen https://www.invaluement.com ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
