I need to know the status on DSPAM, as Dec. 1st is in 5 days. I will be losing a client or 2 if this does not go into effect, as I have held on to them telling them to give me 3 weeks to get this in place. Dec 1st is 3 weeks and this is the date you guys told us.
The dspam developer has access to the dspam servers and is working on it, but we just came out of a holiday time that Yash was not taking into account when giving the times. We have progress but not yet ready to deploy system-wide.
the system is up. But I can’t commit on when it will be ready for system-wide use.
We will however start allowing customers/resellers from next week to start using the filtering system. You’d need to make a small change in the MX records for it to work.
The ability to make this system-wide rests on 3rd party HSphere contractors we are working with to implement certain HSphere changes that can make this possible. I am hopefull to have something within 1 week, but with software development it can stretch into 3 weeks.
The huge issue is inbound and outbound SMTP traffic are one the same IP. All your email is delivered to the same IP, and when you connect to the SMTP server to send email, its on the same IP. We have 2 different approaches to get this fixed. One is modifying HSphere templates and software to insert a different MX record for each mail server, and rebuild the DNS system. The second approach we are working on is buiding a layer7 proxy server that can untangle inbound and outbound traffic.
We have done a bit of ham and spam training and put the first live domains on it, there is a bug with it mangling html formatted emil tht we are working out before making the tests more open.
WebD, do you want mail that is formatted crazy if it has HTML?
Well that has been fixed. We can putyour client on dspam now, but you may have some bugs, we can work them out by we are trying to find BEFORE putting clients on them.
Aslo the reason for more spam, is becasue a major RBL is down, it was taking all the mailservers down trying to reach it this morning.
IT was a good RBL that stopped much spam.
When RBLS go down it makes the SMTP sessions timeout trying to find the RBL server, so it is a bit of a catch 22 in that, we will verify if it is up and re-add that RBL here later.
the RBL blocked virus infected PCs and trojaned PCs specifically, so the botnets can again hammer away with spam. Not good, but we can’t control that without something like this RBL.