On Tue, 18 May 2004, Jeffrey Laramie wrote:
Morning All,
The last 2 days it appears my mail server has incorrectly forwarded (or at
least attempted to forward) a message to the wrong IP. This is on a system
that had been running for months without change. Some additional info:
SuSE 8.2
Does a dns lookup for smtp.ubaight.com on the xmail machine give the =
good ip
?
If ok, see your xmail smail log to see where xmail connected to send =
the
mails ...
If bad IP, try this (clear xmail dns cache) :
stop xmail
empty xmail 'dnscache/mx'
empty xmail
On Tuesday 18 May 2004 12:31, CLEMENT Francis wrote:
Does a dns lookup for smtp.ubaight.com on the xmail machine give the =
good ip
?
Yes
If ok, see your xmail smail log to see where xmail connected to send =
the
mails ...
If bad IP, try this (clear xmail dns cache) :
stop xmail
At 10:38 1/13/2004, Jeffrey Laramie wrote:
That's kinda interesting. You have multiple A records pointing to
66.219.172.36. We're getting a little OT here but why do you use A
records instead of CNAMEs? I know there was some debate about this years
ago and at that time the conventional wisdom was
At 10:38 1/13/2004, Jeffrey Laramie wrote:
Right, but getting back to Dale's original concern, his virtual domains
won't fail the remote server's RDNS check if the DNS for his SMTP server
is configured correctly. And he shouldn't be afraid to use RDNS to check
the validity of a remote server. Even
Tracy wrote:
At 10:38 1/13/2004, Jeffrey Laramie wrote:
That's kinda interesting. You have multiple A records pointing to
66.219.172.36. We're getting a little OT here but why do you use A
records instead of CNAMEs? I know there was some debate about this years
ago and at that time the
Tracy [EMAIL PROTECTED] wrote:
Because RFC2822 specifies that A records for mail servers should not
be CNAMEs...:)
You mean, rcf 2821.
Here is an extract:
Once an SMTP client lexically identifies a domain to which mail will
be delivered for processing (as described in sections 3.6
chabral wrote:
Jeffrey Laramie [EMAIL PROTECTED] wrote:
Would you by any chance have a link to this document? This is
something I really need to keep up on.
Here you can find all rfcs:
http://www.rfc-index.com/
Great, thanks. You've provided a valuable resource *and*
So it has nothing to do with my server setup?
Is there anything I can do to force Xmail to send the message?
Thanks in advance, and great software. This beats the heck outta =
eXtremail. Glad I made the jump.
[EMAIL PROTECTED] 01/12/04 04:29PM
On Mon, 12 Jan 2004, Dale Qualls wrote:
I'm
On Mon, 12 Jan 2004, Dale Qualls wrote:
So it has nothing to do with my server setup?
Is there anything I can do to force Xmail to send the message?
You can try to use the ESMTP extension:
MAIL FROM:... I-REALLY-BEG-YOU=1
but I don't think is gonna work :-)
Seriously, you can't.
-
Great, thank you.
I was wondering about the reverse DNS lookup that some mailservers do.
If my xmailserver has a default domain of mydomain.org and a reverse DNS =
lookup pointing to mydomain.org all is well. But, if myseconddomain.org =
users send a message to a place that does reverse DNS
Dale Qualls wrote:
Great, thank you.
I was wondering about the reverse DNS lookup that some mailservers do.
If my xmailserver has a default domain of mydomain.org and a reverse DNS =
lookup pointing to mydomain.org all is well. But, if myseconddomain.org =
users send a message to a place that
At 19:47 1/12/2004, Jeffrey Laramie wrote:
In a standard DNS configuration you would have a domain 'zone' file for
each domain name and a 'reverse lookup' zone file for each block of IPs.
The zone file typically has records that resolve a name to an IP address:
myhost A 12.34.56.78
The
That's exactly my question. How does an ISP handle this? I have one name =
for my xmail server that if you telnet to it you get mydomain.org and a =
RDNS will match mydomain.org, but if I'm sending mail from mythirddomain=
..org and a RDNS is looked at it will see mydomain.organd therefore get =
14 matches
Mail list logo
