scottatwittenberg
2[H]4U
- Joined
- Apr 10, 2002
- Messages
- 3,306
short story long, i can't do it.
it makes no sense.
exchange has all the default settings, which allow for pop / imap / stmp / mobile devices etc..
i think its because the mail server is directed using an A record. the DNS seems to just be all bootleg..
this might be the problem:
-----------------------------------
WARN
Mail server host name in greeting
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mail.ourdomain.org claims to be invalid hostname '**************************************************************************0****0****0':
220 **************************************************************************0****0****0 *********************200******0*****0*00
-------------------------
we do get e-mail though, which seems odd after looking at our DNS report..
and we can check our e-mail remotely via outlook web access..
and when we send out a mass e-mail, yahoo/gmail/msn, puts all of our e-mails straight to spam, if it doesn't block them all together.
it makes no sense.
exchange has all the default settings, which allow for pop / imap / stmp / mobile devices etc..
i think its because the mail server is directed using an A record. the DNS seems to just be all bootleg..
this might be the problem:
-----------------------------------
WARN
Mail server host name in greeting
WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.
mail.ourdomain.org claims to be invalid hostname '**************************************************************************0****0****0':
220 **************************************************************************0****0****0 *********************200******0*****0*00
-------------------------
we do get e-mail though, which seems odd after looking at our DNS report..
and we can check our e-mail remotely via outlook web access..
and when we send out a mass e-mail, yahoo/gmail/msn, puts all of our e-mails straight to spam, if it doesn't block them all together.