ChangeIP.com Forums

I am getting reports from some of my contacts that my ChangeIP hosted mail address is sporadically disappearing. Has anyone else had this issue, and if so what was the solution? Below is the message the contacts get. Some are getting frustrated that they cannot reach me...

Your message did not reach some or all of the intended recipients.
Subject: The following recipient(s) could not be reached:
lbass@infrasys.com on 5/2/2005 11:53 PM
The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address. Check the address and try again.

< mx1s24dca.secure-24.net #2.1.0 smtp; 421 4.3.2 Greylisted; Send it once more (198.173.201.212 <ed.maes@atlastube.com>)>

Did you ever find a solution?

There has been no solution and the problem persists. I've had to move some of my contacts to other mail addresses supported by other ISPs.

I just got a response from ChangeIP to try turning on authentication for outgoing server. Haven't send enough emails today to see if it works.

Greylisting is a dumb idea. Spamming software exists that will automatically resend when prompted with greylist notification. I have no idea why ChangeIP installed this when it'll soon be useless.

I can't stand these SPAM filters. Problem is, ChangeIP installs them without notification and enables them by default. Funky things happen and we end up wasting time checking with the ISP, mobile phone data provider, MS Outlook... I went through this last time when I started getting email tagged [SPAM] in the subject line.

Thank you VERY MUCH for the posting. I'll try this also. I think this may fix the issue. As you said some warning would be helpful.

The spam filtering is an option on the mailboxes, you simply turn on or off the 'Instant Spam Filter' option within the mailbox settings. This will turn on and off that [Spam] and [SpamSA] flagging thats being done. If this is a backup domain you must email us and we will bypass it for your domain.

The greylisting seems to be causing problems with Exchange servers - they fail a message that receives a 4xx error when they should retry. Every other mail server on the planet uses RFC actions when they receive a 4xx response, don't tell me why ms decided to not retry a temporary failure message. Trust me, zombie spammers do not retry messages, their goal is to get as many messages out in as short of a time as they can. They never use a retry queue and they could care less about delivery notifications. Their mail goal, again, is to send as much crap as they can in the shortest time possible before that infected machine gets banned. We will remove the greylisted and make it a domain level option.

Sam