RE: Website link for 66.146.164.36
"Jacques Shake" <[email protected]>
| Newsgroups | gmane.mail.spam.dsbl.admin |
|---|---|
| Message-ID | <[email protected]> |
Dick, thanks for the quick response! Our Exchange Server person tells me he corrected both problems. Do you have a way to test to confirm it? I'm not sure that we have postmaster and abuse accounts set up on our exchange server, I will check when I'm back at the office and get that corrected as well if they don't already exist. I appreciate your assistance in getting us off your list, all of the other lists were much easier to get off of. Jack Jacques "Jack" Shake Tel: (619)448.3467 Cell: (619)708.3817 -----Original Message----- From: Dick Wesseling [mailto:[email protected]] Sent: Friday, February 24, 2006 5:54 PM To: [email protected] Cc: [email protected] Subject: Re: Website link for 66.146.164.36 <[email protected]> wrote: > I've managed to remove our mail server from every black list except > yours. It's been well over 7 days since you last trapped spam, don't > you automatically remove it like every other spam list? No, DSBL only removes upon explicit request from the postmaster or abuse desk responsible for a server. > I've tried to receive email at the admin addresses you have listed but > they don't work through my ISP. http://dsbl.org/faq-listed#notmine addresses this problem. Of course the preferred solution is to setup informative reverse DNS - such as mail.milleniasecurity.com - for your IP. > Please remove my mail server from your list; we've corrected the relay > problem that got us listed in the first place. The problem was not an open relay, but - worse - an open proxy. Proxies at unusual port addresses are a sure sign of virus infection. Did you fix that as well? > If you need to send a confirmation email, please use > [email protected] and info me at this email address. administrator@ is not a standard role account, postmaster@ and abuse@ are. The idea is that anybody on the Internet that receives spam through your system should be able to tack a standard role account onto the reverse name of your IP in order to contact the person responsible for the system.