Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread John Levine via mailop
It appears that Suresh Ramasubramanian via mailop  said:
>Why is it deferred when you get a 554?

Because that's the response on the initial connection, not to a message.

Here's what I get when I connect from my house:

Connected to mx.sympatico.ca.
554 Invalid DNS PTR resource record for 64.246.232.221
Connection closed by foreign host.

(It's right, there's no PTR on my IP.)

This has nothing to do with anything about any individual message, since it
never sees an individual message.  Anyone who's guessing about problems
with the messages, bad guess.

I see in another message that the client in question is at Linode, so my guess
is that they block all connections from Linode.  I don't blame them, since the
vast majority of mail I've seen from Linode hosts is spam.

R's,
John
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop


Re: [mailop] HR 8160 and SB 4409: The "You're not allowed to run political campaign email through your spam filter" act

2022-07-31 Thread Laura Atkins via mailop
The research paper seems reasonably well done and I encourage people to 
actually read it and their conclusions rather than paying attention to the 
popular press takes on it. 

Laura

Sent from my iPhone

> On Jul 30, 2022, at 7:54 PM, Larry M. Smith via mailop  
> wrote:
> 
> On 7/29/2022, Anne Mitchell via mailop wrote:
>> I want to be sure that everyone here is aware of a piece of pending 
>> legislation in the U.S. that is in committee in both the House and the 
>> Senate right now. It's called the Political BIAS Emails Act of 2022 (BIAS is 
>> short for “Bias In Algorithm Sorting”), and it requires that, and I quote:
>> “It shall be unlawful for an operator of an email service to use a filtering 
>> algorithm to apply a label to an email sent to an email account from a 
>> political campaign unless the owner or user of the account took action to 
>> apply such a label.”
>> It is getting relatively very little press, and of course the chances of it 
>> passing are greater if nobody knows to oppose it.
>> We've written an article about it, which includes what to do, whom to 
>> contact and how, etc., and which includes all relevant links, here:
>> https://www.isipp.com/blog/do-you-want-political-email-to-bypass-spam-filters-and-go-directly-to-your-inbox-congress-does-heres-what-to-do/
>> Feel free to share - in fact please do, if this thing passes it's the 
>> camel's nose under the tent.
> 
> IIRC, this all started because a research paper somewhere noted that a 
> specific political party seemed to have more deliverability issues than the 
> other prominent party did.  Fast forward a bit and  there exists a 
> vast conspiracy in anti-spam against that specific political party .
> 
> I can't speak to all anti-spam systems, but the vast majority of them work on 
> behavioral models and not some list of word that someone has entered into a 
> list somewhere.
> 
> I have noted that a large number that political party's members seem to be 
> quick to label those that disagree with some its policies and positions as 
> either the enemy or disloyal.  Perhaps it is an attitude "I will do what I 
> want, and if you disagree with me, then you are some sort of commie scum," 
> that has resulted in them not following advise offered to them, so that they 
> don't look like a bunch of spammers taking a bump all over everyone's inboxes.
> 
> .. I really don't know, but I tend to discount the belief that this is a 
> conspiracy against them.
> 
> 
> SgtChains
> ___
> 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] Trouble sending to sympatico.ca

2022-07-31 Thread Bill Cole via mailop

On 2022-07-31 at 13:07:43 UTC-0400 (Sun, 31 Jul 2022 12:07:43 -0500)
John Gateley via mailop 
is rumored to have said:


On 7/31/22 11:38 AM, Michael Rathbun via mailop wrote:


Since you have included none of the information that might have been 
used by
the receiving system (your IP?  Your HELO string?  The domain in the 
envelope?

Any domains referenced in the body?) ...



Fair point:

The sending domain is annbauer.com, mx is hosted by 
mx.oustrencats.com.


IP addresses:

root@giraffe:~# host mx.oustrencats.com
mx.oustrencats.com has address 50.116.29.164
mx.oustrencats.com has IPv6 address 2600:3c00:e000:323::1

I am not positive on the HELO string, as postfix isn't logging that, 
but I would guess it is mx.oustrencats.com with envelope from 
x...@annbauer.com


I would bet that with the error message you cited, there was no HELO or 
envelope sender, because the *connection* was refused.


Again, DKIM, SPF, DMARC and reverse DNS are set up properly enough to 
get mail delivered to google.


Google does what Google does. Sympatico clearly does elsewise. Their 
servers, their rules.


My guess is that Sympatico got tired of seeing misbehaving Linode IPs in 
their logs and you're just collateral damage.



Not sure what you mean about domains referenced in the body, someone 
contacted my wife and she was replying.


Some spam filters (e.g. SpamAssassin) parse any URIs out of message 
bodies and score based on the reputation of their domains.


Likely not relevant in this case, especially since there was probably no 
SMTP traffic sent at all.


--
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


Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread Michael Rathbun via mailop
On Sun, 31 Jul 2022 12:07:43 -0500, John Gateley via mailop
 wrote:

>The sending domain is annbauer.com, mx is hosted by mx.oustrencats.com.
>
>IP addresses:
>
>root@giraffe:~# host mx.oustrencats.com
>mx.oustrencats.com has address 50.116.29.164

Look clean as far as publicly accessible reputation lists are concerned.

>Not sure what you mean about domains referenced in the body, someone 
>contacted my wife and she was replying.

Some systems will examine the message in depth, and check some or all of the
domains found against domain reputation lists.  Some of my clients find their
mail is rejected because they are using a third-party statistics or image
hosting system, and that system's domain has been listed in URIBL or a similar
service, for a simple example.

mdr
-- 
   "There will be more spam."
  -- Paul Vixie

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


Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread John Gateley via mailop


On 7/31/22 11:38 AM, Michael Rathbun via mailop wrote:


Since you have included none of the information that might have been used by
the receiving system (your IP?  Your HELO string?  The domain in the envelope?
Any domains referenced in the body?) ...



Fair point:

The sending domain is annbauer.com, mx is hosted by mx.oustrencats.com.

IP addresses:

root@giraffe:~# host mx.oustrencats.com
mx.oustrencats.com has address 50.116.29.164
mx.oustrencats.com has IPv6 address 2600:3c00:e000:323::1

I am not positive on the HELO string, as postfix isn't logging that, but 
I would guess it is mx.oustrencats.com with envelope from x...@annbauer.com


Again, DKIM, SPF, DMARC and reverse DNS are set up properly enough to 
get mail delivered to google.


Not sure what you mean about domains referenced in the body, someone 
contacted my wife and she was replying.


Thanks!


John

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


Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread Jaroslaw Rafa via mailop
Dnia 31.07.2022 o godz. 09:28:31 John Gateley via mailop pisze:
> 
> Usually providers provide info on the block, with details on how to get
> removed if you are legit etc. This error is very unfriendly...

For example in case of Postfix, if you manually add sender's IP or email
address to the block list (check_sender_access or similar), then the sending
server gets just "Access denied" message.

Actually, in case of a manual block, there's really not much info to return
except "Access denied"...
-- 
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://list.mailop.org/listinfo/mailop


Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread Michael Rathbun via mailop
On Sun, 31 Jul 2022 08:36:31 -0500, John Gateley via mailop
 wrote:


>I don't see any details in the error message.

Since you have included none of the information that might have been used by
the receiving system (your IP?  Your HELO string?  The domain in the envelope?
Any domains referenced in the body?) ... 

>Any ideas? Thanks!

...we really can't say too much.

mdr
-- 
 "There are no laws here, only agreements."  
-- Masahiko

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


Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread Jarland Donnell via mailop
I just ran through the last month of SMTP logs and the only error I 
found was "451 System policy engine error" for sympatico.ca besides 
"User unknown" (contact form typos it looks like). So for what little 
it's worth, I think this is either domain or IP reputation. Doesn't have 
to be for anything you did, they may be like AT and just have a bunch 
of IPs blocked for no real reason.


On 2022-07-31 08:36, John Gateley via mailop wrote:

Hello,

I just got a bounce from sympatico.ca that I don't understand:


Jul 31 04:20:41 giraffe postfix/qmgr[2366]: 841B53C6CD:
from=, size=7809, nrcpt=1 (queue active)
Jul 31 04:20:41 giraffe postfix/smtp[526159]: 841B53C6CD:
to=, relay=mx.sympatico.ca[209.71.212.24]:25,
delay=433213, delays=433213/0.02/0.15/0, dsn=4.0.0, status=de
ferred (host mx.sympatico.ca[209.71.212.24] refused to talk to me: 554
Access Denied)
Jul 31 04:20:41 giraffe postfix/qmgr[2366]: 841B53C6CD:
from=, status=expired, returned to sender

It had been in the queue for a week or so, and finally bounced.

I don't see any details in the error message.

I have a very small mail server (just my wife and I) but it is
configured with reverse DNS, SPF, DKIM and DMARC. I can send to the
big players without bouncing or ending in the spam folder.


Any ideas? Thanks!


John

___
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] Trouble sending to sympatico.ca

2022-07-31 Thread John Gateley via mailop


On 7/31/22 8:55 AM, Suresh Ramasubramanian via mailop wrote:

Why is it deferred when you get a 554?

Probably a spam block on your IP or domain name with that generic an 
error





I'm not sure why my server defers on 554, that's the default config for 
postfix I think. Anyways, that is my server, not sympatico.ca


Usually providers provide info on the block, with details on how to get 
removed if you are legit etc. This error is very unfriendly...



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


Re: [mailop] Trouble sending to sympatico.ca

2022-07-31 Thread Suresh Ramasubramanian via mailop
Why is it deferred when you get a 554?

Probably a spam block on your IP or domain name with that generic an error

--srs

From: mailop  on behalf of John Gateley via mailop 

Sent: Sunday, July 31, 2022 7:06:31 PM
To: mailop@mailop.org 
Subject: [mailop] Trouble sending to sympatico.ca

Hello,

I just got a bounce from sympatico.ca that I don't understand:


Jul 31 04:20:41 giraffe postfix/qmgr[2366]: 841B53C6CD:
from=, size=7809, nrcpt=1 (queue active)
Jul 31 04:20:41 giraffe postfix/smtp[526159]: 841B53C6CD:
to=, relay=mx.sympatico.ca[209.71.212.24]:25,
delay=433213, delays=433213/0.02/0.15/0, dsn=4.0.0, status=de
ferred (host mx.sympatico.ca[209.71.212.24] refused to talk to me: 554
Access Denied)
Jul 31 04:20:41 giraffe postfix/qmgr[2366]: 841B53C6CD:
from=, status=expired, returned to sender

It had been in the queue for a week or so, and finally bounced.

I don't see any details in the error message.

I have a very small mail server (just my wife and I) but it is
configured with reverse DNS, SPF, DKIM and DMARC. I can send to the big
players without bouncing or ending in the spam folder.


Any ideas? Thanks!


John

___
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] Trouble sending to sympatico.ca

2022-07-31 Thread John Gateley via mailop

Hello,

I just got a bounce from sympatico.ca that I don't understand:


Jul 31 04:20:41 giraffe postfix/qmgr[2366]: 841B53C6CD: 
from=, size=7809, nrcpt=1 (queue active)
Jul 31 04:20:41 giraffe postfix/smtp[526159]: 841B53C6CD: 
to=, relay=mx.sympatico.ca[209.71.212.24]:25, 
delay=433213, delays=433213/0.02/0.15/0, dsn=4.0.0, status=de
ferred (host mx.sympatico.ca[209.71.212.24] refused to talk to me: 554 
Access Denied)
Jul 31 04:20:41 giraffe postfix/qmgr[2366]: 841B53C6CD: 
from=, status=expired, returned to sender


It had been in the queue for a week or so, and finally bounced.

I don't see any details in the error message.

I have a very small mail server (just my wife and I) but it is 
configured with reverse DNS, SPF, DKIM and DMARC. I can send to the big 
players without bouncing or ending in the spam folder.



Any ideas? Thanks!


John

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