Re: [mailop] MagicMail / MIPSpace Listing

2022-01-29 Thread Jarland Donnell via mailop
It's not worth the effort to reach out to them. They're extremely condescending and god-like in attitude. Effort is best spent lobbying users to not support their software. On 2022-01-29 19:24, joemailop--- via mailop wrote: A server manage is also listed on All and Poor lists. I did a search

Re: [mailop] MagicMail / MIPSpace Listing

2022-01-29 Thread joemailop--- via mailop
A server manage is also listed on All and Poor lists. I did a search around that IP space, including stuff that never sends emails, like VPN concentrators, routers, and unused IP and they're listed too inside the same /24. I wouldn't be surprised if they block /24s. Removal URL that I found is

Re: [mailop] MagicMail / MIPSpace Listing

2022-01-29 Thread John Gateley via mailop
I just checked my server (very small) and it has the same result as yours. Both of them are on the MIPSpace-All and MIPSpace-Poor list. I can't find any way to delist. These are not pure spam, they are focused on (possibly solicited) commercial email. Since my server is just my wife and I, and

[mailop] MagicMail / MIPSpace Listing

2022-01-29 Thread Scott Mutter via mailop
Anybody from MagicMail or MIPSpace able to give any insight as to why 205.251.153.98 is listed? 550-Your message was rejected by this user and was not delivered. 550-Reason: This system uses BMS to check your IP address reputation, and was rejected by the user. IP=[205.251.153.98]. 550-Protection

Re: [mailop] Exchange 365 outbound connector being used as a relay

2022-01-29 Thread Matthew Richardson via mailop
Alexander Huynh via mailop wrote:- >On 2022-01-29 09:15:02 +, Matthew Richardson via mailop wrote: >> You may wish to have some authentication between O365 and Exim. The MS >> document linked discusses how to do this with certificates. > >The certificate setup listed at that page did not provi

Re: [mailop] Exchange 365 outbound connector being used as a relay

2022-01-29 Thread Alexander Huynh via mailop
On 2022-01-29 09:15:02 +, Matthew Richardson via mailop wrote: > As a thought (probably wrong) could this be caused by your O365 users > forwarding INCOMING email to them FROM outlook.com and/or mail.alokind.com > to external addresses? Since all mail flows through Exchange 365, O365 would hav

Re: [mailop] DMARC Reports to aliexpress.com won't be delivered.

2022-01-29 Thread Jan-Pieter Cornet via mailop
On 29-1-22 13:53, Bastian Blank via mailop wrote: On Fri, Jan 28, 2022 at 10:57:08PM +0100, Jan-Pieter Cornet via mailop wrote: Oh, and then there are a number of ticket systems or mailinglists behind dmarc reporting addresses that usually reply with something like 'Your email to our support s

Re: [mailop] DMARC Reports to aliexpress.com won't be delivered.

2022-01-29 Thread Bastian Blank via mailop
On Fri, Jan 28, 2022 at 10:57:08PM +0100, Jan-Pieter Cornet via mailop wrote: > Oh, and then there are a number of ticket systems or mailinglists behind > dmarc reporting addresses that usually reply with something like 'Your email > to our support system could not be accepted". Usually in such a

Re: [mailop] DMARC Reports to aliexpress.com won't be delivered.

2022-01-29 Thread Alessandro Vesely via mailop
On Fri 28/Jan/2022 22:57:08 +0100 Jan-Pieter Cornet via mailop wrote: On 27-1-22 11:30, Alessandro Vesely via mailop wrote: On Wed 26/Jan/2022 09:03:11 +0100 Mailop wrote: In general, there are also a lot of other _dmarc. records, that have e-mail addresses that doesn't work and generate undeli

Re: [mailop] Exchange 365 outbound connector being used as a relay

2022-01-29 Thread Matthew Richardson via mailop
Alexander Huynh via mailop wrote:- >Meaning that domains `outlook.com` and `mail.alokind.com` have managed to use >Exchange >365 infrastructure to try and route email through my connector. As a thought (probably wrong) could this be caused by your O365 users forwarding INCOMING email to them FR