[mailop] abuse.ch RPZ syntax error

2023-10-10 Thread Slavko via mailop
Hi,

recently i noticed, that one RPZ from abuse.ch floods my logs about
syntax error in it. As i contributed to improve its RPZs syntax some
(long) time ago, i go to their site to find email address as previously,
to report that.

I found no email address but link to contact form at spamhaus site.
I was surprised, that i have to fill as many personal information,
without which the form cannot be send. Interesting! Are they more
interested in my personal details as they are in fixing own errors?
Seems that yes...

I will not fill it, not right, nor fake, i can live without that entry and
with some extra lines in logs, and perhaps without that RPZ at whole
as i will never fill random form which asks too many details...

regards

-- 
Slavko
https://www.slavino.sk/
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] Proofpoint Contact

2023-10-10 Thread Curtis Maurand via mailop
I tried every few days for a couple of weeks from the link you provided 
and never heard a word from them and the ip is still listed. Our client 
changed their practices to double opt-in, added highly visible and 
functional opt-out links, fired the person who was responsible for 
screwing things up in the first place and moved to a third party list 
provider (such as mailchimp. I'm not exactly sure who their using) that 
pays folks like spamhaus and proofpoint and moved the mail domain to a 
clean ip address.  They also set up a new email domain on a clean ip 
address to handle replies only.


I went to the second one.  We are blacklisted on 3. 2 I can't do 
anything about (spamrats - not exactly trustworthy and they have the 
entire /24 blocked and they wouldn't listen to our provider.) and 
another called spfbl.net which I'm working on the delisting. proofpoint 
has us blocked, but they don't report to either mxtoolbox or the valli.org


--Curtis

On 10/5/23 16:25, Jim Popovitch via mailop wrote:


In the past, I've found them to be totally unresponsive and gave up 
on them.




That can't be right.  I literally contacted them a few days ago and 
had a successful response (unlisting) within minutes during US 
business hours.


Go here, put in your IP address, and they give you an opportunity to 
input a text description about the issue.


https://ipcheck.proofpoint.com/

Note, they may not contact you, they did not contact me, but they did 
read what I wrote to them and they removed their listing of my IP address.


I would add as a further point, it's up to you to make certain that 
your IP is clean before you ask them to unblock it.


Put your IP(s) in https://multirbl.valli.org/ and see what lots of 
folks think about it.


-Jim P.

___
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] fastmail and sender score snafu

2023-10-10 Thread Louis Laureys via mailop
I believe they meant users changing their mx for an existing domain, when moving
to fastmail for example. Not necessarily a new domain, though I guess they can't
really differentiate those technically. So the policy would also apply to new
domains. Not entirely sure that this is the solution, but I get it.

Louis


Op dinsdag 10 oktober 2023 om 12:25, schreef Alessandro Vesely via mailop:

> On Mon 09/Oct/2023 08:23:33 +0200 Robert Mueller via mailop wrote:
> > >> I see that current setup might be useful in case some user changes MX >>
> before the domain is activated at Fastmail, in which case giving 4xx >> could
> make sense. But it is not right to report such re-tries to sender >> score as
> attempts to deliver to non-existing users.
> > > Yes, this is why we 4xx rather than 5xx email sent to an unconfigured
> domain. Many inexperienced email users aren't sure exactly what order to
> change or set things up in and we've seen users lose email before because they
> changed the MX records before adding their domain at Fastmail. The 4xx
> response reduces the chance of lost email.
> 
> That's bad.
> 
> First, nobody sends an important mail to a new domain without double checking
> its delivery. It is very reasonable to loose a few test messages when you set
> a new domain up.
> 
> By 4xx any unconfigured domain, a warning for delayed email can take hours and
> several attempts. A 5xx would result in an immediate DSN, which is much better
> in case of mistyping.
> 
> Best
> Ale
> --
> 
> ___
> mailop mailing list
> mailop@mailop.org [mailop@mailop.org]
> https://list.mailop.org/listinfo/mailop
> [https://list.mailop.org/listinfo/mailop]___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] fastmail and sender score snafu

2023-10-10 Thread Alessandro Vesely via mailop

On Mon 09/Oct/2023 08:23:33 +0200 Robert Mueller via mailop wrote:


I see that current setup might be useful in case some user changes MX 
before the domain is activated at Fastmail, in which case giving 4xx 
could make sense. But it is not right to report such re-tries to sender 
score as attempts to deliver to non-existing users.


Yes, this is why we 4xx rather than 5xx email sent to an unconfigured domain. 
Many inexperienced email users aren't sure exactly what order to change or set 
things up in and we've seen users lose email before because they changed the MX 
records before adding their domain at Fastmail. The 4xx response reduces the 
chance of lost email.



That's bad.

First, nobody sends an important mail to a new domain without double checking 
its delivery.  It is very reasonable to loose a few test messages when you set 
a new domain up.


By 4xx any unconfigured domain, a warning for delayed email can take hours and 
several attempts.  A 5xx would result in an immediate DSN, which is much better 
in case of mistyping.



Best
Ale
--





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


[mailop] BT Internet contact

2023-10-10 Thread Isabelle Di Tommaso via mailop
Good morning,

I've had a problem with bad connection bounces for one of my customers since 
September 16th and I'm having a hard time getting answers and help from BT.
I have already contacted the postmaster but without any real exchange.

This client is on shared environment and sends transactionnal emails.

Is there anyone from BT here? Or someone who has a contact ?

Thanks for your help,
Isabelle



Isabelle DI TOMMASO
SENIOR DELIVERABILITY CONSULTANT
[Actito]



CONTACT ME

isabelle.ditomm...@actito.com
www.actito.com



[cid:6e6da6b8-214f-4fa0-a670-ccb841034234]
Subscribe to our newsletter





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