[mailop] Microsoft 365 IP addresses listed on Spamcop

2024-02-14 Thread Christopher Hawker via mailop
Hello all,

I am attempting to send mail from a M365 tenancy, however, we are seeing issues 
with it being filtered due to the address appearing on bl.spamcop.net.
"Decision Engine classified the mail item was rejected because of IP Block 
(from outbound normal IP pools) -> 550 mail from 40.107.107.97 refused, see 
http://www.spamcop.net - Your mail provider is blocked because is sending SPAM."
If there is anyone on-list from Microsoft, could you please take a look? It's 
causing issues šŸ™

Thanks,
Christopher Hawker
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Extortion spam from OVH-hosted *.sbs domains

2024-01-24 Thread Christopher Hawker via mailop
If the abuse contact (ab...@ovh.net) is not responding to e-mails report the 
lack of response to RIPE NCC, the RIR that delegated the resources to them. I 
know that if members under APNIC fail to maintain an abuse and IRT contact 
their account is suspended until it is validated.

I already filter all mail traffic from OVH. They are notorious for failing to 
act on abuse reports.

Regards,
Christopher Hawker

From: mailop  on behalf of Hans-Martin Mosner via 
mailop 
Sent: Thursday, January 25, 2024 5:10 PM
To: mailop 
Subject: [mailop] Extortion spam from OVH-hosted *.sbs domains


Tonight we received a huge wave of extortion spams from OVH hosted domains 
trying to get bitcoin payments. The senders claim that recipients watched child 
porn.

This is the final straw for me to add a rule to reject all mail traffic from 
OVH until the sender is whitelisted. OVH is completely unresponsive to abuse 
complaints, they won't even react when clearly criminal activity happens from 
their IP space.

The domains used were:

aoyn.sbs
bnop.sbs
burx.sbs
enux.sbs
fojr.sbs
hnls.sbs
nbot.sbs
ouhb.sbs
pxur.sbs
rnuh.sbs

with the IP addresses

51.89.5.129
51.89.5.145
51.89.175.30
51.89.175.173
51.89.175.196
54.38.1.200
57.128.16.249
57.128.60.137
57.128.83.193
57.128.123.32
57.128.165.75
57.128.166.120
91.134.96.213
91.134.97.224
91.134.97.232
135.125.66.34
135.125.66.86
135.125.66.217
135.125.217.78
141.94.64.94
141.95.108.175
148.113.137.42
148.113.139.81
148.113.140.91
148.113.141.117
148.113.143.4
162.19.68.117

It's probably pointless to call for a general OVH boycott, as much as I would 
like to do that :-)

Cheers,
Hans-Martin
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Spamhaus contact?

2024-01-23 Thread Christopher Hawker via mailop
I've never had an issue with Spamhaus. Only recently (last couple of weeks), I 
needed to get a recycled IP address for a VM on a cloud provider in AU removed 
as well as a domain delisted from their DBL, which they did with ease. Took a 
little bit of time however did not require any interaction from myself to do 
so. Explained that it was a personal mail system with 2-3 mailboxes and it was 
all taken care of.

Kudos to Spamhaus!

Regards,
Christopher Hawker

From: mailop  on behalf of Riccardo Alfieri via 
mailop 
Sent: Wednesday, January 24, 2024 2:10 AM
To: mailop@mailop.org 
Subject: Re: [mailop] Spamhaus contact?


On 22/01/24 20:19, Curtis Maurand via mailop wrote:

Given my experience with spamhaus this week, Iā€™m convinced that they are out to 
put the small email provider out of business.

Well from what I can see we have samples from a few days ago coming from a 
domain for which you have opened a ticket, with curious subjects like "casino 
games win real money" "Buy pills without restrictions" etc..

If you feel this is an abuse of your infrastructure by some customer of yours, 
please continue the ticket thread.

We are not here to put anyone out of business, on the contrary, we try our best 
to help listees when they have an abuse problem.

--
Best regards,
Riccardo Alfieri

Spamhaus Technology
https://www.spamhaus.com/
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] mail.ru - Connection timed out

2022-09-16 Thread Christopher Hawker via mailop
Iā€™m able to telnet to mxs.mail.ru:25 from Sydney AU.

- CH

Sent from my iPhone

> On 16 Sep 2022, at 7:57 pm, Klaus Tachtler via mailop  
> wrote:
> 
> ļ»æHi,
> 
> does anyone else besides us have problems connecting to mail.ru email servers?
> 
> We are not getting connection from mxs.mail.ru[217.69.139.150] and 
> mxs.mail.ru[94.100.180.31] since 2 days.
> 
> (delivery temporarily suspended: connect to mxs.mail.ru[217.69.139.150]:25: 
> Connection timed out)
> (delivery temporarily suspended: connect to mxs.mail.ru[94.100.180.31]:25: 
> Connection timed out)
> 
> 
> Thanks and greetings
> Klaus.
> 
> 
> -- 
> 
> ---
> e-Mail  : kl...@tachtler.net
> Homepage: https://www.tachtler.net
> DokuWiki: https://dokuwiki.tachtler.net
> ---

mime-attachment
Description: Binary data
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Proofpoint Mail Blocking

2022-09-14 Thread Christopher Hawker via mailop
Hello all,

 

If anyone from Proofpoint is on-list, could they please reach out to me
off-list (chris at thesysadmin dot dev) regarding issues with mail flow
through their network?

 

Thanks,

Christopher Hawker

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


Re: [mailop] SMTP noise from *.bouncer.cloud

2022-09-02 Thread Christopher Hawker via mailop
Seems like a whole lot of bitching and whinging is going on here regarding 
bouncer.cloud. Pretty sure this is a mail operations list, not a ā€œletā€™s whinge 
and complain about mail servicesā€ list.

Itā€™s very simple - if you donā€™t like or want traffic from their systems 
entering your network or servers, then blackhole their AS or block the IPs and 
domains which they use. If you want to discuss their services, take it off-list 
with whoever you choose.

CH.

Sent from my iPhone

> On 3 Sep 2022, at 6:20 am, Bill Cole via mailop  wrote:
> 
> ļ»æOn 2022-09-02 at 14:16:25 UTC-0400 (Fri, 2 Sep 2022 18:16:25 +)
> Larry M. Smith via mailop 
> is rumored to have said:
> 
>> On 8/31/2022, Bill Cole via mailop wrote:
>> (snip)
 Who/what/where their clients are, and for what purpose of course, is not 
 likely something we will find out unless they like to share more, but we 
 can continue discussing this in terms of all the operators out there, and 
 what constitutes the good vs the ugly.
>>> 
>>> Their intended service is the problem.
>>> 
>> 
>> Also at the same address physical address;
>> 
>> https://woodpecker.co/
> 
> It's as if they live in a different reality... Where 'cold email' is not 
> intrinsically problematic.
> 
> The name only makes it worse.
> 
> 
> -- 
> Bill Cole
> b...@scconsult.com or billc...@apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
> ___
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Microsoft 365 Mail Blocking

2022-09-01 Thread Christopher Hawker via mailop
Fortunately I was able to raise a ticket through the M365 Admin Portal, they 
asked a few questions about the company and were able to remove the IP address 
from their spam block list.

Regards,
Christopher Hawker

From: Agathe Allard 
Sent: Thursday, September 1, 2022 7:13 PM
To: Christopher Hawker 
Cc: Christopher Hawker via mailop 
Subject: Re: [mailop] Microsoft 365 Mail Blocking

Hello,

We've been seeing the same errir for several weeks now too for information

Thanks,
Agathe

Le jeu. 1 sept. 2022 Ć  10:59, Christopher Hawker via mailop 
mailto:mailop@mailop.org>> a Ć©crit :
Hello All,

I am currently receiving the below error when attempting to send e-mails to 
M365 e-mail addresses using an Exchange connector as a relay within a tenancy:

550 5.7.708 Service unavailable. Access denied, traffic not accepted from this 
IP. For more information please go to 
http://go.microsoft.com/fwlink/?LinkId=526653 AS(8564) 
[MEYP282MB2719.AUSP282.PROD.OUTLOOK.COM<http://MEYP282MB2719.AUSP282.PROD.OUTLOOK.COM>]
 
[SYYP282CA0011.AUSP282.PROD.OUTLOOK.COM<http://SYYP282CA0011.AUSP282.PROD.OUTLOOK.COM>]
 
[SY4AUS01FT014.eop-AUS01.prod.protection.outlook.com<http://SY4AUS01FT014.eop-AUS01.prod.protection.outlook.com>]

If there is anyone from Microsoft on-list, could they please reach out to 
assist with resolving this issue?

Thanks,
Christopher Hawker
___
mailop mailing list
mailop@mailop.org<mailto:mailop@mailop.org>
https://list.mailop.org/listinfo/mailop


--






Agathe Allard

DELIVERABILITY MANAGER

Telephone 03 74 09 85 41





MINDBAZ - 125, AVENUE DE LA REPUBLIQUE - 59110 LA MADELEINE
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Microsoft 365 Mail Blocking

2022-09-01 Thread Christopher Hawker via mailop
Hello All,

I am currently receiving the below error when attempting to send e-mails to 
M365 e-mail addresses using an Exchange connector as a relay within a tenancy:

550 5.7.708 Service unavailable. Access denied, traffic not accepted from this 
IP. For more information please go to 
http://go.microsoft.com/fwlink/?LinkId=526653 AS(8564) 
[MEYP282MB2719.AUSP282.PROD.OUTLOOK.COM] 
[SYYP282CA0011.AUSP282.PROD.OUTLOOK.COM] 
[SY4AUS01FT014.eop-AUS01.prod.protection.outlook.com]

If there is anyone from Microsoft on-list, could they please reach out to 
assist with resolving this issue?

Thanks,
Christopher Hawker
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Microsoft Office365 blocking non Oauth2 authentication on IMAP and SMTP.

2022-08-19 Thread Christopher Hawker via mailop
Hello Benoit,

What mail client is being used, that doesn't support Oauth2?

Regards,
Christopher Hawker

From: mailop  on behalf of BenoƮt Panizzon via 
mailop 
Sent: Friday, August 19, 2022 4:41 PM
To: mailop@mailop.org 
Subject: [mailop] Microsoft Office365 blocking non Oauth2 authentication on 
IMAP and SMTP.

Hi Team

I am involved in a large non profit organisation in Switzerland.

A couple of years ago, that organisation got persuaded to switch to
Office365 as they got a good offer for non profit organisations. One of
the promises at that time: Everyone could continue working as before as
all clients could connect via IMAP and SMTP, so migration all existing
volunteer accounts and tools would work seamlessly.

Most email user are 'external' volunteers.

Now more and more co-volunteers, including myself get locked out of
their email accounts, because Microsoft disabled non Oauth2 token
authentication. Tools stop working. (usually found out after repeatedly
going through the password reset recovery procedure and still not being
able to log in).

Using the web-based tools is not an option.

The Problem: Most client are unable to use Oauth2. There are
mailinglist tools which connect to a mailbox to process bounces as
example. But any other tool generating emails and sending them via SMTP
is affected.

Some tools are able to do Oauth2, but the help from the 'Domain
Administrator' is needed, to register those tools as 'trusted app' with
Microsoft Azure to get a unique client-id for that tool, but then again
the token renewal then fails after some time (this needs to be
done via a HTTP request somehow) needing a lot of attention to keep
those tools running.

Microsoft Support states, they won't re-enable tokenless authentication
and the provide no help at all to get tools back online which do not
work any more.

I wonder: How do other Microsoft Office365 customers mitigate this
situation?

--
Mit freundlichen GrĆ¼ssen

-BenoƮt Panizzon- @ HomeOffice und normal erreichbar
--
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://list.mailop.org/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


[mailop] Microsoft 365 Mail Banlist

2022-08-14 Thread Christopher Hawker via mailop
Hello All,

I have attempted to use a connector in our Microsoft 365 tenancy as a mail 
relay, however mail is being blocked with the below message:

ā€‚ā€‚"5.7.511 Access denied, banned sender[192.46.xxx.xxx]. To request removal 
from this list please forward this message to del...@messaging.microsoft.com. 
For more information please go to 
http://go.microsoft.com/fwlink/?LinkId=526653.";

I did try to send an e-mail to the specified address however I received a "550 
5.4.300 Message expired" bounceback. I've also tried having the IP address 
delisted using https://sender.office.com which reported the request was denied. 
If there is anyone on here from Microsoft that could assist, could you please 
reach out off-list?

Thanks,
Christopher Hawker
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop