TOPIC:

I am having issues with email that I am sending from my Dreamhost account into the FTH system. Below is one of the bounce messages that I got. From the FTH end, does all of this information look correct? I can followup with Dreamhost, but I am not sure exactly what to say...


<This email address is being protected from spambots. You need JavaScript enabled to view it.>: connect to
mail.toastmastersclubs.org[50.19.253.65]:25: Connection timed out
Reporting-MTA: dns; hapkido.dreamhost.com
X-Postfix-Queue-ID: A1623DCB77
X-Postfix-Sender: rfc822; This email address is being protected from spambots. You need JavaScript enabled to view it.
Arrival-Date: Wed, 5 Mar 2014 17:03:18 -0800 (PST)

Final-Recipient: rfc822; This email address is being protected from spambots. You need JavaScript enabled to view it.
Original-Recipient: rfc822;This email address is being protected from spambots. You need JavaScript enabled to view it.
Action: failed
Status: 4.4.1
Diagnostic-Code: X-Postfix; connect to
mail.toastmastersclubs.org[50.19.253.65]:25: Connection timed out

Resent-From: Randall Million <This email address is being protected from spambots. You need JavaScript enabled to view it.>
From: Randall Million <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Subject: Speaker Needed
Date: March 4, 2014 at 8:27:13 PM EST
Resent-To: Woodman Toastmasters <This email address is being protected from spambots. You need JavaScript enabled to view it.>
To: Woodman Toastmasters <This email address is being protected from spambots. You need JavaScript enabled to view it.>

Servers in the dreamhost network have been compromised and we have blocked them. You should be able to send email now.

Did this affect sending to FTH or receiving from FTH or both?

Both, sending and receiving.

I have looked, but haven't yet found any information about this compromise. Can you post a link about this (so I can see if I need to take further action)?

Besides realizing that I stopped getting email, was there a way I should have been able to realize that my account was blocked? Our club depends almost exclusively on the email list services to communicate about meetings and I found out because I wasn't getting the emails I was sending out as Toastmaster for the week.

There is no post, multiple server from dreamhost attacked our server. This seems to be the way of the future hosting companies do not monitor what happens on the servers they rent/lease nor do they do anything in the way of insisting that the client servers be kept up to date and have active malware and virus protection, and that all the client applications be kept secure. We do not and will not advertise for a hosting company whether is be a good or poor reviews.

DeltaTee wrote:

Besides realizing that I stopped getting email, was there a way I should have been able to realize that my account was blocked? Our club depends almost exclusively on the email list services to communicate about meetings and I found out because I wasn't getting the emails I was sending out as Toastmaster for the week.

While I am kind of new at understanding how a lot of this works, I would offer that I think the only point in this process at which emails to clubs are discerned as distinct from the general mass of emails coming to/going from the server is in the FTH email handler code. The email handler code does see system/server emails, some of which might be of the "Mail Undeliverable" type coming from outside the email handler code, but I am not sure that we currently have a good way to tie all of those back to clubs since some of the original sender identification may be lost in transit for those types of emails. In other words, this is the situation of the bounce not being generated by the email handler itself. I can look if there might be a way to use one or more additional header fields to store the original email sender address for these types of situations but I do not know that there is a quick solution.

Brian wrote:

There is no post, multiple server from dreamhost attacked our server. This seems to be the way of the future hosting companies do not monitor what happens on the servers they rent/lease nor do they do anything in the way of insisting that the client servers be kept up to date and have active malware and virus protection, and that all the client applications be kept secure. We do not and will not advertise for a hosting company whether is be a good or poor reviews.

Given the situation, I can understand your frustration. As a Dream host customer, is there anything that I can do to help improve the situation?

Just make sure the server you are on is up-to-date and the applications you use are kept up-to-date

I try to keep on top of the applications that I am running and make sure they are current. How can I help persuade the others on the shared server to do the same? (I don't think that it was my account that attacked the servers, but I still have the consequences if some one else in the network does.)

It is the company running the servers that must do that no you.