From: Ambictus on

'Ace Fekay [MCT Wrote:
> ;4728352']"Ambictus" <Ambictus.438x7d(a)DoNotSpam.com> wrote in message
> news:Ambictus.438x7d(a)DoNotSpam.com...
> >
> > 'Ace Fekay [MCT Wrote:
> >> ;4727587']"Ambictus" <Ambictus.4375be(a)DoNotSpam.com> wrote in
> message
> >> news:Ambictus.4375be(a)DoNotSpam.com...
> >> >
> >> > Ok, so for the last several days or so I've been experiencing a
> >> problem
> >> > with my SBS 2003 server. I've been getting a lot of messages
> bounced
> >> > back stating that relaying is denied. After a lot of searching
> and
> >> > attempting multiple fixes I believe I've discovered the problem,
> but
> >> am
> >> > unsure of how to fix it.
> >> >
> >> > First let me state that I'm completely baffled as to why it
> started
> >> > happening. I have made no changes in IP or DNS nor have I patched
> >> the
> >> > server or changed the config.
> >> >
> >> > It seems that my server is either attempting to deliver messages
> to
> >> the
> >> > wrong servers or is simply attempting to use those servers to
> relay
> >> our
> >> > messages to the proper server. The issue only occurs when a
> message
> >> is
> >> > sent to multiple recipients.
> >> >
> >> > So I believe our server opens a connection to the first
> recipient's
> >> > server and simply attempts to hand off the messages for all
> >> recipients.
> >> > Below are a couple of examples of the errors from the event
> viewer.
> >> >
> >> > This is an SMTP protocol error log for virtual server ID 1,
> >> connection
> >> > #61. The remote host "X.X.X.X", responded to the SMTP command
> "rcpt"
> >> > with "550-5.1.1 The email account that you tried to reach does
> not
> >> > exist. Please try 550-5.1.1 double-checking the recipient's
> email
> >> > address for typos or 550-5.1.1 unnecessary spaces. Learn more at
> >> > 550 5.1.1
> >> > http://mail.google.com/support/bin/answer.py?answer=6596
> >> > 2si525366qyk.111 ". The full command sent was "RCPT TO:<X(a)X.com>
> >> ".
> >> > This will probably cause the connection to fail.
> >> >
> >> >
> >> > This is an SMTP protocol error log for virtual server ID 1,
> >> connection
> >> > #62. The remote host "X.X.X.X", responded to the SMTP command
> "rcpt"
> >> > with "550 5.7.1 Relaying denied ". The full command sent was
> "RCPT
> >> > TO:<X(a)X.com> ". This will probably cause the connection to
> fail.
> >> >
> >> > Also I'm not using a smart host.
> >> >
> >> >
> >> > --
> >> > Ambictus
> >>
> >>
> >> The first error clearly states the recipient does not exist.
> >>
> >> As for the second one, there can be a number of causes as stated in
> >> the
> >> following:
> >>
> >> 'Relaying Denied' Error while trying to send emailDescription, User
> >> receives
> >> the following error when trying to send Email:
> >> javax.mail.SendFailedException: 550 5.7.1 <name(a)company.com>...
> >> Relaying
> >> denied ...
> >> www.hiteksoftware.com/knowledge/articles/026.htm
> >>
> >> My feeling is your IP may be on a blacklist. Check MX Toolbox's
> site.
> >>
> >> Email Blacklist Check - See if your server is blacklisted.
> >> Online email blacklist lookup check to find out if email server is
> on
> >> any
> >> real-time blacklist, spam blacklist or DNS black list commonly used
> to
> >> block
> >> email ...
> >> www.mxtoolbox.com/blacklists.aspx
> >>
> >>
> >> --
> >> Ace
> >>
> >> This posting is provided "AS-IS" with no warranties or guarantees
> and
> >> confers no rights.
> >>
> >> Please reply back to the newsgroup or forum for collaboration
> benefit
> >> among
> >> responding engineers, and to help others benefit from your
> resolution.
> >>
> >> Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> >> MCSA
> >> 2003/2000, MCSA Messaging 2003
> >> Microsoft Certified Trainer
> >>
> >> For urgent issues, please contact Microsoft PSS directly. Please
> check
> >> http://support.microsoft.com for regional support phone numbers.
> >
> > The reason the first recipient does not exist is because it's
> handing
> > the e-mail message to the wrong server. I suppose I should have just
> > posted the full messages so they would be more clear. In the first
> > message it is trying to send a message for user(a)wavelink.com to
> > gmail.com's servers therefore the user does not exist.
> >
> > I'm not blacklisted on any sites, I've tried multiple tools the one
> you
> > linked included.
> >
> >
> > In response to the Best Practices there were just some minor things
> > like no size limits and virtual memory is greater than physical.
> There
> > was also one about the recipient update service having an outdated
> > entry. But it has been that way since the server was first created
> in
> > 2007. At this point I'm looking to setup a smart host to temporarily
> > alleviate the problem and when the company breaks for Christmas I'll
> > come in and re-install the server. I just can't seem to find any
> real
> > cause.
> >
>
> So you are saying that wavelink.com is being hosted by Gmail? If that
> is
> the case, then assuming that, then the MX records for wavelink.com
> should be
> pointing to Gmail's MTAs. However, I just checked and found that
> wavelink.com's MX records are the following:
>
> wavelink.com MX preference = 10, mail exchanger =
> smtp1.mke.securence.com
> wavelink.com MX preference = 10, mail exchanger =
> smtp1.msp.securence.com
>
> Therfore, based on the above, I am not sure what you mean by your
> statement:
> > "The reason the first recipient does not exist is because it's
> handing
> > the e-mail message to the wrong server."
>
> As for the following statement, I am not sure what you mean by it
> should be
> going to Gmail's mail servers. Maybe I am missing something here? My
> MX
> lookup for wavelink.com do not indicate any of the Gmail severs.
> > "In the first
> > message it is trying to send a message for user(a)wavelink.com to
> > gmail.com's servers therefore the user does not exist."
>
> Also, I am glad to hear you are not on any blacklists.
>
> Ace

I really am unsure of how to describe the exact situation... It's such
a confusing problem.

Wavelink.com is NOT hosted by gmail.com but my server doesn't seem to
care. It simply gave gmail.com wavelink.com's messages. Wavelink.com
hosts their own server in-house.

I guess the best way I can describe this is that my server doesn't
attempt to send out messages to individual servers. What it does is take
an e-mail, contact the first server in the e-mail's list of recipients
and simply hands off the messages for all recipients regardless of their
domain. Almost like some kind of dynamic smart host in that it assumes
the first server it contacts is a smart host for it to relay messages
through. It's exceptionally weird.

Thanks for all your ideas but I've just decided to set up a temporary
smart host and once we break for christmas/new years vacation come
reinstall everything on the machine. It's gonna suck but at least all my
settings will be fresh.


--
Ambictus
------------------------------------------------------------------------
Ambictus's Profile: http://forums.techarena.in/members/163907.htm
View this thread: http://forums.techarena.in/small-business-server/1282271.htm

http://forums.techarena.in

From: Ace Fekay [MCT] on
"Ambictus" <Ambictus.4395ja(a)DoNotSpam.com> wrote in message
news:Ambictus.4395ja(a)DoNotSpam.com...
>
> I really am unsure of how to describe the exact situation... It's such
> a confusing problem.
>
> Wavelink.com is NOT hosted by gmail.com but my server doesn't seem to
> care. It simply gave gmail.com wavelink.com's messages. Wavelink.com
> hosts their own server in-house.
>
> I guess the best way I can describe this is that my server doesn't
> attempt to send out messages to individual servers. What it does is take
> an e-mail, contact the first server in the e-mail's list of recipients
> and simply hands off the messages for all recipients regardless of their
> domain. Almost like some kind of dynamic smart host in that it assumes
> the first server it contacts is a smart host for it to relay messages
> through. It's exceptionally weird.
>
> Thanks for all your ideas but I've just decided to set up a temporary
> smart host and once we break for christmas/new years vacation come
> reinstall everything on the machine. It's gonna suck but at least all my
> settings will be fresh.
>


With all due respect, and I apologize, but what you stated doesn't make one
bit of sense.

Basically an Exchange (or any other mail server) if authorized to receive
mail for a specific domain name, such as wavelink.com, will receive mail for
that domain name, provided the MX records are pointing to it, or to an SMTP
gateway (whether an appliance device on your network such as Barrcuda Spam
Killer, Iron Mail, etc), or if the MX records are pointed to a third part
spam solution such as Postini, which then forwards (relays) the email to
your server.

Now if you are using the SBS POP3 connector, then that means that emails for
wavelink.com are being sent to your ISP hosting solution first (the MX
records are pointed to the ISP's), and the POP3 connector pulls from the
ISP.

Good luck with your solution. Let us know if it works after the holidays.
Also, curious if you can elaborate on the above.

Thanks,

Ace


From: Ambictus on

'Ace Fekay [MCT Wrote:
> ;4728514']"Ambictus" <Ambictus.4395ja(a)DoNotSpam.com> wrote in message
> news:Ambictus.4395ja(a)DoNotSpam.com...
> >
> > I really am unsure of how to describe the exact situation... It's
> such
> > a confusing problem.
> >
> > Wavelink.com is NOT hosted by gmail.com but my server doesn't seem
> to
> > care. It simply gave gmail.com wavelink.com's messages. Wavelink.com
> > hosts their own server in-house.
> >
> > I guess the best way I can describe this is that my server doesn't
> > attempt to send out messages to individual servers. What it does is
> take
> > an e-mail, contact the first server in the e-mail's list of
> recipients
> > and simply hands off the messages for all recipients regardless of
> their
> > domain. Almost like some kind of dynamic smart host in that it
> assumes
> > the first server it contacts is a smart host for it to relay
> messages
> > through. It's exceptionally weird.
> >
> > Thanks for all your ideas but I've just decided to set up a
> temporary
> > smart host and once we break for christmas/new years vacation come
> > reinstall everything on the machine. It's gonna suck but at least all
> my
> > settings will be fresh.
> >
>
>
> With all due respect, and I apologize, but what you stated doesn't make
> one
> bit of sense.
>
> Basically an Exchange (or any other mail server) if authorized to
> receive
> mail for a specific domain name, such as wavelink.com, will receive
> mail for
> that domain name, provided the MX records are pointing to it, or to an
> SMTP
> gateway (whether an appliance device on your network such as Barrcuda
> Spam
> Killer, Iron Mail, etc), or if the MX records are pointed to a third
> part
> spam solution such as Postini, which then forwards (relays) the email
> to
> your server.
>
> Now if you are using the SBS POP3 connector, then that means that
> emails for
> wavelink.com are being sent to your ISP hosting solution first (the MX
> records are pointed to the ISP's), and the POP3 connector pulls from
> the
> ISP.
>
> Good luck with your solution. Let us know if it works after the
> holidays.
> Also, curious if you can elaborate on the above.
>
> Thanks,
>
> Ace

After reviewing the logs a bit more carefully it seems I might be a
little off in what is exactly happening. Here's an example of what is
happening.

An e-mail is sent to user(a)bankofutah.com, user(a)imail.org, user(a)aol.com,
user(a)heart.org and user(a)quiznossub.com.

Below what I've done is given the IP address of the rejecting server,
the user's e-mail address that was rejected and what the IP address
resolves to.

user(a)quiznossub.com = 64.18.7.10 - s8a1.psmtp.com

user(a)heart.org = 166.70.204.242 - exoro-pdc.exoro.com

user(a)aol.com = 204.200.196.106 - jibe2.jibehost.com

user(a)imail.org = 208.177.146.78 - mailmx.lhmse.com

user(a)bankofutah.com = 98.137.54.237 - mta-v1.mail.vip.sp2.yahoo.com


So I guess it more seems like there is some SERIOUSLY crosswired DNS
going on. However that can't really be the case because if the e-mail
was sent to each person individually they would have gotten the e-mail.


--
Ambictus
------------------------------------------------------------------------
Ambictus's Profile: http://forums.techarena.in/members/163907.htm
View this thread: http://forums.techarena.in/small-business-server/1282271.htm

http://forums.techarena.in

From: Ace Fekay [MCT] on
"Ambictus" <Ambictus.439b3b(a)DoNotSpam.com> wrote in message
news:Ambictus.439b3b(a)DoNotSpam.com...
>
> 'Ace Fekay [MCT Wrote:
>> ;4728514']"Ambictus" <Ambictus.4395ja(a)DoNotSpam.com> wrote in message
>> news:Ambictus.4395ja(a)DoNotSpam.com...
>> >
>> > I really am unsure of how to describe the exact situation... It's
>> such
>> > a confusing problem.
>> >
>> > Wavelink.com is NOT hosted by gmail.com but my server doesn't seem
>> to
>> > care. It simply gave gmail.com wavelink.com's messages. Wavelink.com
>> > hosts their own server in-house.
>> >
>> > I guess the best way I can describe this is that my server doesn't
>> > attempt to send out messages to individual servers. What it does is
>> take
>> > an e-mail, contact the first server in the e-mail's list of
>> recipients
>> > and simply hands off the messages for all recipients regardless of
>> their
>> > domain. Almost like some kind of dynamic smart host in that it
>> assumes
>> > the first server it contacts is a smart host for it to relay
>> messages
>> > through. It's exceptionally weird.
>> >
>> > Thanks for all your ideas but I've just decided to set up a
>> temporary
>> > smart host and once we break for christmas/new years vacation come
>> > reinstall everything on the machine. It's gonna suck but at least all
>> my
>> > settings will be fresh.
>> >
>>
>>
>> With all due respect, and I apologize, but what you stated doesn't make
>> one
>> bit of sense.
>>
>> Basically an Exchange (or any other mail server) if authorized to
>> receive
>> mail for a specific domain name, such as wavelink.com, will receive
>> mail for
>> that domain name, provided the MX records are pointing to it, or to an
>> SMTP
>> gateway (whether an appliance device on your network such as Barrcuda
>> Spam
>> Killer, Iron Mail, etc), or if the MX records are pointed to a third
>> part
>> spam solution such as Postini, which then forwards (relays) the email
>> to
>> your server.
>>
>> Now if you are using the SBS POP3 connector, then that means that
>> emails for
>> wavelink.com are being sent to your ISP hosting solution first (the MX
>> records are pointed to the ISP's), and the POP3 connector pulls from
>> the
>> ISP.
>>
>> Good luck with your solution. Let us know if it works after the
>> holidays.
>> Also, curious if you can elaborate on the above.
>>
>> Thanks,
>>
>> Ace
>
> After reviewing the logs a bit more carefully it seems I might be a
> little off in what is exactly happening. Here's an example of what is
> happening.
>
> An e-mail is sent to user(a)bankofutah.com, user(a)imail.org, user(a)aol.com,
> user(a)heart.org and user(a)quiznossub.com.
>
> Below what I've done is given the IP address of the rejecting server,
> the user's e-mail address that was rejected and what the IP address
> resolves to.
>
> user(a)quiznossub.com = 64.18.7.10 - s8a1.psmtp.com
>
> user(a)heart.org = 166.70.204.242 - exoro-pdc.exoro.com
>
> user(a)aol.com = 204.200.196.106 - jibe2.jibehost.com
>
> user(a)imail.org = 208.177.146.78 - mailmx.lhmse.com
>
> user(a)bankofutah.com = 98.137.54.237 - mta-v1.mail.vip.sp2.yahoo.com
>
>
> So I guess it more seems like there is some SERIOUSLY crosswired DNS
> going on. However that can't really be the case because if the e-mail
> was sent to each person individually they would have gotten the e-mail.
>
>


Ok, just to make sure I get the facts correct, what is YOUR domain name you
are sending from? Is it wavelink.com?

And what is the IP address of YOUR mail server that is supposed to send
email?

I want to do a little more research in this for you. I already know the MX
records, if it is wavelink.com, however I need to know where mail is being
sent from. If it is being sent from your IP address at your office, but the
MX records are elsewhere, then what may be happening is you do not have an
SPF record that indicates your IP is authorized to send mail from your IP,
therefore NUMEROUS receivers are rejecting it because of this.

Ace



From: Ambictus on

'Ace Fekay [MCT Wrote:
> ;4728663']"Ambictus" <Ambictus.439b3b(a)DoNotSpam.com> wrote in message
> news:Ambictus.439b3b(a)DoNotSpam.com...
> >
> > 'Ace Fekay [MCT Wrote:
> >> ;4728514']"Ambictus" <Ambictus.4395ja(a)DoNotSpam.com> wrote in
> message
> >> news:Ambictus.4395ja(a)DoNotSpam.com...
> >> >
> >> > I really am unsure of how to describe the exact situation... It's
> >> such
> >> > a confusing problem.
> >> >
> >> > Wavelink.com is NOT hosted by gmail.com but my server doesn't
> seem
> >> to
> >> > care. It simply gave gmail.com wavelink.com's messages.
> Wavelink.com
> >> > hosts their own server in-house.
> >> >
> >> > I guess the best way I can describe this is that my server
> doesn't
> >> > attempt to send out messages to individual servers. What it does
> is
> >> take
> >> > an e-mail, contact the first server in the e-mail's list of
> >> recipients
> >> > and simply hands off the messages for all recipients regardless
> of
> >> their
> >> > domain. Almost like some kind of dynamic smart host in that it
> >> assumes
> >> > the first server it contacts is a smart host for it to relay
> >> messages
> >> > through. It's exceptionally weird.
> >> >
> >> > Thanks for all your ideas but I've just decided to set up a
> >> temporary
> >> > smart host and once we break for christmas/new years vacation
> come
> >> > reinstall everything on the machine. It's gonna suck but at least
> all
> >> my
> >> > settings will be fresh.
> >> >
> >>
> >>
> >> With all due respect, and I apologize, but what you stated doesn't
> make
> >> one
> >> bit of sense.
> >>
> >> Basically an Exchange (or any other mail server) if authorized to
> >> receive
> >> mail for a specific domain name, such as wavelink.com, will receive
> >> mail for
> >> that domain name, provided the MX records are pointing to it, or to
> an
> >> SMTP
> >> gateway (whether an appliance device on your network such as
> Barrcuda
> >> Spam
> >> Killer, Iron Mail, etc), or if the MX records are pointed to a
> third
> >> part
> >> spam solution such as Postini, which then forwards (relays) the
> email
> >> to
> >> your server.
> >>
> >> Now if you are using the SBS POP3 connector, then that means that
> >> emails for
> >> wavelink.com are being sent to your ISP hosting solution first (the
> MX
> >> records are pointed to the ISP's), and the POP3 connector pulls
> from
> >> the
> >> ISP.
> >>
> >> Good luck with your solution. Let us know if it works after the
> >> holidays.
> >> Also, curious if you can elaborate on the above.
> >>
> >> Thanks,
> >>
> >> Ace
> >
> > After reviewing the logs a bit more carefully it seems I might be a
> > little off in what is exactly happening. Here's an example of what
> is
> > happening.
> >
> > An e-mail is sent to user(a)bankofutah.com, user(a)imail.org,
> user(a)aol.com,
> > user(a)heart.org and user(a)quiznossub.com.
> >
> > Below what I've done is given the IP address of the rejecting
> server,
> > the user's e-mail address that was rejected and what the IP address
> > resolves to.
> >
> > user(a)quiznossub.com = 64.18.7.10 - s8a1.psmtp.com
> >
> > user(a)heart.org = 166.70.204.242 - exoro-pdc.exoro.com
> >
> > user(a)aol.com = 204.200.196.106 - jibe2.jibehost.com
> >
> > user(a)imail.org = 208.177.146.78 - mailmx.lhmse.com
> >
> > user(a)bankofutah.com = 98.137.54.237 - mta-v1.mail.vip.sp2.yahoo.com
> >
> >
> > So I guess it more seems like there is some SERIOUSLY crosswired DNS
> > going on. However that can't really be the case because if the
> e-mail
> > was sent to each person individually they would have gotten the
> e-mail.
> >
> >
>
>
> Ok, just to make sure I get the facts correct, what is YOUR domain name
> you
> are sending from? Is it wavelink.com?
>
> And what is the IP address of YOUR mail server that is supposed to
> send
> email?
>
> I want to do a little more research in this for you. I already know the
> MX
> records, if it is wavelink.com, however I need to know where mail is
> being
> sent from. If it is being sent from your IP address at your office, but
> the
> MX records are elsewhere, then what may be happening is you do not have
> an
> SPF record that indicates your IP is authorized to send mail from your
> IP,
> therefore NUMEROUS receivers are rejecting it because of this.
>
> Ace

Details details... Geez! :)

My domain is lovecomm.net
The server is: mail.lovecomm.net
Server IP: 64.55.41.211


--
Ambictus
------------------------------------------------------------------------
Ambictus's Profile: http://forums.techarena.in/members/163907.htm
View this thread: http://forums.techarena.in/small-business-server/1282271.htm

http://forums.techarena.in