commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Hoffer <dhoff...@gmail.com>
Subject Re: commons-email sending email twice?
Date Fri, 29 Mar 2013 11:43:16 GMT
I'm not sure if it's relevant but the app...is also using Java Mail to read
the Inbox and once read it moves it to an archive folder.  I use
commons-email to send (text) reports that are generated during the process
of processing the data read in the Inbox.

-Dave


On Fri, Mar 29, 2013 at 5:37 AM, David Hoffer <dhoffer6@gmail.com> wrote:

> I found that...will do.
>
> -Dave
>
>
> On Fri, Mar 29, 2013 at 5:36 AM, David Hoffer <dhoffer6@gmail.com> wrote:
>
>> Sure, how do I enable debug mode?
>>
>> -Dave
>>
>>
>> On Fri, Mar 29, 2013 at 5:31 AM, Thomas Neidhart <
>> thomas.neidhart@gmail.com> wrote:
>>
>>> On Fri, Mar 29, 2013 at 1:30 AM, David Hoffer <dhoffer6@gmail.com>
>>> wrote:
>>>
>>> > I've got a strange one.  I'm using commons-email to send some email,
>>> that
>>> > is being sent to two recipients so I call addTo() twice, once for each
>>> > recipients, then I call send() once.  I can tell I'm calling send()
>>> once
>>> > per the log files.
>>> >
>>> > However two messages get sent.  I'm using GMail to send.  I can tell
>>> two
>>> > got sent because it logs two sent in GMail's Sent Mail folder. And
>>> each of
>>> > the recipients get duplicate emails.  They both have the same send and
>>> > receive timestamp.
>>> >
>>> > This program runs and does this twice per day, happens to be at
>>> midnight
>>> > and at 1am.  To try to keep GMail from combining/threading the
>>> messages the
>>> > subject contains the date.  So since we send the email an hour apart
>>> these
>>> > both have the same subject...and since the emails are duplicated we
>>> have 4
>>> > combined/threaded messages per day in our Sent Mail folder.  However we
>>> > should only have 2.
>>> >
>>> > This started happening about a month ago and we were using
>>> commons-email
>>> > 1.3, I since upgraded to 1.3.1 and get the same behavior.
>>> >
>>> > I don't know if this issue is with commons-email or GMail, or why it
>>> > started...it used to work fine.
>>> >
>>> > Has anyone seen anything like this?  Have any pointers how I might
>>> resolve
>>> > this?
>>> >
>>>
>>> Hi Dave,
>>>
>>> just tested it myself with my gmail account and could not reproduce your
>>> problem.
>>> Can you try to send the email with debug mode turned on and attach the
>>> output here?
>>>
>>> Thomas
>>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message