Dspam??

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.

I hope this is still happening!

What is the status???

HELLO???

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.

What is the date Stephen, you guys cant give us dates and with our unhappy clients we have to change it.

what is the date now???

What concerns me, in the past you guys plan stuff and months goes by, I cant do this, I will have to find other options if this is the case.

1st week of december.

Ok thats still on schedule. Thanks.

I thought this was already answered.

I can wait until the 2nd or even 3rd week of December as long as it works well.:slight_smile:

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.

What about Comcast, is it still a current problem on servers?

We have disabled a number of forwards(and there are topics here with clients asking questions about why), and it has helped greatly.

In that topic Tanmaya explained why it is a problem.

Please provide me status of DSPAM, client as ask me.

should be available to customer on optional basis shortly (next 3 days)

Ok, thanks. I think I can save this client…

we are just training the spam filter with a public corpus of ham and spam..

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.

Not sure what happen with the spam, its been very good and catching most of the spam the last couple weeks.

Today, here we go again, tons and tons of spam.

I got ripped by a customer, what changes did you guys make???

ANd when is this DSPAM going in to effect, you guys told us 2 weeks ago it was going to be in effect, and I was afaird of this.

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.

:frowning:
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.

I knew somthing happen, casue today, spam got awful again today.

The last couple of weeks the spam has been caught and put in spam folder.

Will see if that list is back up now. It helps a lot, unless it is down then it hurts a lot in SMTP timeouts.