Local mail exchange and remote website? FIXED
Sandeep Bains
sandebains at gmail.com
Mon Oct 18 10:36:04 MST 2010
I'm still bit puzzled on this. I think that the domain has no MX records
listed and it is working with A record only
Or if as per the email; MX was pointing to a CNAME and now it is pointing to
A?
If things were wrong (as per your old configuration), where were those
emails going to (in case you haven't made any changes on the system, they
should had been accepted)....
It will be interesting to see all the resource records for the domain.
As per the RFC the resolution should take place the following way
Once an SMTP client lexically identifies a domain to which mail will
be delivered for processing (as described in sections 3.6 and 3.7), a
DNS lookup MUST be performed to resolve the domain name [22]. The
names are expected to be fully-qualified domain names (FQDNs):
mechanisms for inferring FQDNs from partial names or local aliases
are outside of this specification and, due to a history of problems,
are generally discouraged. The lookup first attempts to locate an MX
record associated with the name. If a CNAME record is found instead,
the resulting name is processed as if it were the initial name. If
no MX records are found, but an A RR is found, the A RR is treated as
if it was associated with an implicit MX RR, with a preference of 0,
pointing to that host. If one or more MX RRs are found for a given
name, SMTP systems MUST NOT utilize any A RRs associated with that
name unless they are located using the MX RRs; the "implicit MX" rule
above applies only if there are no MX records present. If MX records
are present, but none of them are usable, this situation MUST be
reported as an error.
Thanks,
Sandeep
On Mon, Oct 18, 2010 at 9:28 AM, Eric Shubert <ejs at shubes.net> wrote:
> Just to be as clear as possible, I'm basing that statement on this:
> http://www.dyndns.com/suppor/kb/getting_email_with_custom_dns.html#case3
> I don't know if this is just a DynDNS requirement or not, but I expect that
> it's at least a good practice if those guys require it. DynDNS knows their
> stuff when it comes to DNS. ;)
> --
> -Eric 'shubes'
>
>
> On 10/18/2010 09:17 AM, Tom Ostlund wrote:
>
>> Thanks "Shubes"
>>
>> I appreciate it.
>>
>> It is weird that it is that way. I was looking at my unmodified locally
>> hosted accounts and they are all pointing to a cname. None of them have
>> any issues.
>>
>> Go figure. That will be for the next linux meeting!
>>
>> Toodles!
>>
>> Tom
>>
>>
>>
>> On Mon, 2010-10-18 at 08:52 -0700, Eric Shubert wrote:
>>
>>> MX records must point to type A records, not CNAME records. It sounds
>>> like this was your problem. You might suggest to the WHM developers that
>>> they edit for such misconfigurations.
>>>
>>> This certainly does not appear to be related to the error message you
>>> originally posted. Sometimes error messages aren't indicative of the
>>> real problem though.
>>>
>>> On 10/18/2010 08:36 AM, Tom Ostlund wrote:
>>> >
>>> > In WHM under the DNS Functions, changing
>>> >
>>> > mail 301 in cname websitename.com --> to --> mail 14400 in A
>>> IP_ADDRESS
>>> > is the change that needed to be made.
>>> >
>>> > Now it all works.
>>> >
>>> > Thanks to all
>>> >
>>> > Tom
>>> >
>>> > On Mon, 2010-10-18 at 08:28 -0700, Tom Ostlund wrote:
>>> >> Hello All,
>>> >>
>>> >> My problem relates to receiving mail. It gets returned with that
>>> error
>>> >> message that I posted.
>>> >>
>>> >> I am so frustrated. All because the company that gave me a free site
>>> >> for two years did it in asp... ugh!
>>> >>
>>> >> Thanks all for your help, I am still looking for the correct entries
>>> >> to have the mail exchange local and the site hosted on a different ip
>>> >> address.
>>> >>
>>> >> Thanks
>>> >> Tom
>>> >>
>>> >> On Mon, 2010-10-18 at 08:14 -0700, Eric Shubert wrote:
>>> >>> On 10/18/2010 07:55 AM, Lisa Kachold wrote:
>>> >>> > HI Tom;
>>> >>> >
>>> >>> > These guys are correct, your mail server is not exchanging any
>>> >>> > authentication but expecting it.
>>> >>> >
>>> >>> > WHM and Cpanel use different mail tools depending in what
>>> exactly is
>>> >>> > available and embraced/installed by your hoster.
>>> >>> >
>>> >>> > http://www.cpanel.net/products/cpanelwhm/features.html
>>> >>> >
>>> >>> > If you have it, use the WHM mail troubleshooter:
>>> >>> >
>>> >>> >
>>> http://www.webhostingresourcekit.com/flash/whm/whm10_x_mail.html
>>> >>> >
>>> >>> > Most web hosters use the WHM mail tool because of the many
>>> issues with
>>> >>> > insecure mail scripts cgi hacked. This simply means that your
>>> server is
>>> >>> > sending mail FROM ITSELF (not necessarily for/to the domain)
>>> using WHM.
>>> >>> >
>>> >>> > 1) MX for your domain (so that your new server will be used for
>>> MAIL
>>> >>> > XFER [if you are already using another mail service and have a 0
>>> or 1
>>> >>> > priority MX record, just add a second MX for your offsite mailer
>>> IP
>>> >>> > machinename (which MUST match the reverse in-addr-arpa IP
>>> address and
>>> >>> > name the server presents itself as PER the RFC)]
>>> >>> >
>>> >>> > http://www.gregrobert.com/mxsetup.php
>>> >>>
>>> >>> Sorry Lisa, but I think you're off base here. If I understand Matt's
>>> >>> situation correctly, he's having a problem sending email. MX records
>>> >>> only come into play for receiving email. You can send all day long
>>> with
>>> >>> no MX record(s) at all. ;) He shouldn't need to touch any DNS MX
>>> >>> configuration. Of course, the destination/recipient domains would
>>> need
>>> >>> appropriate DNS MX records.
>>> >>>
>>> >>> > 2) Mailer to allow specific IP addresses to access and relay
>>> without
>>> >>> > authentication.
>>> >>> >
>>> >>> > If you find you are not using WHM, but have another mail server,
>>> it's
>>> >>> > going to be configurable within Cpanel or WHM also.
>>> >>> >
>>> >>> > This is generally in /etc/mail or /etc/postfix and is usually
>>> called
>>> >>> > *relay* something. But refer to specific documentation for your
>>> mail
>>> >>> > transport tool.
>>> >>> >
>>> >>> > I.E. google"How do I configure relay hosts in postfix" for
>>> instance.
>>> >>> > GoDaddy does have ssh or ftp. You can change configuration
>>> files with
>>> >>> > ftp, where you generally would be vim editing the file and
>>> restarting
>>> >>> > the mail daemon. Generally CPanel and WHM have tools to manage
>>> >>> > everything available on the server.
>>> >>> >
>>> >>> > I am familiar with setting up Cpanel and WHM on servers as well
>>> as
>>> >>> > working within them for various shops through the years. If you
>>> have
>>> >>> > questions you can email or call me off list.
>>> >>> >
>>> >>> > So much of the specifics of your hoster are guessed by us,
>>> wouldn't this
>>> >>> > question best be crafted and packaged for their support email or
>>> process?
>>> >>> >
>>> >>>
>>> >>> This part's right on. ;)
>>> >>>
>>> >>
>>> >> ---------------------------------------------------
>>> >> PLUG-discuss mailing list-PLUG-discuss at lists.plug.phoenix.az.us <mailto:
>>> -PLUG-discuss at lists.plug.phoenix.az.us> <mailto:
>>> PLUG-discuss at lists.plug.phoenix.az.us>
>>>
>>> >> To subscribe, unsubscribe, or to change your mail settings:
>>> >> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>> >
>>>
>>>
>>>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.PLUG.phoenix.az.us/pipermail/plug-discuss/attachments/20101018/0425830a/attachment.html>
More information about the PLUG-discuss
mailing list