Re: [mailop] Spamhaus SBL listing fonts.googleapis.com

2024-02-07 Thread Andreas Schamanek via mailop


On Wed, 7 Feb 2024, at 08:32, Lichtinger, Bernhard via mailop wrote:

The IP addresses for "fonts.googleapis.com" are: 142.250.217.106 
2607:f8b0:400a:800::200a


The IPs of "fonts.googleapis.com" got listed on SBL because these 
IPs are also used to serve "firebasestorage.googleapis.com". Last 
time i checked the IPs with https://check.spamhaus.org/ it told me 
the listing was because of malware hosted on some 
"firebasestorage.googleapis.com" URLs.


Thanks for pointing this out. Already yesterday I came to the 
conclusion that the whole thing is essentially related to how the 
Spamhaus' DQS plugin for SpamAssassin operates. My bug report, though, 
was quickly closed saying it was a "a listing issue". Understandably, 
such issues are not disputed in the dqs plugin issue tracker.


In the meantime, your reply, Bernhard, helped me understand better 
what's going on. So, I added a comment, also crediting you, 
re-iterating that the core problem is not that (presumably not all 
but) some IPs are SBL listed:


https://github.com/spamhaus/spamassassin-dqs/issues/68#issuecomment-1932189548

--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Spamhaus SBL listing fonts.googleapis.com

2024-02-06 Thread Andreas Schamanek via mailop


On Tue, 6 Feb 2024, at 15:24, John Levine via mailop wrote:

On January 25 I was alerted to false positives due to Spamhaus SBL 
listing IP addresses of fonts.googleapis.com.


Are those IPs supposed to send mail?  If not, why would an SBL 
listing, even a mistaken one, matter?


Thanks, that's the aspect my foggy brain missed. It only matters for 
those who check URIs, especially if found in the body, or more 
precisely the IPs of the hostnames of these URIs.


That's what their SpamAssassin Plugin for DQS does, cf. 
https://github.com/spamhaus/spamassassin-dqs


Rules URIBL_SBL_A and SH_BODYURI_REVERSE_SBL cause a very high rate of 
FPs (with default settings). The descriptions are


  Contains URL's A record listed in the Spamhaus SBL blocklist
  [URIs: fonts.googleapis.com]

  The corresponding A record of an URI contained in the body is
  listed in SBL [142.250.74.202]

So, I still got questions :) like why did these IPs end up on SBL in 
the first place, and why does Spamhaus check against them?


--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Spamhaus SBL listing fonts.googleapis.com

2024-02-06 Thread Andreas Schamanek via mailop


Hi mailops,

Thought some might be interested, though those affected sure already 
know:


On January 25 I was alerted to false positives due to Spamhaus SBL 
listing IP addresses of fonts.googleapis.com. According to our spam 
filter stats this, as expected, did not last long. But it seems to 
have recurred early February 3, and the listings persist until today.


I tried to contact Spamhaus via their customers contact form but 
haven't received any reply yet (also no automatic one).


So, maybe somebody reading this can actually do something about it.
Thanks in advance,

--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] verifier.port25.com

2023-05-23 Thread Andreas Schamanek via mailop


On Tue, 23 May 2023, at 16:10, Jim Popovitch via mailop wrote:


Lots of good responses for alternatives to verifier.port25.com, but
do any of them support aliased feedback address whereby you could
send an email to check-auth-lhs=domain@verifier.port25.com and
the response would be returned to the aliased address not the sender?


I feel like it took me much longer than it should to realize why I 
would want such a feature. Now that I got it, thank you very much, 
this is really helpful!


--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Corrupt plain text email

2021-09-03 Thread Andreas Schamanek via mailop


On Fri, 3 Sep 2021, at 13:45, Tom Wong-Cornall via mailop wrote:

On Fri, Sep  3 '21 at 10.02 NZST, Mark Fletcher via mailop  
wrote:

On Thu, Sep 2, 2021 at 2:31 PM Ken Johnson via mailop 
wrote:


The kind of answer I was expecting was along the lines of "Obviously your
data has been mis-interpreted as XYZZY encoding.  You can read about XYZZY
encoding here ."  (I did not say so, not
wanting to launch preconceptions.)

You didn't include any of the MIME headers, which might contain some

clues. Could it be something weird with format=flowed?


Your plaintext email reply nesting (as shown above) is ironic given the
context; compare with the HTML version you sent! Not the same as lines
being truncated, but definitely a loss of fidelity.


Indeed. A long known bug of Gmail's HTML mails, and one of the albeit 
minor reasons why I discourage its use.


--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] What's w/ .bl.score.senderscore.com?

2021-04-22 Thread Andreas Schamanek via mailop


On Wed, 21 Apr 2021, at 13:52, Tom Bartel wrote:


Issues should be resolved, please let me know otherwise.


Last error I got for 2.0.0.127.bl.score.senderscore.com was 
yesterday around 17:30 UTC. All good since then.


Thanks!

--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] What's w/ .bl.score.senderscore.com?

2021-04-21 Thread Andreas Schamanek via mailop


Did I miss something? Since days .bl.score.senderscore.com returns 
NXDOMAIN or SERVFAIL, and apparently I am not the only one affected.


--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Postmaster for UPC/chello.at/inode.at, now Magenta

2021-03-25 Thread Andreas Schamanek via mailop


The wonderful domain name b-home.at is not my own but I am its 
postmaster. All mail from b-home.at sent to chello.at and inode.at 
is rejected by mxin?.upcmail.net with e.g.


550 5.1.0 MXIN405 sending mailbox postmas...@b-home.at unknown

11 years ago [sic] b-home.at was hosted at inode.at (which became UPC 
and then Magenta). My guess is that some old config is lingering. 
Probably easy to fix for someone who knows nuts and bolts. However, I 
fail to find a contact. Official contact forms don't even mention 
e-mail. And all old contact addresses I had are either defunct or do 
not answer.


Can someone provide a contact that is at least likely to reach a 
postmaster?


MTIA,

--
-- Andreas


___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Spamcop

2021-01-31 Thread Andreas Schamanek via mailop


Could someone provide the old but apparently still valid IP addresses 
so that we can configure DNS forwarding locally instead of disabling 
the DNSBL?


--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] [FEEDBACK] Azure Spammer Activity

2021-01-14 Thread Andreas Schamanek via mailop


On Thu, 14 Jan 2021, at 20:22, Michael Wise via mailop wrote:


On Tue, 8 Dec 2020, at 23:43, Hans-Martin Mosner wrote:
Today we got a response to our abuse reports requesting that we 
report these to j...@office365.microsoft.com
Why would you have thought reporting an Azure item to the Office365 
abuse SAMPLE input queue would have any affect at all on Azure 
issues?


@Michael: Maybe he trusts your colleagues more than you do?

BTW, in reply to reports sent to ab...@microsoft.com I received 
several replies from cdo...@microsoft.com (the last one yesterday) 
telling me to report directly to c...@microsoft.com though this 
address is not listed in the respective whois records, like for 
52.149.219.36.


--
-- Andreas

 :-)

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Mailman confirmation email denial of service

2020-08-19 Thread Andreas Schamanek via mailop


On Wed, 19 Aug 2020, at 09:51, Andy Smith via mailop wrote:


Since yesterday I've been seeing a large number of attempted
subscriptions to all the public lists on one of my Mailman servers. 
(...)


I can confirm this for my servers from top to end including some of 
the hashes.


BTW, Mailman mm_cfg.py option `SUBSCRIBE_FORM_SECRET` apparently 
mitigates the DoS, too.


--
-- Andreas

 :-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] mta-sts.outlook.com Internal server error

2020-02-19 Thread Andreas Schamanek via mailop


A reminder:

On Thu, 16 Jan 2020, at 21:26, Michael Wise via mailop wrote:


And it appears to still be happening. Hmm.


1 month later, yes, MTA-STS at the receiving side of hotmail.com + 
outlook.com is _still_ broken :} (I haven't tried other Microsoft 
domains apart from @microsoft.com which doesn't offer MTA-STA at all.)



-Original Message-
From: mailop  On Behalf Of Andreas Schamanek via 
mailop
Sent: Thursday, January 16, 2020 1:17 PM
To: mailop 
Subject: [mailop] mta-sts.outlook.com Internal server error

In case someone cares:

$ curl -sD- -o/dev/null 
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta-sts.hotmail.com%2F.well-known%2Fmta-sts.txtdata=02%7C01%7Cmichael.wise%40microsoft.com%7C3808f274e5a2447acaa308d79aca1ca6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637148065163372902sdata=LJDO5VpnEx7FDxbUeDpdP%2BTIGfiaeoBOp0HqmPe9Mmg%3Dreserved=0
 | grep ^HTTP

HTTP/1.1 500 Internal Server Error

Same for hotmail.com. Started seeing this in the night between January
6 and 7.


--
-- Andreas

:-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] [ext] Re: Business justification to use noreply sender addresses?

2020-02-08 Thread Andreas Schamanek via mailop

On Fri, 7 Feb 2020, at 19:21, John Levine via mailop wrote:


In article ,
Philip Paeps via mailop  wrote:

On 2020-02-07 08:34:13 (-0800), Jaroslaw Rafa via mailop wrote:

It would be best if autoresponders simply didn't reply to messages
from mailing lists.
That windmill is not going to budge no matter how much you try to 
tilt it...


People who write mail software have known at least since the 1980s
that an autoresponder should only respond if the recipient's address
is on the To: or maybe the Cc: line.  I have a procmail man page from
about 1991 with an autoresponder recipe that makes that check.


+ RFC 3834 from 2004, and speaking of procmailrc

  * !^FROM_DAEMON

which includes `* !^Precedence: (list|junk|bulk)`

--
-- Andreas

 :-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


[mailop] mta-sts.outlook.com Internal server error

2020-01-16 Thread Andreas Schamanek via mailop


In case someone cares:

$ curl -sD- -o/dev/null https://mta-sts.hotmail.com/.well-known/mta-sts.txt | 
grep ^HTTP
HTTP/1.1 500 Internal Server Error

Same for hotmail.com. Started seeing this in the night between January 
6 and 7.


--
-- Andreas

 :-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] Reasons to add plain text alternative to email?

2019-12-09 Thread Andreas Schamanek via mailop


On Mon, 9 Dec 2019, at 09:50, Maarten Oelering via mailop wrote:

we were wondering if there's still a good reason for adding plain 
text to a html message. Is there a significant audience reading in 
plain text? Is plain text important for accessibility?


As others have said "significant" is significantly hard to define.
The percentage of human recipients reading plain text is probably 
declining. Still, IMHO, a plain text alternative part has the 
advantage that the sender has control over it. Without a plain text 
alternative it is up to the recipients to convert the HTML to 
something readable. This is known to lead to unwanted and certainly 
less than optimal results.


For a list of pros and cons of HTML in general see e.g. my list
https://fam.tuwien.ac.at/~schamane/_/html-mail-vs-plain-text

--
-- Andreas

 :-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] [EXTERNAL] Does sending HTML only email affect delivery?

2019-10-25 Thread Andreas Schamanek via mailop


On Fri, 25 Oct 2019, at 19:17, Michael Wise via mailop wrote:


We certainly don’t care….


You got a weird sense of humor ;)

$ perl -MEmail::MIME -e 'print 
Email::MIME->new(join("",<>))->debug_structure' michael.eml

+ multipart/mixed; 
boundary="_000_DM5PR00MB0267E9CF6178ED6925F03AAF80650DM5PR00MB0267namp_"
 + text/plain; charset="utf-8"
 + application/ms-tnef; name="winmail.dat"
 + text/plain; charset="utf-8"


--
-- Andreas

 :-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


[mailop] Is notification.skype.com an oversight?

2019-10-11 Thread Andreas Schamanek via mailop


notification.skype.com does not resolve. When I saw it some days ago I 
thought it was an oversight that Microsoft's gonna fix instantly, but 
I was mistaken:


Oct 12 01:14:09 iac postfix/smtpd[13338]: connect from 
db3gmehub01.msn.com[94.245.112.10]
Oct 12 01:14:09 iac postfix/smtpd[13338]: Anonymous TLS connection established 
from db3gmehub01.msn.com[94.245.112.10]: TLSv1.2 with cipher 
ECDHE-RSA-AES256-SHA384 (256/256 bits)
Oct 12 01:14:10 iac postfix/smtpd[13338]: NOQUEUE: reject: RCPT from 
db3gmehub01.msn.com[94.245.112.10]: 450 4.1.8 : Sender address 
rejected: Domain not found; from= to= 
proto=ESMTP helo=

$ host -t a notification.skype.com
notification.skype.com has no A record
$ host -t mx notification.skype.com
notification.skype.com has no MX record

however

$ host -t a notifications.skype.com
notifications.skype.com has address 91.190.216.101
$ host -t mx notifications.skype.com
notifications.skype.com mail is handled by 10 notifications.skype.com.

--
-- Andreas

 :-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] No MX record on domain is a bounce by Gmail

2019-05-04 Thread Andreas Schamanek via mailop


On Sat, 4 May 2019, at 11:44, Vytis Marciulionis via mailop wrote:


DNS Error: 6443565 DNS type 'mx' lookup of example.com responded with
code NXDOMAIN Domain name not found: example.com

Has anything changed and now we can consider "no MX record" a valid reason
to not deliver messages to that domain?


Looks like the domain was unknown. Of course, then the MX lookup 
fails. But there is a difference:


$ host -t a example.com.
example.com has address 93.184.216.34
$ host -t mx example.com.
example.com has no MX record
$ host -t a probablynotexisting.example.com.
Host probablynotexisting.example.com. not found: 3(NXDOMAIN)
$ host -t mx probablynotexisting.example.com.
Host probablynotexisting.example.com. not found: 3(NXDOMAIN)

--
-- Andreas

:-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop


Re: [mailop] Strange access alert for an outlook.com account

2019-05-04 Thread Andreas Schamanek via mailop


On Fri, 3 May 2019, at 20:13, Marc Bradshaw via mailop wrote:

What's odd here is that 2603:1036:301:2171::5 is allocated to 
Microsoft itself.


Maybe they still haven't fixed this hole?

  Microsoft: Hackers compromised support agent’s credentials to access
  customer email accounts | TechCrunch
  https://techcrunch.com/2019/04/13/microsoft-support-agent-email-hack/

SCNR,

--
-- Andreas

:-)


___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop