Eric Shubert wrote:
Jake Vickers wrote:
Eric Shubert wrote:
Interesting.
I don't buy that using an IP address is necessarily the best
practice though. Here are my thoughts on this.
It does not matter so much these days, but it used to be best
practice for multi-domain machines that
quote
It also can cause less problems in the corporate world if some
brighter-than-normal person performs a telnet session and finds that
you're not only running their email, but a competitor's as well or other
similar situation.
I liked this answer so much because I have a situation like
Lucian Cristian wrote:
quote
It also can cause less problems in the corporate world if some
brighter-than-normal person performs a telnet session and finds that
you're not only running their email, but a competitor's as well or
other similar situation.
I liked this answer so much because I
Eric Shubert wrote:
Interesting.
I don't buy that using an IP address is necessarily the best practice
though. Here are my thoughts on this.
It does not matter so much these days, but it used to be best practice
for multi-domain machines that accept mail. The reason being that when a
Jake Vickers wrote:
Eric Shubert wrote:
Interesting.
I don't buy that using an IP address is necessarily the best practice
though. Here are my thoughts on this.
It does not matter so much these days, but it used to be best practice
for multi-domain machines that accept mail. The reason
Around three years ago I had some mail rejected because the greeting
contained another domain name, maybe the destination had a very strict
spam filter, and after changing it to ip the mail was accepted, I
remember testing a lot with dnsstuff and following their advices
Lucian
Eric Shubert
Interesting.
I don't buy that using an IP address is necessarily the best practice
though. Here are my thoughts on this.
First, from rfc2821 (http://www.ietf.org/rfc/rfc2821.txt):
quote
One important reply is the connection greeting. Normally, a receiver
will send a 220 Service ready
Here's the entire error message. The info on conf files I read said to
put the IP in the me file if using multiple virtual hosts. For the
other files it always said me or... and then whatever went in that
file. So I thought that meant to put the word me in the file. Maybe it
means to just
The receiving server doesn't like the host name it's seeing in the smtp
session.
You haven't told me (that I see)
Adam Glass wrote:
Here's the entire error message. The info on conf files I read said to
put the IP in the me file if using multiple virtual hosts. For the other
files it always
Please ignore the first part, Adam. I meant to delete it.
Eric Shubert wrote:
ignored
Adam Glass wrote:
Here's the entire error message. The info on conf files I read said to
put the IP in the me file if using multiple virtual hosts. For the
other files it always said me or... and then
Telnet to port 25 confirms it just shows pmcawab. The challenge is
that there are two domains, awabllc.com and parkermerrick.com. If I
put one of those in smtpgreeting will there be a problem sending mail
from the other domain? Should I put the IP address there instead of a
host and
best practice is to use: [ip]
including []
Regards
Lucian
Adam Glass wrote:
Telnet to port 25 confirms it just shows pmcawab. The challenge is
that there are two domains, awabllc.com and parkermerrick.com. If I
put one of those in smtpgreeting will there be a problem sending mail
from the
Adam Glass wrote:
Telnet to port 25 confirms it just shows pmcawab. The challenge is that
there are two domains, awabllc.com and parkermerrick.com. If I put one
of those in smtpgreeting will there be a problem sending mail from the
other domain?
Not that I've ever seen.
Should I put the IP
Where'd you get that info from?
What if your server is on a dynamic IP address???
Lucian Cristian wrote:
best practice is to use: [ip]
including []
Regards
Lucian
Adam Glass wrote:
Telnet to port 25 confirms it just shows pmcawab. The challenge is
that there are two domains, awabllc.com
usually I don't use dynamic :)
there was a guide on http://www.dnsstuff.com/ (back when it was free)
and best practice for multiple domains was to use the ip address in the
greeteing,
Lucian
Eric Shubert wrote:
Where'd you get that info from?
What if your server is on a dynamic IP
I can't imagine why that would be considered best practice, except maybe
to save a DNS lookup. Certainly doesn't work with dynamic addresses. :(
Lucian Cristian wrote:
usually I don't use dynamic :)
there was a guide on http://www.dnsstuff.com/ (back when it was free)
and best practice for
you can check for current ip by cron (I do this on some servers, never
use dynamic on mail servers) and replace it , the file can be modified
any time
Lucian
Eric Shubert wrote:
I can't imagine why that would be considered best practice, except
maybe to save a DNS lookup. Certainly doesn't
That'd be simple enough to do for dynamic addresses.
Still begs the question, why is this considered best practice? There
must be a reason of some sort. If it's best practice for servers with
multiple domains, why wouldn't it also be best practice for servers with
only one domain?
I'm
Hello,
We are running qmail toaster with two virtual domain names. We can send
mail to most addresses, but now have run into a recipient who rejects our
messages. The key phrase in the error message is need fully qualified
hostname.
I think the problem is that some control files have just the
Adam Glass wrote:
Hello,
We are running qmail toaster with two virtual domain names. We can send
mail to most addresses, but now have run into a recipient who rejects
our messages. The key phrase in the error message is need fully
qualified hostname.
What is the entire error message? Is
20 matches
Mail list logo
