[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Independent Mail Server vs. RAQ Mail Routing



>.  The script generates 3
> separate emails (two to email addresses other than the clientdomain.com
and one
> email addressed to client@xxxxxxxxxxxxxxxx).  The two emails work
perfectly
> that are addressed to non-clientdomain.com addresses; however, the one
email
> addressed to client@xxxxxxxxxxxxxxxx fails and generates a variety of
errors
> (malformed header, etc.).  ANY use of a clientdomain.com email address in
this
> script fails.  The failure is specific to the clientdomain.com email
address as
> the other two emails are sent without error

I had a simialr problem on my Raq2 - the perl script in question would dump
out with excessive recursion. I only use my Raq for Web hosting (No Mail,
DNS, etc,)

If I telnet in and do :

sendmail -t
to: test@xxxxxxxxxxxxxxxx
from: a@xxxxx
Hello
.
(last line is a period on its own)

I see the error - Excesive recursion blah, blah

The only way we found to get round it was to uncheck the "collect email for
this domain" in the GUI. Which has the side effect of stopping
http://clientdomain.com from working (only the
http://hostname.clientname.com works)

I don't know whether these functions exist, or have been de-coupled on a
Raq3. Funny thing is, for a short time everything was peachy - but then my
colo company did some 'maintenance' on their DNS tables and it stopped
working. After much gnashing of teeth, they fixed it, and I asked them what
they did. They sent me this chunk config:

; Name Servers
;
clientdomain.com. IN      NS      <PRIMARYNAMESEVER>.
clientdomain.com. IN      NS      <SECONDARYNAMESERVER>.
;
; A Records for hosts
;
clientdomain.com.         IN      A       <IPADDRESS>
www.clientdomain.com.     IN      A       <IPADDRESS>
; Leave config pointing to two A records. -dja
;
; Mail Exchange Information
;
clientdomain.com. IN      MX      0       <PRIMARYNAMESERVER>.
clientdomain.com. IN      MX      10      <MAILSERVER>.

I know nothing about what it means :-) but every time they did more
"maintenance of their DNS tables", my email would stop working, and I'd send
them this, they'd copy and paste it, and it would work again.

Then one day, they broke it, and its never worked since, despite weeks and
weeks of trying. Good Luck, if you do find the answer, please post it :-)

Shaun


----- Original Message -----
From: <gary@xxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Cc: <gary@xxxxxxxxx>
Sent: Friday, February 23, 2001 12:26 PM
Subject: [cobalt-users] Independent Mail Server vs. RAQ Mail Routing


> Hello All.
>
> We have a somewhat puzzling email situation with only ONE of our website
that
> resides upon our remotely-hosted RAQ3.  I think I am begining to see the
> problem cause BUT would value your comments.  The current scenario is as
> follows:
>
> 1.  Client has their own mail server (MS Exchange) at their locale which
is
> connected to the Internet via dedicated line and fixed IP address.
>
> 2.  Client desired backup email server and local telephone company (Telco)
> provides this service as a part of the dedicated IP address package.
>
> 3.  We worked with Telco (pretty much did as directed by Telco) to
establish
> DNS entries (via RAQ3 Control Panel/DNS) to establish the following
entries:
>
>
> A Record Entries:
>
> clientdomain.com      ==>  xx.xx.xxx.xx  (website IP address)
>
> www.clientdomain.com  ==>  xx.xx.xxx.xx  (website IP address)
>
> xx.xx.xxx.xx          ==>  clientdomain.com
>
>
> MX Entries:
>
> mail.clientdomain.com ==>  yyy.yyy.yyy.yyy (dedicated IP address to client
mail
> server)
>
> clientdomain.com      [Very High Priority Mail Server Setting] ==>
> mail.clientdomain.com
>
> clientdomain.com      [Very Low Priority Mail Server Setting]  ==>
> backupmail.telco.net  (Telco Backup Mail Server)
>
>
> Problem.
> Outside of the RAQ 3 environment, everything works fine.  The client
domain
> name resolves correctly and displays the website.  Email directed to valid
> clientdomain.com addresses route okay to the client's mail server.  If the
> client's mail server is down, the Telco's backup mail server catches the
email
> and delivers when the client mail server is back up.
>
> The problem comes when operating within the RAQ3 environment.  We have a
simple
> PERL script (loaded within the clientdomain.com website) which processes
output
> from a web form on the clientdomain.com website.  We use this same PERL
script
> on many other websites on the RAQ3 without any problem.  The script
generates 3
> separate emails (two to email addresses other than the clientdomain.com
and one
> email addressed to client@xxxxxxxxxxxxxxxx).  The two emails work
perfectly
> that are addressed to non-clientdomain.com addresses; however, the one
email
> addressed to client@xxxxxxxxxxxxxxxx fails and generates a variety of
errors
> (malformed header, etc.).  ANY use of a clientdomain.com email address in
this
> script fails.  The failure is specific to the clientdomain.com email
address as
> the other two emails are sent without error.
>
> Summary.
> I suspect that somehow the combination of DNS/Mail Server entries
"confuse" the
> RAQ3's internal mail routings for clientdomain.com.  I need to continue to
use
> the web form on clientdomain.com.  Is there a simple adjustment?  May I
have
> your comments and recommendations?
>
> Thank you.
>
> Gary Ownsby
>
>
>
> --------------------------------------------------------------------------
-
> This message was sent by Web Mail from Smoky Mountain Webs Client
Services.
> --------------------------------------------------------------------------
-
> http://www.smokymountainwebs.com/
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>