--- [ "Ken Hohhof" <[email protected]> wrote ]
-----------------------------------
Strange, if I look up SMTP connection caching, it says it can't be used with
TLS.
-----Original Message-----
From: Animal Farm
Sent: Monday, September 15, 2014 1:06 PM
To: Ken Hohhof
Subject: Re: [AFMUG] spam
--- [ "George Skorup (Cyber Broadcasting)" <[email protected]> wrote ]
-----------------------------------
Well, at least we got you back, Chuck! Your presence offsets my anger
for the new list headaches. Trying to be helpful with the issues. Sorry
if I'm complaining too much.
Paul, you might want to send that log file output from my mail server to
someone at Amazon about the missing SMTP QUIT commands. That breaks the
RFC and my mail server obviously doesn't like that, which I can't change
because the connection rate-limiting is very helpful in stopping or
slowing down attacks. I don't know what would cause SMTP commands to be
dropped on their end. Anyway.. I don't touch our cPanel server unless
it's absolutely necessary. Usually cPanel themselves break stuff and I
make them log in and fix it.
Here's some more from a few minutes ago:
2014-09-15 12:47:08 SMTP command timeout on TLS connection from
a9-109.smtp-out.amazonses.com [54.240.9.109]:55967
2014-09-15 12:47:08 H=a9-109.smtp-out.amazonses.com [54.240.9.109]:55967
Warning: "Connection Ratelimit - a9-109.smtp-out.amazonses.com
[54.240.9.109]:55967 because of notquit: command-timeout (1.8/1h max:1.2)"
2014-09-15 12:47:29 SMTP command timeout on TLS connection from
a9-91.smtp-out.amazonses.com [54.240.9.91]:37510
2014-09-15 12:49:30 SMTP command timeout on TLS connection from
a9-110.smtp-out.amazonses.com [54.240.9.110]:49199
2014-09-15 12:49:30 H=a9-110.smtp-out.amazonses.com [54.240.9.110]:49199
Warning: "Connection Ratelimit - a9-110.smtp-out.amazonses.com
[54.240.9.110]:49199 because of notquit: command-timeout (2.6/1h max:1.2)"
2014-09-15 12:49:50 SMTP command timeout on TLS connection from
a9-41.smtp-out.amazonses.com [54.240.9.41]:39221
2014-09-15 12:50:22 H=a9-91.smtp-out.amazonses.com [54.240.9.91]:38738
Warning: Sender rate 3.6 / 1h
On 9/15/2014 12:33 PM, Animal Farm wrote:
--- [ "Chuck McCown" <[email protected]> wrote ]
-----------------------------------
Guys, Paul is doing this out of the goodness of his heart too. This ain't
exactly a profit center for him. Please be kind.
-----Original Message----- From: Animal Farm
Sent: Monday, September 15, 2014 10:08 AM
To: [email protected]
Subject: Re: [AFMUG] spam
--- [ Paul McCall <[email protected]> wrote ]
-----------------------------------
George,
Please be aware that we are looking at ALL of this actively. I am not
going to post every 30 seconds to respond to every individual post, but
there are 2 people in our office "on it" and we will work through whatever
issues are there, make adjustments as needed. First glance at the "thread
headers" issue is that the only two "standard options" within Mailman for
this, are indeed set to initiate that.
Amazon does not have a "list server". Amazon is a complete development
environment yet it is a "blank slate".
Again, please be patient... breathe :)
Paul
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, September 15, 2014 12:02 PM
To: Paul McCall
Subject: Re: [AFMUG] spam
--- [ "George Skorup (Cyber Broadcasting)" <[email protected]> wrote ]
-----------------------------------
Plus messages are extremely delayed. And I'll get replies to stuff before
I see my own post.
Oh, I see Amazon list serv is Mailman. Maybe there's some options to
tweak?
On 9/15/2014 10:49 AM, Animal Farm wrote:
--- [ "George Skorup (Cyber Broadcasting)" <[email protected]> wrote ]
-----------------------------------
Thunderbird, which only looks at the thread headers. I believe Gmail
figures it out by subject as well as the thread header. And I don't
really want to move my list subscriptions to my Google Apps email.
It looks like the first message of a new thread/subject does not have
any Thread headers. The message Ken sent a little while ago about
surge suppression between a SyncInjector and SyncPipe did not have
thread headers. But any replies seem to get the them. Nope, I take
that back. The two replies to the Official Announcement subject from
Jaime and Forrest do not have thread headers. Is the client stripping
them, or is it the list server? Seems it's the list server because
that's the only thing that changed. Sorry to be a PITA, but this is
highly annoying.
On 9/15/2014 10:09 AM, Animal Farm wrote:
--- [ Paul McCall <[email protected]> wrote ]
-----------------------------------
George,
What client are you using that would seem to not be working right
with threads? I only use Outlook and Gmail and it seems to be
working right for both of those.
Paul
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Monday, September 15, 2014 11:06 AM
To: Paul McCall
Subject: Re: [AFMUG] spam
--- [ "George Skorup (Cyber Broadcasting)" <[email protected]> wrote
]
-----------------------------------
Put it back the way it was.... (yes, I know, I read the other thread,
but I don't have to like it).
And it looks like threads are broken or the thread ID header is
nonexistent.
#IHateMondays
#IDontDoHashTags
On 9/15/2014 9:50 AM, Animal Farm wrote:
--- [ Adam Moffett <[email protected]> wrote ]
-----------------------------------
I think some dude named Animal Farm is spamming the list
