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: m
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 : jwmhost
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 cl
More progress... But now I'm really stumped. I dug into the
remoteDelivery mailet source. I did confirm that James is NOT using the
smtpserver.xml 'hello' value at all for outbound HELO. It is definitely
using the config parms for the remoteDelivery mailet.
In the mailet, the outbound HELO
Here is the answer, in RemoteDelivery.java, line 136:
* heloName (optional) - a String containing the name used in the
SMTP HELO and EHLO commands. Default is the default domain,
* which is typically localhost.
so in mailetcontainer.xml, this line:
mail.jwmhosting.com
should be this:
mail
hmm, wait, that isn’t working . another check ...
On Oct 27, 2014, at 1: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 show
well, this looks like it is hard-coded in AbstractConfigurableAsyncServer.java
in the trunk code,
/**
* Configure the helloName for the given Configuration
*
* @param handlerConfiguration
* @throws ConfigurationException
*/
protected void configureHelloName(Confi
Thanks for jumping in and investigating. This has gone from ugly to
horrible I think I have found the culprit.
I first had to figure out who is providing the class for SMTPTransport.
I figured out that the package for SMTPTransport is:
org.apache.geronimo.javamail.transport.smtp. So it
More info. SMPTConnection.java extends MailConnection.java which has a method
with this signature:
public boolean protocolConnect(String host, int port, String username, String
password) throws MessagingException
If you fail to pass ‘host’ as an argument to the method, the host defaults to
‘
mailet calls 'transport' which is an "SMTPTransport" instance.
SMTPTransport calls SMTPConnection.getLocalHost() which is inherited
from MailConnection.getLocalHost().
That method returns the InetAddress().getLocalHost().getHostName()
first. According to the spec, that should only occur IF th
Here is the base code. Note localHost is a property of the MailConnection
class. Note also that there is a setLocalHost() method. I am going to try
setting the localhost property from RemoteDelivery using setLocalHost(
localHost ).
public String getLocalHost() throws MessagingException {
The mailet only sees 'transport' which is cast to generic
"javax.mail.Transport". The localhost methods and connection methods
are all part of the geronimo impl. You'll need to cast the transport to
the geronimo package for the class, then see if you can get the
connection object from the tr
I may have a good build, stand by. I got the transport cast as SMTPTransport.
The code will need some polishing, let’s see first if it works.
On Oct 27, 2014, at 12:00 PM, Jerry Malcolm wrote:
> The mailet only sees 'transport' which is cast to generic
> "javax.mail.Transport". The localhost
Well, Robert, you get the prize It works (finally)!
Two changes required to RemoteDelivery mailet:
Add:
import org.apache.geronimo.javamail.transport.smtp.*;
Right after:
transport = session.getTransport(outgoingMailServer);
add:
((org.apache.geronimo.javamail.transport.smtp.SMTPTransp
Great stuff. I got the build working as well. I don’t like the fact that we’re
forcing it to use SMTPTransport, ruling out using other transport providers,
but if you look at the section of the code just below there, you see this:
// if the transport is a SMTPTransport (from sun) some
Here is my code. Import the SMTPTransport class, and replace this:
transport = session.getTransport(outgoingMailServer);
with this:
transport = (SMTPTransport) session.getTransport(outgoingMailServer);
transport.setLocalHost( props.getProperty("mail.smtp.localhost", heloName) );
Forgot one thing. Just above the try{} block, Transport transport is defined. I
changed it to this:
SMTPTransport transport = null;
On Oct 27, 2014, at 1:54 PM, Robert Munn wrote:
> Here is my code. Import the SMTPTransport class, and replace this:
>
> transport = session.getTransport(out
OK, I made an Eclipse patch for the RemoteDelivery issue. I also made a patch
for a mod I made to ReadOnlyUsersLDAPRespository.java that filters LDAP users
by an additional filter string specified in the ldap conf file. Details, and
patches, available on my blog:
http://blog.bonnydoonmedia.com/
A couple of additional notes. This issue appeared on Ubuntu as well, so it
is not just a windows issue.
On the good side, the version of Geronimo java mail in the app is fairly
old, so this bug may be fixed already.
On Oct 27, 2014 12:29 PM, "Jerry Malcolm" wrote:
> Well, Robert, you get the pr
Last followup about this subject for now. I did some digging into Geronimo
Javamail. There is a newer version, but the implementation has not changed, and
I don’t think it is regarded as a bug. I don’t see in the docs where
mail.smtp.localhost is supposed to preempt the
InetAddress.getLocalHost
Can you open a JIRA and upload your patches there?
On 10/28/2014 12:11 AM, Robert Munn wrote:
> OK, I made an Eclipse patch for the RemoteDelivery issue. I also made a patch
> for a mod I made to ReadOnlyUsersLDAPRespository.java that filters LDAP users
> by an additional filter string specified
ok
On Mar 1, 2015 12:51 AM, "Eric Charles" wrote:
> Can you open a JIRA and upload your patches there?
>
> On 10/28/2014 12:11 AM, Robert Munn wrote:
> > OK, I made an Eclipse patch for the RemoteDelivery issue. I also made a
> patch for a mod I made to ReadOnlyUsersLDAPRespository.java that filt
tickets created and patch files uploaded.
On Mar 3, 2015, at 1:09 PM, Robert Munn wrote:
> ok
>
> On Mar 1, 2015 12:51 AM, "Eric Charles" wrote:
> Can you open a JIRA and upload your patches there?
>
> On 10/28/2014 12:11 AM, Robert Munn wrote:
> > OK, I made an Eclipse patch for the RemoteDe
> Most java.mail parameters are only parsed on startup by the vm.
>
>
> Ciao.
> Bernd
>
>
>
> Ursprüngliche Nachricht
> Von: Jerry Malcolm
> Datum:
> An: James Users List
> Betreff: Re: James 3 b4 HELO Override Not Working?
>
>
>
liche Nachricht
Von: Jerry Malcolm
Datum:
An: James Users List
Betreff: Re: James 3 b4 HELO Override Not Working?
More progress... But now I'm really stumped. I dug into the
remoteDelivery mailet source. I did confirm that James is NOT using the
smtpserver.xml 'hello'
t; "-Djava.mail.localhost=mail.jwmhosting.com" in the java startup command
>>> line?
>>>
>>> Most java.mail parameters are only parsed on startup by the vm.
>>>
>>>
>>> Ciao.
>>> Bernd
>>>
>>>
>>>
> Von: Jerry Malcolm
> Datum:
> An: James Users List
> Betreff: Re: James 3 b4 HELO Override Not Working?
>
>
> More progress... But now I'm really stumped. I dug into the
> remoteDelivery mailet source. I did confirm that James is NOT using the
> smtpser
che Nachricht
> Von: Jerry Malcolm
> Datum:
> An: James Users List
> Betreff: Re: James 3 b4 HELO Override Not Working?
>
>
> More progress... But now I'm really stumped. I dug into the
> remoteDelivery mailet source. I did confirm that James is NOT using
startup command line?
Most java.mail parameters are only parsed on startup by the vm.
Ciao.
Bernd
Ursprüngliche Nachricht
Von: Jerry Malcolm
Datum:
An: James Users List
Betreff: Re: James 3 b4 HELO Override Not Working?
More progress... But now I'm really
cfmuns...@gmail.com]
Gesendet: Dienstag, 28. Oktober 2014 09:29
An: James Users List
Betreff: Re: James 3 b4 HELO Override Not Working?
Last followup about this subject for now. I did some digging into Geronimo
Javamail. There is a newer version, but the implementation has not changed, and
I don
x system used.
> In my opinion, this is not a bug, because it is not clear which network card
> to use on getLocalHost().
> But the same: it should be an option for default implementation, which should
> always be possible to configure.
>
> Just my remarks.
>
> Many thanks
olm
Datum:
An: James Users List
Betreff: Re: James 3 b4 HELO Override Not Working?
More progress... But now I'm really stumped. I dug into the
remoteDelivery mailet source. I did confirm that James is NOT using the
smtpserver.xml 'hello' value at all for outbound HELO. It is de
32 matches
Mail list logo