ESVA Website (global-domination.org) Down, 2010-March

Update 2010-08-07: Several updates of note pulled from the comments.

  • The main site and Andy are back, see the last few comments for more info.
  • Downloads of 2.0.5.7 are available, see the 2010-04-08 update at the end of this post.
  • Updates beyond 2.0.5.7 are not currently available, but people are working on it.
  • Most discussion should probably be moving to the ESVA Interim Forums at http://rbe1.de/ESVA
  • There is a semi-commercial fork of the project at ESVA.Libra.IT, there has been some controversy over it but the developers of that project are also involved in the discussions and further project work at the forums. It also has its own forum.

Update 2010-04-12: The problem is being worked on; read for details.

Just a note because I’ve been seeing searches hit my site looking for information on this.

The Email Security Virtual Appliance (ESVA) website is down, I do not have any information on why but it doesn’t appear to be a domain registration or DNS issue – it’s something on the hosting side. I’ve been unsuccessful in contacting the creator/maintainer of ESVA, but I wasn’t corresponding with him before so I don’t have a known-good email address – just two old ones that may not still be in use. He does travel for business and has disappeared from the ‘net in the past while doing so, so everything may be restored at any time if he’s simply out of contact.

Continue reading ESVA Website (global-domination.org) Down, 2010-March, Back 2010-July

(Fix) postfix: Recipient address rejected: Domain not found

We had a problem last weekend with Postfix not accepting email for a single domain when it was coming from outside our network, while messages from hosts on the local network were accepted and routed with no problems. Messages from outside the network were rejected with a 450 (temporary) code and the error message “Recipient address rejected: Domain not found”. The cause did end up being a DNS problem (apparently the most common kind of issue with Postfix), but not one that I would have expected (a missing host entry for the top-level domain, so example.com wouldn’t resolve even though mail.example.com did). Finding the source of the problem was complicated because of a set of several changes during a weekend maintenance window.

Continue reading (Fix) Postfix: Recipient address rejected: Domain not found

Email Marketing - Use A Service

I occasionally get requests from clients for assistance with sending out email marketing to their existing clients. My advice in these situations is always the same: Use A Service.

Every client that I’ve dealt with that’s interested in this kind of marketing starts out planning to do it using their regular email account, but there are good reasons not to do so. The reasons for using a service break down into three key areas: creation of your content, distribution of your content, and management of your address list. Keep reading for some notes on those.

Continue reading Email Marketing – Use A Service

Fix for Outlook 2007 Trying to Load InfoPath (Error 1605)

Just ran into this situation after a client uninstalled & reinstalled Office 2007 Pro. When Outlook was opened, it complained twice about being unable to open InfoPath because it wasn’t installed.

I found multiple other complaints about this, but no solutions (though some suggested removing and reinstalling Office). A bit of digging with SysInternals’ Process Monitor, turned up mention of not finding the somewhat promising value “DisableInfopathForms,” so I took a stab and created the value as a DWORD under the location ProcMon was reporting. Setting the value to 1 cleared the problem on Outlook startup.

Continue reading Fix for Outlook 2007 Trying to Load InfoPath (Error 1605)

NEVER Give Out Your Password

IF support staff for a service you are using need access to your account or information within it, they can get that access without needing your password. Nobody should be asking for your password.

This applies to email (e.g. Hotmail/Windows Live, Yahoo, Google and many others), social networking (Facebook, LinkedIn, MySpace, etc.), online photos (Flickr, etc.), and especially applies to your banking and finances. NO bank or financial services employee should ever ask for your password – bank policies generally prohibit them from doing so as a firing offense.

Think of someone asking for your password the same way you’d think about a stranger walking up to you on the street and saying “Hi, I’m with the village. I need your home address and your house keys.” No matter how friendly and professional looking, would you just give your keys to a stranger like that?

Continue reading NEVER Give Out Your Password