Nabble - Javamail

Re: forgettopheaders and boundary

2008-10-10T12:40:33Z

Kevin Bush wrote:
> I thought of that, but it's "inconvenient" (downright nasty) from a
> time/bandwidth point of view.
>
> Besides, everything else in the TOP header is fine, and Javamail has this very
> nice "forgettopheaders" capability. Why is Content-Type not forgotten?
>

forgettopheaders doesn't cause the headers to be ignored, it causes them
to be forgotten when you fetch the content of the message, which will
include the correct headers.

In looking into this, it appears that if you call the getContent method,
it might be using the bad Content-Type header to choose the JAF
DataContentHandler, before actually calling the DataContentHandler to
process the message content.

If you're using getContent, try calling getInputStream first. You can
just close the stream without reading it. Then call getContent.

If this solves your problem, let me know.

Still, after fetch the content, the Content-Type header should be correct.
If it's not, let me know in more detail what you're doing.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: forgettopheaders and boundary

2008-10-10T11:54:18Z

I thought of that, but it's "inconvenient" (downright nasty) from a
time/bandwidth point of view.

Besides, everything else in the TOP header is fine, and Javamail has this very
nice "forgettopheaders" capability. Why is Content-Type not forgotten?

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: forgettopheaders and boundary

2008-10-10T10:07:48Z

That's a seriously broken server. Set the mail.pop3.disabletop
property to "true" to disable all use of the TOP command.

Kevin Bush wrote:

> I'm working with a POP3 server that doesn't implement the TOP headers very
> well, specifically regarding the Content-Type header: it always sends
> text/plain and when the mail is actually multipart, it doesn't include the
> boundary. For example TOP shows:
>
> Content-Type: text/plain; charset="iso-8859-1"
>
> but RETR for the same message correctly shows
>
> Content-Type: multipart/alternative; boundary="uvNeLHH7rO"
>
> I'm using Javamail 1.4.1 (and jaf 1.1.1), and am setting the property
> mail.pop3.forgettopheaders to true and retrieving message like this (exception
> handling removed for clarity):
>
> Properties sysProps = new Properties();
> sysProps.put("mail.pop3.forgettopheaders", "true");
> Session mailSession = Session.getInstance(sysProps, null);
> mStore = mailSession.getStore("pop3");
> mFolder = mStore.getFolder("INBOX");
> Message[] msgs = {};
> msgs = mFolder.search(new SentDateTerm( ComparisonTerm.GT,date ));
>
> but when messages are retrieved, the Content-Type header is always the
> incorrect one returned by the TOP command.
>
> Am I doing something wrong, or is the Javamail forgettopheaders
> implementation not ignoring the TOP Content-Type header?
>
> ===========================================================================
> To unsubscribe, send email to listserv@... and include in the body
> of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
> listserv@... and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

forgettopheaders and boundary

2008-10-10T08:39:31Z

I'm working with a POP3 server that doesn't implement the TOP headers very
well, specifically regarding the Content-Type header: it always sends
text/plain and when the mail is actually multipart, it doesn't include the
boundary. For example TOP shows:

Content-Type: text/plain; charset="iso-8859-1"

but RETR for the same message correctly shows

Content-Type: multipart/alternative; boundary="uvNeLHH7rO"

I'm using Javamail 1.4.1 (and jaf 1.1.1), and am setting the property
mail.pop3.forgettopheaders to true and retrieving message like this (exception
handling removed for clarity):

Properties sysProps = new Properties();
sysProps.put("mail.pop3.forgettopheaders", "true");
Session mailSession = Session.getInstance(sysProps, null);
mStore = mailSession.getStore("pop3");
mFolder = mStore.getFolder("INBOX");
Message[] msgs = {};
msgs = mFolder.search(new SentDateTerm( ComparisonTerm.GT,date ));

but when messages are retrieved, the Content-Type header is always the
incorrect one returned by the TOP command.

Am I doing something wrong, or is the Javamail forgettopheaders
implementation not ignoring the TOP Content-Type header?

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Content-type: application/octet-stream

2008-10-02T23:54:56Z

Srinidhi Kannappady wrote:

> Hi Bill,
> Thanks a lot for providing the solution....
> But I am still wondering like if I do the follwoing I get the (No
> DCH...) exception:
>
> DataHandler dh = new DataHandler(request.message,
> "application/octet-stream");
> msg.setDataHandler(dh);
> msg.setHeader("Content-Transfer-Encoding", "base64");
>
> where request.message is a byte[].

There are no DataContentHandlers included for the MIME type
application/octet-stream. Before JAF 1.1.1, if there was no DCH,
JAF didn't know what to do. In JAF 1.1.1, if there is no DCH, and
the object type is a byte array or String, it will do the obvious
conversion. You must be using an older version of JAF.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Training & jobs

2008-10-02T02:20:14Z

“Join us to make future”
FOR OPT/F-1 STUDENTS
FREE TRAINING
FOOD ACCOMODATION
H1B PROCESSING FOR L1/ L2/ H1/ H4/ EAD/ GC
EXCELLENT OPPRTUNITIES
TRAINING
PLACEMENT
Highly Competitive offers for New H1b Transfers
About Us:
V2 technology inc is serving NJ since 2005, for us our employees are of utmost importance. Our highly skilled and dedicated instructors train you explicitly in market-related technologies for today and tomorrow. We will work with you in developing marketing strategies and finding the assignments of your choice.
We not only help you get a job but we build your long lasting careers!!!
What are we Looking for:
Excellent communication skills.
Valid F1/ OPT/ CPT/ H1/ H4/ L1 or valid work status (EAD, GC).
Bachelors’ degree in CS/ IT or previous IT experience.
Preferably (not mandatory) Master's Degree in Computers/ Electronics or previous IT experience.
Willing to relocate anywhere in USA.
What’s The Deal:
H1-B sponsorship to F1/ OPT/ H4/ L1/ L2/ E3/ EAD
Transfer of H1 & L1 visas.
Green Card sponsorship through PERM
Job focused professional training in
Java/ J2EE
.NET
Documentum
Share point
Oracle
Data Modeling
Relocation assistance- airfare, hotel accommodation, car rental etc
Guarantee lowest bench period.
Employee referral program.
Effective Resume writing help, Marketing and Placement.
Technical mock interviews. Preparation of In Person Interviews
100% Guaranteed placement
Get in Touch:
Contact immediately to know more about the opportunities with us at:609-843-0312
or
write mail at jobs@v2techinc.com
Contact person : John

Re: Yahoo! Mail Web Service provider

2008-09-30T18:46:19Z

Chris Webb wrote:
> Bill,
>
> I saw that you made a comment on the Yahoo! Mail Web Service API blog
> 23/3/07 where you queried whether regarding the terms of that service it
> would be possible to create a JavaMail provider and the following reply
> seemed to indicate that it would although I could see your concern. I
> was wondering whether you knew of such an endeavour?

I don't. I was hoping to work on that in my spare time, but I barely
got started before realizing it was going to take *a lot* of my time to
really understand the Yahoo! Mail Web Service side of things enough to
connect it to JavaMail. I was using JAX-WS to create a Java API for the
web service interface, and I got hung up on a few problems there as well.

I'd still like to do it, or see it get done, but it's currently rather
low on my priority list.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Content-type: application/octet-stream

2008-09-30T18:42:51Z

What object are you using to represent the content? JAF needs to
know how to convert that object, whatever it is, to a stream of
bytes in the "application/octet-stream" format. Since that format
is just an uninterpreted stream of bytes, you pretty much have to
start with bytes. Using ByteArrayDataSource will help.

So, instead of using

msg.setContent(myObjectOfSomeType, "application/octet-stream");

get the content of your message into some format that ByteArrayDataSource
understands, such as a String or a byte array or an InputStream, and use

msg.setDataHandler(new DataHandler(new ByteArrayDataSource(
myObject, "application/octet-stream");

Normally, it's a JAF DataContentHandler that's responsible for turning
a Java object of some type into a byte stream of a given MIME type.
What you did by adding that mailcap entry was configure the DataContentHandler
for the application/octet-stream MIME type to use the same DataContentHandler
that's used for the text/html MIME type. It might happen to work for the data
you have, but it's certainly not the right answer in general.

scorpion10 wrote:

> Hi,
>
> I was trying to send a simple SMTP message (using JavaMail 1.4.1) and the
> content-type I set was application/octet-stream.
> The exception I get is :
>
> javax.mail.MessagingException: IOException while sending message;
> nested exception is:
> javax.activation.UnsupportedDataTypeException: no object DCH for MIME type
> application/octet-stream
> at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:676)
> at com.srinidhi.examples.MyMailExample.postMail(MyMailExample.java:169)
> at
> com.srinidhi.examples.MyMailExample$TaskExecutor.run(MyMailExample.java:218)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
> at java.lang.Thread.run(Thread.java:619)
>
> I googled for this for few hours and did some things like downloaded latest
> activation.jar but still had the problem.
>
> Then I did the following:
> MailcapCommandMap mc = (MailcapCommandMap)CommandMap.getDefaultCommandMap();
> mc.addMailcap("application/octet-stream;;
> x-java-content-handler=com.sun.mail.handlers.text_html");
> CommandMap.setDefaultCommandMap(mc);
>
> And it is working now. But I am not sure if this is the right way of solving
> this problem. Also, could any one explain what
> x-java-content-handler=com.sun.mail.handlers.text_html that stands for and
> what I should be setting for application/octet-stream?
>
> Thanks
>

Yahoo! Mail Web Service provider

2008-09-30T09:43:48Z

Bill,

I saw that you made a comment on the Yahoo! Mail Web Service API blog 23/3/07 where you queried whether regarding the terms of that service it would be possible to create a JavaMail provider and the following reply seemed to indicate that it would although I could see your concern. I was wondering whether you knew of such an endeavour?

regards,
chris

--
Chris Webb
CTO
Inniu Ltd
e) chris.webb@...
m) +44 77 8639 2359

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVAMAIL-INTEREST". For general help, send email to listserv@... and include in the body of the message "help".

Content-type: application/octet-stream

2008-09-30T08:56:42Z

Hi,

I was trying to send a simple SMTP message (using JavaMail 1.4.1) and the content-type I set was application/octet-stream.
The exception I get is :

javax.mail.MessagingException: IOException while sending message;
nested exception is:
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type application/octet-stream
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:676)
at com.srinidhi.examples.MyMailExample.postMail(MyMailExample.java:169)
at com.srinidhi.examples.MyMailExample$TaskExecutor.run(MyMailExample.java:218)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

I googled for this for few hours and did some things like downloaded latest activation.jar but still had the problem.

Then I did the following:
MailcapCommandMap mc = (MailcapCommandMap)CommandMap.getDefaultCommandMap();
mc.addMailcap("application/octet-stream;; x-java-content-handler=com.sun.mail.handlers.text_html");
CommandMap.setDefaultCommandMap(mc);

And it is working now. But I am not sure if this is the right way of solving this problem. Also, could any one explain what x-java-content-handler=com.sun.mail.handlers.text_html that stands for and what I should be setting for application/octet-stream?

Thanks

Re: Transport.sendMessage()

2008-09-29T12:59:59Z

scorpion10 wrote:
> Hi,
>
> I was wondering if there is any way to specify the destination address as
> Cc or Bcc by using the sendMessage(msg, addresses) method of the Transport
> class. In the send(msg) method, we can set in the msg object like
> msg.addRecipients(Message.RecipientType.CC, "xxx@...");. I want to use
> the sendMessage(msg, addresses) because I can add the TransportEvent whereas
> if I use the send(msg) method I cannot add the TransportEvent to it.

"To" vs. "Cc" vs. "Bcc" is just a convention in the headers. In the end,
the message is sent to everyone equally. That's the list of addresses you
provide to sendMessage. How you arrange the addresses in the headers, or
whether you include them in the headers at all, is entirely up to you.
The message will be sent to the addresses you provide separately to
sendMessage, independently of what you include in the headers.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-28T13:51:35Z

Srinidhi Kannappady wrote:
> OK I tried with the msgsend.java. You can see the difference if you add
> the following to msgsend.java:
>
> props.put("mail.smtp.connectiontimeout", "0");
>
> Please check the exception when the value is 0 and the exception when
> the value is anything other than 0. The differnece in exception to
> observe is the exception that is wrapped inside the MessagingException.

Do you see the same difference when you do a raw socket connection with
a timeout of 0 vs. no timeout at all?

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-28T10:26:54Z

Srinidhi Kannappady wrote:
> The program I wrote is a stand alone application and I am sure the
> settings I provided will not be overridden ....

So, can you reproduce the problem using the msgsend.java demo program?

Bottom line, the same problem doesn't happen for me, and without a way
to reproduce the problem I can't explain why it's happening to you.
We either need to find a way to reproduce the problem in my environment,
or find a way to reproduce the problem in your environment using code I
know is correct.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-26T20:45:55Z

Where are you running your program? From the command line using
the "java" command? Inside an application server?

Is it possible that someone else is setting the mail.smtp.connectiontimeout
property for you?

Can you reproduce the problem using the msgsend.java demo program?

scorpion10 wrote:

> Hi,
> Sorry for the late reply...I created a scoket and tried to connect it to my
> host and it does different than what JavaMail does. The exception I get
> using the socket is as follows:
>
> java.net.ConnectException: Connection refused: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
> at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
> at java.net.Socket.connect(Socket.java:518)
> at java.net.Socket.connect(Socket.java:468)
> at java.net.Socket.<init>(Socket.java:365)
> at java.net.Socket.<init>(Socket.java:179)
> at com.srinidhi.examples.scjp.SocketExample.main(SocketExample.java:16)
>
> As mentioned in my previous post, JavaMail throws this ConnectException (of
> course wrapped inside MessagingException) only in 2 cases:
>
> a. props.put("mail.smtp.connectiontimeout", "0");
> b. mail.smtp.connectiontimeout is not specified at all
>
> All other cases JavaMail throws java.net.SocketTimeoutException (wrapped
> inside MessagingException)
>
> Thanks.
>
>
>
>
> Bill Shannon wrote:
>> scorpion10 wrote:
>>> Ya i purposely gave a wrong port number to test the exception. As I
>>> stated
>>> before ConnectException occurs only during the conditions mentioned i.e.
>>> if
>>> a specify a value for "mail.smtp.connectiontimeout" other than 0, even if
>>> I
>>> give a wrong port number, a time out exception is thrown.( One would
>>> expect
>>> a java.net.ConnectException to be thrown).
>>>
>>> I also tested by giving the "mail.smtp.connectiontimeout" value less
>>> than
>>> the time out value still it throws a time out exception.
>> In all cases we're talking about an exception that's wrapped in a
>> MessagingException, right?
>>
>> JavaMail is just reflecting whatever exception the java.net socket
>> support throws. Try creating a Socket to connect to your host and
>> set the timeout parameters however you like and see what exception
>> it throws. If it doesn't do what you expect, that's a java.net
>> problem and you should take that up with the JDK folks. If it does
>> something different than what you're seeing with JavaMail, let me
>> know the details.
>>
>> ===========================================================================
>> To unsubscribe, send email to listserv@... and include in the
>> body
>> of the message "signoff JAVAMAIL-INTEREST". For general help, send email
>> to
>> listserv@... and include in the body of the message "help".
>>
>>
>

Re: ConnectionTimeOut

2008-09-26T11:31:54Z

Hi,
Sorry for the late reply...I created a scoket and tried to connect it to my host and it does different than what JavaMail does. The exception I get using the socket is as follows:

java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at java.net.Socket.<init>(Socket.java:365)
at java.net.Socket.<init>(Socket.java:179)
at com.srinidhi.examples.scjp.SocketExample.main(SocketExample.java:16)

As mentioned in my previous post, JavaMail throws this ConnectException (of course wrapped inside MessagingException) only in 2 cases:

a. props.put("mail.smtp.connectiontimeout", "0");
b. mail.smtp.connectiontimeout is not specified at all

All other cases JavaMail throws java.net.SocketTimeoutException (wrapped inside MessagingException)

Thanks.

Bill Shannon wrote:

scorpion10 wrote:
> Ya i purposely gave a wrong port number to test the exception. As I stated
> before ConnectException occurs only during the conditions mentioned i.e. if
> a specify a value for "mail.smtp.connectiontimeout" other than 0, even if I
> give a wrong port number, a time out exception is thrown.( One would expect
> a java.net.ConnectException to be thrown).
>
> I also tested by giving the "mail.smtp.connectiontimeout" value less than
> the time out value still it throws a time out exception.

In all cases we're talking about an exception that's wrapped in a
MessagingException, right?

JavaMail is just reflecting whatever exception the java.net socket
support throws. Try creating a Socket to connect to your host and
set the timeout parameters however you like and see what exception
it throws. If it doesn't do what you expect, that's a java.net
problem and you should take that up with the JDK folks. If it does
something different than what you're seeing with JavaMail, let me
know the details.

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-23T12:35:31Z

scorpion10 wrote:
> Ya i purposely gave a wrong port number to test the exception. As I stated
> before ConnectException occurs only during the conditions mentioned i.e. if
> a specify a value for "mail.smtp.connectiontimeout" other than 0, even if I
> give a wrong port number, a time out exception is thrown.( One would expect
> a java.net.ConnectException to be thrown).
>
> I also tested by giving the "mail.smtp.connectiontimeout" value less than
> the time out value still it throws a time out exception.

In all cases we're talking about an exception that's wrapped in a
MessagingException, right?

JavaMail is just reflecting whatever exception the java.net socket
support throws. Try creating a Socket to connect to your host and
set the timeout parameters however you like and see what exception
it throws. If it doesn't do what you expect, that's a java.net
problem and you should take that up with the JDK folks. If it does
something different than what you're seeing with JavaMail, let me
know the details.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-23T11:16:17Z

Ya i purposely gave a wrong port number to test the exception. As I stated before ConnectException occurs only during the conditions mentioned i.e. if a specify a value for "mail.smtp.connectiontimeout" other than 0, even if I give a wrong port number, a time out exception is thrown.( One would expect a java.net.ConnectException to be thrown).

I also tested by giving the "mail.smtp.connectiontimeout" value less than the time out value still it throws a time out exception.

Bill Shannon wrote:

scorpion10 wrote:
> This is the exception I get when I set
> props.put("mail.smtp.connectiontimeout", "0"); or when I don't have this
> property in the program.
> javax.mail.MessagingException: Could not connect to SMTP host: XXX, port:
> 25;
> nested exception is:
> java.net.ConnectException: Connection refused: connect

Great, so you *are* getting a MessagingException.

The nested exception is from the java.net package and tells why the
connect failed. The connect isn't timing out, it's failing because
it's trying to connect to a port number on a host and there's no
server running on that port number on that host.

You're either connecting to the wrong port number or the wrong host.

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-23T10:28:19Z

scorpion10 wrote:
> This is the exception I get when I set
> props.put("mail.smtp.connectiontimeout", "0"); or when I don't have this
> property in the program.
> javax.mail.MessagingException: Could not connect to SMTP host: XXX, port:
> 25;
> nested exception is:
> java.net.ConnectException: Connection refused: connect

Great, so you *are* getting a MessagingException.

The nested exception is from the java.net package and tells why the
connect failed. The connect isn't timing out, it's failing because
it's trying to connect to a port number on a host and there's no
server running on that port number on that host.

You're either connecting to the wrong port number or the wrong host.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-23T09:22:19Z

This is the exception I get when I set props.put("mail.smtp.connectiontimeout", "0"); or when I don't have this property in the program.
javax.mail.MessagingException: Could not connect to SMTP host: XXX, port: 25;
nested exception is:
java.net.ConnectException: Connection refused: connect
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1542)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:452)
at javax.mail.Service.connect(Service.java:291)
at javax.mail.Service.connect(Service.java:172)
at javax.mail.Service.connect(Service.java:121)
at com.srinidhi.examples.MyMailExample.postMail(MyMailExample.java:129)
at com.srinidhi.examples.MyMailExample$TaskExecutor.run(MyMailExample.java:179)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:254)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:215)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1510)
... 12 more
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:254)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:215)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1510)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:452)
at javax.mail.Service.connect(Service.java:291)
at javax.mail.Service.connect(Service.java:172)
at javax.mail.Service.connect(Service.java:121)
at com.srinidhi.examples.MyMailExample.postMail(MyMailExample.java:129)
at com.srinidhi.examples.MyMailExample$TaskExecutor.run(MyMailExample.java:179)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:254)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:215)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1510)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:452)
at javax.mail.Service.connect(Service.java:291)
at javax.mail.Service.connect(Service.java:172)
at javax.mail.Service.connect(Service.java:121)
at com.srinidhi.examples.MyMailExample.postMail(MyMailExample.java:129)
at com.srinidhi.examples.MyMailExample$TaskExecutor.run(MyMailExample.java:179)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
Connection exception, may be the server is down!!! for messageId::100
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

Bill Shannon wrote:

scorpion10 wrote:
> Hi,
>
> I observed one thing in the properties that we set, if I set the
> connectiontimeout property, even if the server is down the JavaMail(v1.4.1)
> throws SocketTimeOutException instead of ConnectException and this is
> irrespective of the value I specify in the following:
>
> 1. props.put("mail.smtp.connectiontimeout", "10");
> 2. props.put("mail.smtp.timeout", "1000");
>
> The ConnectException is thrown only if :
>
> a) I don't specify 1.
> b) I give a value of 0 for 1.
>
> I read in the document that by default the connectiontimeout value is
> infinite. Please let me know if this is a bug.

There is no ConnectException.

The connect method should throw MessagingException in this case, with the
SocketTimeoutException attached. That's the behavior I'm seeing:

javax.mail.MessagingException: Could not connect to SMTP host: XXX, port: 25;
nested exception is:
java.net.SocketTimeoutException: connect timed out
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1542)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:452)
at javax.mail.Service.connect(Service.java:291)
at javax.mail.Service.connect(Service.java:172)
at javax.mail.Service.connect(Service.java:121)
at javax.mail.Transport.send0(Transport.java:190)
at javax.mail.Transport.send(Transport.java:120)
at msgsend.main(msgsend.java:178)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:252)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:215)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1510)
... 7 more

What's the traceback look like for the exception you're getting?

Can you reproduce the problem using the msgsend.java demo program?

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".

Re: ConnectionTimeOut

2008-09-22T13:36:58Z

scorpion10 wrote:

> Hi,
>
> I observed one thing in the properties that we set, if I set the
> connectiontimeout property, even if the server is down the JavaMail(v1.4.1)
> throws SocketTimeOutException instead of ConnectException and this is
> irrespective of the value I specify in the following:
>
> 1. props.put("mail.smtp.connectiontimeout", "10");
> 2. props.put("mail.smtp.timeout", "1000");
>
> The ConnectException is thrown only if :
>
> a) I don't specify 1.
> b) I give a value of 0 for 1.
>
> I read in the document that by default the connectiontimeout value is
> infinite. Please let me know if this is a bug.

There is no ConnectException.

The connect method should throw MessagingException in this case, with the
SocketTimeoutException attached. That's the behavior I'm seeing:

javax.mail.MessagingException: Could not connect to SMTP host: XXX, port: 25;
nested exception is:
java.net.SocketTimeoutException: connect timed out
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1542)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:452)
at javax.mail.Service.connect(Service.java:291)
at javax.mail.Service.connect(Service.java:172)
at javax.mail.Service.connect(Service.java:121)
at javax.mail.Transport.send0(Transport.java:190)
at javax.mail.Transport.send(Transport.java:120)
at msgsend.main(msgsend.java:178)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:252)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:215)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1510)
... 7 more

What's the traceback look like for the exception you're getting?

Can you reproduce the problem using the msgsend.java demo program?

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

ConnectionTimeOut

2008-09-22T12:52:49Z

Hi,

I observed one thing in the properties that we set, if I set the connectiontimeout property, even if the server is down the JavaMail(v1.4.1) throws SocketTimeOutException instead of ConnectException and this is irrespective of the value I specify in the following:

1. props.put("mail.smtp.connectiontimeout", "10");
2. props.put("mail.smtp.timeout", "1000");

The ConnectException is thrown only if :

a) I don't specify 1.
b) I give a value of 0 for 1.

I read in the document that by default the connectiontimeout value is infinite. Please let me know if this is a bug.

Thanks

Re: IMAP folder append and copy

2008-09-22T05:08:04Z

Bill,

I got the search for the recent appended message working using the following code as per your suggestion:

folder.appendMessage(message);
folder.open(Folder.READ_ONLY);

String[] headerValues = message.getHeader("Message-ID");
if (headerValues.length != 1) {
     throw new IllegalStateException("Unexpected Message-ID header value count of " + headerValues.length + " when expecting 1");
}

MessageIDTerm messageIdTerm = new MessageIDTerm(headerValues[0]);
Message[] messages = folder.getMailFolder().search(messageIdTerm);

if (messages.length != 1) {
    throw new IllegalStateException("Unexpected message count of " + messages.length + " when expecting 1");
}

inboxFolder = folder.getFolder("INBOX");
inboxFolder.open(Folder.READ_WRITE);
folder.getMailFolder().copyMessages(messages, inboxFolder);

Can you expand on how I would optimise this to only search messages that appear after the append takes place?

Can you explain why there would be a delay between the append completing and the message appearing in the folder?

regards,
Chris

On Thu, Sep 18, 2008 at 1:04 AM, Bill Shannon <bill.shannon@...> wrote:

Chris Webb wrote:

Hello,

I need to append a message to an IMAP folder then immediately copy that message to another folder, doing two appends is not an option, and I'm struggling to work out the best way to do the copy using JavaMail 1.3.3. <http://1.3.3.> The copyMessages operation understandably requires an IMAPMessage but I'm not sure how I can retrieve the exact IMAPMessage object for the message just appended. The JavaDoc indicates that appendMessages fires off a MessageCountEvent and I was hoping that might provide me with the message details but no event is being fired. Is there another option?

Assuming you're stuck with 1.3.3...

You'll need to search the destination folder for the new message, e.g.,
using the Message-ID to match. You can narrow the search by only searching
messages that appear after you do the append, e.g., that have a larger
message number than the number of messages before the append. Note that
there might be some delay between when the append completes and when the
message appears in the folder.

--
Chris Webb
CTO
Inniu Ltd
e) chris.webb@...
m) +44 77 8639 2359

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVAMAIL-INTEREST". For general help, send email to listserv@... and include in the body of the message "help".

Re: javamail backwards compatibility

2008-09-18T15:46:44Z

Brendan Miller wrote:
> My team has a bunch of stuff linked into the javamail 1.3.1 mail.jar.
> How strong of backwards compatibility does the latest javamail offer?
> Can I just drop in the 1.4.1 mail.jar and expect everything to work?
> Will jars originally built against earlier versions work with newer
> versions without recompile?

The goal is very strong backwards compatibility.

The highest importance is the APIs defined by the JavaMail spec.

Less important is the Sun-specific features of the implementation,
although generally we try to maintain compatibility for them as well.

As I'm sure you're aware, part of the responsibility is on the application.
It's always possible for applications to do things there were never defined
by the spec, never expected to work, and possibly even violate the
expectations of the spec. It's a lot harder to provide compatibility for
such applications.

Performance compatibility is also hard. We often change the implementation
to improve the performance of most apps, but some apps might be (unknowingly)
dependent on the implementation details and perform worse as those details
change.

All software has bugs. Every change to software risks introducing a new
bug. It's always possible that new versions have bugs that older versions
don't have, and that such bugs will effect your application.

But, if the application developer has made some attempt to produce a
portable app, the probability that it will work with a new version of
JavaMail is extremely high.

And of course we're always interested in any compatibility problems, or
bugs, you might find!

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

javamail backwards compatibility

2008-09-18T14:16:26Z

My team has a bunch of stuff linked into the javamail 1.3.1 mail.jar.
How strong of backwards compatibility does the latest javamail offer?
Can I just drop in the 1.4.1 mail.jar and expect everything to work?
Will jars originally built against earlier versions work with newer
versions without recompile?

Thanks

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Problem using JavaMail to send email with SMTP AUTH

2008-09-18T11:19:31Z

Simon Kittle wrote:
> Thanks!! It probably doesn't help there are so many examples floating
> around the web with the wrong method and people asking for help! heh.

The web is *full* of misinformation.

I try to make sure the documentation on java.sun.com is correct.
Please check there first.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Problem using JavaMail to send email with SMTP AUTH

2008-09-18T10:35:44Z

Thanks!! It probably doesn't help there are so many examples floating
around the web with the wrong method and people asking for help! heh.

> -----Original Message-----
> From: Bill Shannon [mailto:bill.shannon@...]
> Sent: Thursday, September 18, 2008 6:31 PM
> To: Simon Kittle
> Cc: JAVAMAIL-INTEREST@...
> Subject: Re: Problem using JavaMail to send email with SMTP AUTH
>
> Simon Kittle wrote:
> > Hi,
> >
> > I'm having trouble sending email using JavaMail using SMTP AUTH. I
> have a
> > JAMES server setup. I'm 99% sure that my JAMES config is okay
> because I can
> > both send email by hand using telnet, and also using Outlook as a
> client
> > (both with SMTP AUTH).
> >
> > This is the code which tries to send the mail:
> >
> > props.put("mail.debug", true);
>
> true needs to be a string - "true"
>
> > props.put("mail.smtp.host", smtpHostName);
> > props.put("mail.smtp.auth", true);
>
> Ditto.
>
> Fixing that will solve your problem.
>
> It's explained in the javadocs that these properties need to be set as
> strings, but this is another one of those things that enough people
> mess
> up that I'm adding support for it in the next release.

Re: Properties in general

2008-09-18T10:33:18Z

Setting it by doing:

props.put("mail.debug", true);

Yeah I didn't mean the property for the actual password - just the user and
the "auth" property to make it use auth in the first place. My bad. My
question was why they need to be set, and the auth object passed, and then
Transport.connect has to have all the values specified anyway.

My debug output from JavaMail confirms that it is not attempting the AUTH,
in regard to my previous (original) question.

EHLO *REMOVED*
250-*REMOVED* Hello *REMOVED* (*REMOVED* [127.0.0.1])
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250-PIPELINING
250 ENHANCEDSTATUSCODES
DEBUG SMTP: Found extension "AUTH", arg "LOGIN PLAIN"
DEBUG SMTP: Found extension "AUTH=LOGIN", arg "PLAIN"
DEBUG SMTP: Found extension "PIPELINING", arg ""
DEBUG SMTP: Found extension "ENHANCEDSTATUSCODES", arg ""
DEBUG SMTP: use8bit false
MAIL FROM:<mailer-testtest=fastmail.co.uk@*REMOVED*>
250 2.1.0 Sender <mailer-testtest=fastmail.co.uk@*REMOVED*> OK
RCPT TO:<testtest@...>
530 5.7.1 Authentication Required
DEBUG SMTP: Invalid Addresses
DEBUG SMTP: testtest @inbox.com
DEBUG SMTP: Sending failed because of invalid destination addresses

> -----Original Message-----
> From: Bill Shannon [mailto:bill.shannon@...]
> Sent: Thursday, September 18, 2008 6:28 PM
> To: Simon Kittle
> Cc: JAVAMAIL-INTEREST@...
> Subject: Re: Properties in general
>
> Simon Kittle wrote:
> > Obviously, the "mail.debug"
> > property is being completely ignored. Do these properties always get
> > ignored? Has anyone had success with them actually working?
>
> Yes, they definitely work. How were you setting the mail.debug
> property?
>
> > Could that be
> > why you still have to login with something like
> "tr.connect(smtpHostName,
> > smtpUser, smtpPassword);", because the user and password properties
> are
> > basically ignored?
>
> There is no password property. Our security experts convinced us that
> it's
> a bad idea to store passwords in properties. Still, enough people
> think
> that there *is* a password property that I'm considering adding support
> for
> it in a future release, even with the potential security problem (which
> is
> probably only of interest to the truly paranoid).

Re: Problem using JavaMail to send email with SMTP AUTH

2008-09-18T10:30:31Z

Simon Kittle wrote:

> Hi,
>
> I'm having trouble sending email using JavaMail using SMTP AUTH. I have a
> JAMES server setup. I'm 99% sure that my JAMES config is okay because I can
> both send email by hand using telnet, and also using Outlook as a client
> (both with SMTP AUTH).
>
> This is the code which tries to send the mail:
>
> props.put("mail.debug", true);

true needs to be a string - "true"

> props.put("mail.smtp.host", smtpHostName);
> props.put("mail.smtp.auth", true);

Ditto.

Fixing that will solve your problem.

It's explained in the javadocs that these properties need to be set as
strings, but this is another one of those things that enough people mess
up that I'm adding support for it in the next release.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Properties in general

2008-09-18T10:27:39Z

Simon Kittle wrote:
> Obviously, the "mail.debug"
> property is being completely ignored. Do these properties always get
> ignored? Has anyone had success with them actually working?

Yes, they definitely work. How were you setting the mail.debug property?

> Could that be
> why you still have to login with something like "tr.connect(smtpHostName,
> smtpUser, smtpPassword);", because the user and password properties are
> basically ignored?

There is no password property. Our security experts convinced us that it's
a bad idea to store passwords in properties. Still, enough people think
that there *is* a password property that I'm considering adding support for
it in a future release, even with the potential security problem (which is
probably only of interest to the truly paranoid).

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Properties in general

2008-09-18T10:03:56Z

Hi,

I don't know if this could be related to my problem with getting SMTP AUTH
to work....but, previously I was setting the property "mail.debug" to be
true. The docs say this way debugging is turned on during the constructor.
With this enabled I wasn't actually receiving any debug output.

I put this down to me having something else badly configured, and so I tried
to fix my SMTP AUTH problem just without getting debugging working.

I've recently added the line of code:

session.setDebug(true);

Suddenly I've got loads of debugging output. Obviously, the "mail.debug"
property is being completely ignored. Do these properties always get
ignored? Has anyone had success with them actually working? Could that be
why you still have to login with something like "tr.connect(smtpHostName,
smtpUser, smtpPassword);", because the user and password properties are
basically ignored?

Not that any of that could be the reason why my auth problem exists because
I'm using the full method of connect(). Just curious as to why these
properties seem to be ignored.

Si

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Problem using JavaMail to send email with SMTP AUTH

2008-09-18T09:49:41Z

Hi,

I'm having trouble sending email using JavaMail using SMTP AUTH. I have a
JAMES server setup. I'm 99% sure that my JAMES config is okay because I can
both send email by hand using telnet, and also using Outlook as a client
(both with SMTP AUTH).

This is the code which tries to send the mail:

props.put("mail.debug", true);
props.put("mail.smtp.host", smtpHostName);
props.put("mail.smtp.auth", true);
String[] envelopeSender = envelopeSenderAddress.split("@");
// setup VERP
props.put("mail.smtp.from", envelopeSender[0] +
emailMessage.toEmail.replaceAll("@", "=") + "@" + envelopeSender[1]);
Session session = Session.getInstance(props, auth);
javax.mail.Message m = new MimeMessage(session);

m.setFrom(new InternetAddress(emailMessage.fromEmail));
m.setSubject(emailMessage.subject);
m.setRecipient(javax.mail.Message.RecipientType.TO, new
InternetAddress(emailMessage.toEmail));

// body set according to appropriate content.

And this is all then send to the SMTP server using:

Transport tr = session.getTransport("smtp");
//tr.connect(smtpHostName, 2346, smtpUser, smtpPassword);
tr.connect(smtpHostName, smtpUser, smtpPassword);
m.saveChanges();
tr.sendMessage(m, m.getAllRecipients());
tr.close();

(I tried to just use Transport.send(m); but that didn't work either, which
is why its in the expanded form).

What happens is that despite setting up auth in the above code, the message
is rejected due to an auth error. I've check the username and password and
they are fine (the same ones being used by hand, or in Outlook). Whats more
the message isn't "bad authentication" but "class
com.sun.mail.smtp.SMTPAddressFailedException: 530 5.7.1 Authentication
Required", so it seems as if JavaMail isn't actually attempting to do any
AUTH.

I've searched and not found any ideas on the internet, save one post saying
I also need to insert something similar to "props.put("mail.smtp.submitter",
auth.getPasswordAuthentication());", which I tried, but which had no effect.

What's more, my JAMES logs seem also to indicate that JavaMail is not
actually trying to do the authentication, see below:

18/09/08 17:00:22 DEBUG smtpserver: Sent: 250-AUTH LOGIN PLAIN
18/09/08 17:00:22 DEBUG smtpserver: Sent: 250-AUTH=LOGIN PLAIN
18/09/08 17:00:22 DEBUG smtpserver: Sent: 250-PIPELINING
18/09/08 17:00:22 DEBUG smtpserver: Sent: 250 ENHANCEDSTATUSCODES
18/09/08 17:00:22 DEBUG smtpserver: Calling reset() default Worker #17
18/09/08 17:00:23 DEBUG smtpserver: Lookup command handler for command: MAIL
18/09/08 17:00:23 DEBUG smtpserver: Sent: 250 2.1.0 Sender <**REMOVED**> OK
18/09/08 17:00:23 DEBUG smtpserver: Calling reset() default Worker #17
18/09/08 17:00:23 DEBUG smtpserver: Lookup command handler for command: RCPT
18/09/08 17:00:23 DEBUG smtpserver: Sent: 530 5.7.1 Authentication Required
18/09/08 17:00:23 ERROR smtpserver: Rejected message - authentication is
required for mail request [to:REMOVED] [from:REMOVED]

If anyone could help me shed from light on this that would be great. I'd
also be interested in learning why one has to both do this:

props.put("mail.smtp.auth", true);
Session session = Session.getInstance(props, auth);

and then login with the auth details also:

tr.connect(smtpHostName, smtpUser, smtpPassword);

Any help would be mucho appreciated....

Simon

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: IMAP folder append and copy

2008-09-17T17:04:10Z

Chris Webb wrote:

> Hello,
>
> I need to append a message to an IMAP folder then immediately copy that
> message to another folder, doing two appends is not an option, and I'm
> struggling to work out the best way to do the copy using JavaMail 1.3.3.
> <http://1.3.3.> The copyMessages operation understandably requires an
> IMAPMessage but I'm not sure how I can retrieve the exact IMAPMessage
> object for the message just appended. The JavaDoc indicates that
> appendMessages fires off a MessageCountEvent and I was hoping that might
> provide me with the message details but no event is being fired. Is
> there another option?

Assuming you're stuck with 1.3.3...

You'll need to search the destination folder for the new message, e.g.,
using the Message-ID to match. You can narrow the search by only searching
messages that appear after you do the append, e.g., that have a larger
message number than the number of messages before the append. Note that
there might be some delay between when the append completes and when the
message appears in the folder.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

IMAP folder append and copy

2008-09-17T16:09:03Z

Hello,

I need to append a message to an IMAP folder then immediately copy that message to another folder, doing two appends is not an option, and I'm struggling to work out the best way to do the copy using JavaMail 1.3.3. The copyMessages operation understandably requires an IMAPMessage but I'm not sure how I can retrieve the exact IMAPMessage object for the message just appended. The JavaDoc indicates that appendMessages fires off a MessageCountEvent and I was hoping that might provide me with the message details but no event is being fired. Is there another option?

cheers,
chris

--
Chris Webb
CTO
Inniu Ltd
e) chris.webb@...
m) +44 77 8639 2359

=========================================================================== To unsubscribe, send email to listserv@... and include in the body of the message "signoff JAVAMAIL-INTEREST". For general help, send email to listserv@... and include in the body of the message "help".

Re: Unique ID for SMTP messages

2008-09-15T12:21:36Z

scorpion10 wrote:

> Yes you are right but I store the request event (which I use later when I get
> the response) into a queue. The request event is my own event where I have
> some other processing to do. So I need this unique ID for retrieving this
> event from the queue when I get the TransportEvent.
>
> So I feel its better to give a ID parameter for storing some unique ID.
> (Just a suggestion).
>
> Right now for this I found a way i.e. I create a hashCode for the Object and
> store this value as a uniqueID.

What information do you need in the queue? Just create your own object to
hold that information, possibly including the MimeMessage object that you
sent. Put the information in the queue after you call Transport.send.

Note also that JavaMail will generate a Message-ID header for each message.
That might meet your needs for a unique ID. You can fetch that from the
Message object included in the TransportEvent, if you really want to use
TransportEvent.

===========================================================================
To unsubscribe, send email to listserv@... and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@... and include in the body of the message "help".

Re: Unique ID for SMTP messages

2008-09-15T11:37:47Z

Yes you are right but I store the request event (which I use later when I get the response) into a queue. The request event is my own event where I have some other processing to do. So I need this unique ID for retrieving this event from the queue when I get the TransportEvent.

So I feel its better to give a ID parameter for storing some unique ID. (Just a suggestion).

Right now for this I found a way i.e. I create a hashCode for the Object and store this value as a uniqueID.

Thanks

Bill Shannon wrote:

scorpion10 wrote:
> I am trying to send SMTP messages (Using JavaMail API v 1.4). Since I need
> high performance I make use of Threads to submit messages (I submit around
> 100 messages per second). My question is how would I know when the response
> arrives, to which request it was. In other words is there any field called
> ID which I can set in the request and get it back in the TransportEvent?
>
> One of the way I can see is to set as Header value and retrieve it from the
> TransportEvent. But then the problem is the recipient of the message can get
> this value too (Which is not desirable).
>
> So please let me know if there is any way I can set the ID.

If all you're looking for is the confirmation that the server has
received the message (which is all the TransportEvent is telling you),
it's probably easy just to not listen for the transport events and
simply use the success of the send method.

===========================================================================
To unsubscribe, send email to listserv@java.sun.com and include in the body
of the message "signoff JAVAMAIL-INTEREST". For general help, send email to
listserv@java.sun.com and include in the body of the message "help".