"Ambictus" <> wrote in message
news:...
>
> 'Ace Fekay [MCT Wrote:
>> ;4728663']"Ambictus" <> wrote in message
>> news:...
>> >
>> > 'Ace Fekay [MCT Wrote:
>> >> ;4728514']"Ambictus" <> wrote in
>> message
>> >> news:...
>> >> >
>> >> > 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 , ,
>> ,
>> > and .
>> >
>> > 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.
>> >
>> > = 64.18.7.10 - s8a1.psmtp.com
>> >
>> > = 166.70.204.242 - exoro-pdc.exoro.com
>> >
>> > = 204.200.196.106 - jibe2.jibehost.com
>> >
>> > = 208.177.146.78 - mailmx.lhmse.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
>
Thank you for the details. Can't figure this out without them. Does your
doctor ask for details when you go in with a problem?
Here's what I found:
==============
Non-authoritative answer:
lovecomm.net text =
"v=spf1 ip4:64.55.41.211 mx ptr ~all"
lovecomm.net internet address = 64.13.232.183
lovecomm.net MX preference = 10, mail exchanger = server94.appriver.com
lovecomm.net MX preference = 20, mail exchanger = server95.appriver.com
lovecomm.net
===============
Based on the above, and your post, it appears that your mail server in your
office is sending mail, but the MX records point elsewhere. You have an SPF
for 64.55.41.211, however it doesn't exactly describe your setup, based on
your posts. Try the following. It includes the appriver.com servers for you
MX in case you want to use it to send out (as a smarthost), at the same time
shows some systems that check to see if the sending IP is the same as the MX
or not (I've seen some companies block email from this type of setup such as
craig's list and others.
v=spf1 mx ptr ip4:64.55.41.211 mx:server94.appriver.com
mx:server95.appriver.com -all
Ace
Similar Threads
Linear Mode
