Enter hostname or ip: mail.aptn.ca Enter port (25 or 11025) [25]: 25
You are about to connect to mail.aptn.ca on port 25. connecting to host mail.aptn.ca (139.142.213.125), port 25 connection open 220 mail.aptn.ca Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 28 May 2008 15:24:11 -0500 helo shaw.ca 250 mail.aptn.ca Hello [64.59.134.9] mail from: <[EMAIL PROTECTED]> 550 Message rejected because of RBL policy Exactly! There it is....Shaw has been blacklisted by SORBS... On Wed, May 28, 2008 at 4:36 PM, Don Andrews <[EMAIL PROTECTED]> wrote: > That IP seems to be on some DNSBLs. > > > ------------------------------ > > *From:* Steve Ens [mailto:[EMAIL PROTECTED] > *Sent:* Wednesday, May 28, 2008 2:24 PM > *To:* MS-Exchange Admin Issues > *Subject:* Re: 4.4.7 > > The admin at the ISP in question is saying that it is my mail server that > is blocking mail from the 64.59.134.9. address. I've checked far and wide > in ESM and cannot see anywhere that this could be happening. Any good ideas > to look? The spam filter is not blocking them, otherwise they wouldn't get > a NDR, it must be somewhere in Exchange? He said they use two IP's to send > all of their mail, one of them works fine...which he says accounts for 70% > of their mail. Hence most mail gets through to us. > > On Tue, May 27, 2008 at 9:56 AM, Steve Ens <[EMAIL PROTECTED]> wrote: > > Yah the message does come from her mail server, not ours. It's odd since > we get messages from other people from Shaw. > According to the error codes, she has entered the correct email addresses. > I could call Shaw to check it out and see what their support people say. > > On Tue, May 27, 2008 at 9:53 AM, Micheal Espinola Jr < > [EMAIL PROTECTED]> wrote: > > Not true. That message is supposed to come from her own mail server - > not yours. Its a Delivery Status Notification (DSN) that indicates > that her mail server was unable to complete an SMTP transaction with > yours. So, this message comes from her server - not yours. > > Based on on the original e-mail and this bounce, are/is you/she > positive that she is sending to the correct recipient? > > If yes, then SMTP tests should be performed between her server and > yours. A basic telnet test (against ports 25) should suffice in > determining if basic SMTP connectivity is possible. > > If that's good, then another possibility to check is *your* spam > filter logs to see if you are greylisting (delaying) connections from > her server. There are mail domains that are known to handle > greylisting well because of rotating egress mail servers (with > different IPs), etc. > > > > > On Tue, May 27, 2008 at 10:33 AM, Steve Ens <[EMAIL PROTECTED]> wrote: > > One person trying to send messages into our org is getting these errors > > coming back... > > > > Original-recipient: rfc822;[EMAIL PROTECTED] > > Final-recipient: rfc822;[EMAIL PROTECTED] > > > > Action: delayed > > Status: 4.4.7 (unable to deliver this message after 1 day) > > > > Doesn't look like it's getting into our server at all, since that message > > comes back from her ISP. We get messages from other users at the ISP. > She > > can send messages to other people fine in other companies. I've > whitelisted > > her address in the spam filter, I've checked all my settings, it all > looks > > ok. Any suggestions? > > Thanks > > Steve > > > > > > > -- > ME2 > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ > ~ http://www.sunbeltsoftware.com/Ninja ~ > > > > > > > > > > > > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
