I cleared this up the last time by putting the very long unique from
address on the no processing list.
Overnight the problem re-appeared with a slightly different from address.
 It's to the same recipient and again a legitimate email from American
Airlines through the same mailing service as last time.  ASSP is still
sending a 451.  I only know about this because I have a notifyRE of
"warning:"

This time it is with a different txt record lookup, but it's hanging just
like it did in January.

*Warning: try to terminate inactive/stuck Worker_1*

*warning: TERMINATED - possibly by MainThread on detected stuck  - for DNS
query on '_adsp._domainkey.mail2.bounce.spopessentials2.com
<http://domainkey.mail2.bounce.spopessentials2.com>','TXT'*

In January, the error was
*Warning: TERMINATED - possibly by MainThread on detected stuck  -
for DNS query on '_domainkey.bounce.spopessentials2.com
<http://domainkey.bounce.spopessentials2.com/>','TXT'*

They definitely have DNS issues as spopessentials2.com.  I looked for the
txt record _adsp._domainkey.mail2.bounce.spopessentials2.com and that does
not exist, just like _domainkey.bounce.spopessentials2.com didn't exist in
January.  I haven't seen this any other time than in January and today.
Last time I thought it was just a fluke, but now that it's happened a
second time with the same sender, *I'm convinced that there is a dns
**reconfiguration scenario
on the sender side that ASSP isn't gracefully handling.*




On Fri, Jan 25, 2019 at 11:20 AM K Post <nntp.p...@gmail.com> wrote:

> For about 24 hours, I keep getting notices of a stuck MainThread doing a
> dns looking up of _domainkey.bounce.spopessentials2.com   It's always
> this same record causing this.  It's a legitimate mail from American
> Airlines.  This keeps happening, every time they send it.
>
>
>
> *Jan-25-19 10:34:27 Warning: TERMINATED - possibly by MainThread on
> detected stuck  - for DNS query on '_domainkey.bounce.spopessentials2.com
> <http://domainkey.bounce.spopessentials2.com>','TXT'*
>
>
> Jan-25-19 10:30:57 Connected: session:1113B818 208.85.50.32:47782 >
> assp:25 > smtp:25
>
> Jan-25-19 10:31:18 Info: enhanced Originated IP detection ignored IP's:
> 208.85.50.32 (connected IP)
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> [scoring] DKIM domain-check skipped - bounce.mail2.spopessentials2.com
> does not support DKIM  <== but it's still doing a lookup?
>
> Jan-25-19 10:35:48 msg30257-00511 [BlackHELO] 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> [scoring] (blacklisted HELO 'mail2155.silverpop.mkt2499.com' - weight 1)
> <-- that's interesting, shouldn't be
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> deleting spamming safelisted tuplet: (208.85.50.0,
> bounce.mail2.spopessentials2.com) age: 4m 30s
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> Message-Score: added 20 for blacklisted HELO '
> mail2155.silverpop.mkt2499.com' - weight 1, total score for this message
> is now 20
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> checking MX/A for businessextraa.email.aa.com ,
> bounce.mail2.spopessentials2.com
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> businessextraa.email.aa.com - MX 'mail-router.e-dialog.com' - got IP
> (208.94.20.16)
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> bounce.mail2.spopessentials2.com - MX 'bounce.mail2.spopessentials2.com'
> - got IP (74.112.69.40)
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org MX
> found: businessextraa.email.aa.com (From , Reply-To) ->
> mail-router.e-dialog.com
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org A
> record found for MX: businessextraa.email.aa.com (From , Reply-To) ->
> 208.94.20.16
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org MX
> found: bounce.mail2.spopessentials2.com (Mail From: , List-Unsubscribe)
> -> bounce.mail2.spopessentials2.com
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org A
> record found for MX: bounce.mail2.spopessentials2.com (Mail From: ,
> List-Unsubscribe) -> 74.112.69.40
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org 
> *Connection
> idle for 180 secs - timeout  <-- is that because Main Thread got stick?*
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> [SMTP Status] 451 Connection timeout, try later
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> finished message - received DATA size: 13.51 kByte - sent DATA size: 0 Byte
>
> Jan-25-19 10:35:48 msg30257-00511 208.85.50.32 <
> longstr...@bounce.mail2.spopessentials2.com> to: u...@ourcharity.org
> disconnected: session:1643B898 208.85.50.32 - processing time 0 seconds
>
>
> Any idea of what's going on and how to fix?
>
> thanks
>
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to