Robert,
Thank you so much for the quick reply. I will probably start the
process of moving up to the latest beta soon. But i know it's not a
trivial process, and I don't want to risk destabilizing the environment
at this point. Just need to get this HELO thing fixed quickly and keep
the clients happy at least for another day....
I see where I left of 'mail.' in the helloName in the smtpserver.xml.
But that appears to only be used for inbound SMTP. In the
mailetcontainer template file, as part of the remoteDelivery mailet,
there is this:
<!-- Set the HELO/EHLO name to use when connectiong to remote
SMTP-Server -->
<!--
<mail.smtp.localhost>myMailServer</mail.smtp.localhost>
-->
</mailet>
Why are there two different places to specify the HELO name? If the
smtpserver.xml one is supposed to be used for inbound and outbound, this
is redundant. I know smtpserver.xml hello is used for inbound smtp.
That is working. But it appears that James isn't using either one of
these (the smtpserver hello def or the RemoteDelivery HELO def) for
OUTBOUND smtp (which is the one I care about). After changing the
smtpserver.xml to mail.jwmhosting.com and verifying the remoteDelivery
mailet HELO def is also mail.jwmhosting.com, mail-tester reports that
it's still getting the Win Server machine name....
At this point, I'm willing to hardcode the HELO in the java file and
rebuild the jar. But I'm not that familiar with the James source. By
chance could you point me to a particular class or package inside James
where the HELO command is sent on outbound?
Thanks again.
Jerry
On 10/27/2014 3:51 AM, Robert Munn wrote:
Your rDNS: mail.jwmhosting.com looks correct to me.
I just did a telnet check of your smtp server:
$ telnet
telnet > open mail.jwmhosting.com 25
telnet > helo foo.com
reply shows:
250 jwmhosting.com Hello foo.com [xx.xx.xx.xx]) <- my ip address
What is important here is the helo name : jwmhosting.com. It should say
mail.jwmhosting.com. This is a spammer flag and can get your mail rejected
depending on the host. That is what the mail-tester service is complaining
about.
You set this in smptserver.xml (smtpserver.conf in beta4?)
Look for the block below, change it :
<helloName autodetect=“false”>mail.jwmhosting.com</helloName>
<!-- This is the name used by the server to identify itself in the SMTP -->
<!-- protocol. If autodetect is TRUE, the server will discover its -->
<!-- own host name and use that in the protocol. If discovery fails,
-->
<!-- the value of 'localhost' is used. If autodetect is FALSE, James
-->
<!-- will use the specified value. -->
<!--
<helloName autodetect="true">myMailServer</helloName>
-->
FYI, beta4 has a deadlocking problem, you might want to upgrade to beta 5. I
have instructions on how to build it from source on YouTube:
https://www.youtube.com/channel/UChNyi0dlyanLLhp7cA9q5dA
or if you prefer a text tutorial, on my blog:
http://blog.bonnydoonmedia.com/post.cfm/building-apache-james-from-source
On Oct 26, 2014, at 10:44 PM, Jerry Malcolm <techst...@malcolms.com> wrote:
I have been running James 3 b4 for several months. I was having some outbound
mail rejected by gmail and started doing some research. I did an email test
using mail-tester.com and got the error message that my HELO did not match the
rDNS. It reports:
IP: 64.34.163.186
HELO: p2825577
rDNS: mail.jwmhosting.com
The p2825577 number is my Windows Server 2008 machine name. I don't want to
use that.
In the RemoteDelivery mailet config, I have the following:
<mail.smtp.localhost>mail.jwmhosting.com</mail.smtp.localhost>
If I'm reading the instructions correctly, this should cause the specified
value (mail.jwmhosting.com) to be sent on the HELO instead of the p282...
number, correct? But it isn't.
What am I doing wrong?
BTW... I tried changing my rDNS to the p282... number. rDNS's have to be a
fully qualified domain name. So it won't take it. Fine... I then tried
changing my Win Server 08 machine name to be mail.jwmhosting.com. No go on
that either. Can't have periods in Win machines names.... So I'm stuck.
Please advise....
This is kinda urgent since I now realize that there's a distinct possibility
that some of my clients' emails are not getting through due to this. So thanks
in advance for a quick reply to this.
Jerry
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5315 / Virus Database: 4189/8459 - Release Date: 10/26/14
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
