Smalltalk › Gemtalk › GLASS

Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

16 messages Options

glassdb

Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-GLASS0.231

New issue 358 by [hidden email]: Socket error during SendMail >>
readSmtpResult leads to #isEmpty MNU
http://code.google.com/p/glassdb/issues/detail?id=358

see http://forum.world.st/How-to-send-mail-from-Gemstone-tt4686799.html for
details

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

glassdb

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Comment #1 on issue 358 by [hidden email]: Socket error during
SendMail >> readSmtpResult leads to #isEmpty MNU
http://code.google.com/p/glassdb/issues/detail?id=358

Just ran into this issue too. Only in gemstone 3.1

We threw away the method override on SendMail>>connectTo:on: and have no
problems since.
Perhaps a different patch is required though as this was the quick solution
for us :-)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Dale Henrichs-3

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Johan and Alejandro ...

Yes the 3.1 universe is slightly different when it comes to GsSocket and it appears that we'll have to have a branch of the SMTP package for GemStone 3.x...

Alejandro, have you tried eliminating the extra method as Johan suggests?

Dale

----- Original Message -----
| From: [hidden email]
| To: [hidden email]
| Sent: Saturday, May 18, 2013 12:45:33 AM
| Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU
|
|
| Comment #1 on issue 358 by [hidden email]: Socket error during
| SendMail >> readSmtpResult leads to #isEmpty MNU
| http://code.google.com/p/glassdb/issues/detail?id=358
|
| Just ran into this issue too. Only in gemstone 3.1
|
| We threw away the method override on SendMail>>connectTo:on: and have
| no
| problems since.
| Perhaps a different patch is required though as this was the quick
| solution
| for us :-)
|
| --
| You received this message because this project is configured to send
| all
| issue notifications to this address.
| You may adjust your notification preferences at:
| https://code.google.com/hosting/settings
|

Alejandro Zuzek

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

Sorry for the too basic question that follows, but how can I eliminate a method using Topaz? I know how I could do this with GemTools, but GemTools is so slow when I try to run it on my local machine and connect it to the remote server where my GLASS instance is, that I'd rather not go through that path.

Thanks,

Alejandro

On Tue, May 21, 2013 at 2:52 PM, Dale K. Henrichs <[hidden email]> wrote:

Johan and Alejandro ...

Yes the 3.1 universe is slightly different when it comes to GsSocket and it appears that we'll have to have a branch of the SMTP package for GemStone 3.x...

Alejandro, have you tried eliminating the extra method as Johan suggests?

Dale

----- Original Message -----
| From: [hidden email]
| To: [hidden email]
| Sent: Saturday, May 18, 2013 12:45:33 AM
| Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU
|
|
| Comment #1 on issue 358 by [hidden email]: Socket error during
| SendMail >> readSmtpResult leads to #isEmpty MNU
| http://code.google.com/p/glassdb/issues/detail?id=358
|
| Just ran into this issue too. Only in gemstone 3.1
|
| We threw away the method override on SendMail>>connectTo:on: and have
| no
| problems since.
| Perhaps a different patch is required though as this was the quick
| solution
| for us :-)
|
| --
| You received this message because this project is configured to send
| all
| issue notifications to this address.
| You may adjust your notification preferences at:
| https://code.google.com/hosting/settings
|

Dale Henrichs-3

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Alejandro,

Soon I hope to have tODE available which should give you topaz-like performance with GemTools tools support...but I am not quite there yet:)

To remove a method you write a Smalltalk expression to remove the method from the class:

run
ClassName removeSelector: #methodToBeRemoved
%
commit

Dale

From: "Alejandro Zuzek" <[hidden email]>
To: "GemStone Seaside beta discussion" <[hidden email]>
Sent: Thursday, May 23, 2013 5:59:10 AM
Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

Sorry for the too basic question that follows, but how can I eliminate a method using Topaz? I know how I could do this with GemTools, but GemTools is so slow when I try to run it on my local machine and connect it to the remote server where my GLASS instance is, that I'd rather not go through that path.

Thanks,

Alejandro

On Tue, May 21, 2013 at 2:52 PM, Dale K. Henrichs <[hidden email]> wrote:

Johan and Alejandro ...

Yes the 3.1 universe is slightly different when it comes to GsSocket and it appears that we'll have to have a branch of the SMTP package for GemStone 3.x...

Alejandro, have you tried eliminating the extra method as Johan suggests?

Dale

----- Original Message -----
| From: [hidden email]
| To: [hidden email]
| Sent: Saturday, May 18, 2013 12:45:33 AM
| Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU
|
|
| Comment #1 on issue 358 by [hidden email]: Socket error during
| SendMail >> readSmtpResult leads to #isEmpty MNU
| http://code.google.com/p/glassdb/issues/detail?id=358
|
| Just ran into this issue too. Only in gemstone 3.1
|
| We threw away the method override on SendMail>>connectTo:on: and have
| no
| problems since.
| Perhaps a different patch is required though as this was the quick
| solution
| for us :-)
|
| --
| You received this message because this project is configured to send
| all
| issue notifications to this address.
| You may adjust your notification preferences at:
| https://code.google.com/hosting/settings
|

Alejandro Zuzek

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

Thanks again for all the help. I removed SendMail>>connectTo:On: this time getting a 'false' as the result of the SendMail>>send message and still no mail being sent. Getting a 'false' from SendMail>>send means that "rc := self openTcpConnection. " in SendMail>>send returned false. I'll investigate further in openTcpConnection if this gives me any clues.

Alejandro

On Thu, May 23, 2013 at 1:19 PM, Dale K. Henrichs <[hidden email]> wrote:

Alejandro,

Soon I hope to have tODE available which should give you topaz-like performance with GemTools tools support...but I am not quite there yet:)

To remove a method you write a Smalltalk expression to remove the method from the class:

run
ClassName removeSelector: #methodToBeRemoved
%
commit

Dale

From: "Alejandro Zuzek" <[hidden email]>
To: "GemStone Seaside beta discussion" <[hidden email]>
Sent: Thursday, May 23, 2013 5:59:10 AM

Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

Sorry for the too basic question that follows, but how can I eliminate a method using Topaz? I know how I could do this with GemTools, but GemTools is so slow when I try to run it on my local machine and connect it to the remote server where my GLASS instance is, that I'd rather not go through that path.

Thanks,

Alejandro

On Tue, May 21, 2013 at 2:52 PM, Dale K. Henrichs <[hidden email]> wrote:

Johan and Alejandro ...

Yes the 3.1 universe is slightly different when it comes to GsSocket and it appears that we'll have to have a branch of the SMTP package for GemStone 3.x...

Alejandro, have you tried eliminating the extra method as Johan suggests?

Dale

----- Original Message -----
| From: [hidden email]
| To: [hidden email]
| Sent: Saturday, May 18, 2013 12:45:33 AM
| Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU
|
|
| Comment #1 on issue 358 by [hidden email]: Socket error during
| SendMail >> readSmtpResult leads to #isEmpty MNU
| http://code.google.com/p/glassdb/issues/detail?id=358
|
| Just ran into this issue too. Only in gemstone 3.1
|
| We threw away the method override on SendMail>>connectTo:on: and have
| no
| problems since.
| Perhaps a different patch is required though as this was the quick
| solution
| for us :-)
|
| --
| You received this message because this project is configured to send
| all
| issue notifications to this address.
| You may adjust your notification preferences at:
| https://code.google.com/hosting/settings
|

Dale Henrichs-3

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Alejandro,

IIRC, if you get a false back from the call, you should be able to do the `self lastErr....` thing to get the socket error that caused the failure and then go from there...

Dale

From: "Alejandro Zuzek" <[hidden email]>
To: "GemStone Seaside beta discussion" <[hidden email]>
Sent: Thursday, May 23, 2013 3:34:35 PM
Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

Thanks again for all the help. I removed SendMail>>connectTo:On: this time getting a 'false' as the result of the SendMail>>send message and still no mail being sent. Getting a 'false' from SendMail>>send means that "rc := self openTcpConnection. " in SendMail>>send returned false. I'll investigate further in openTcpConnection if this gives me any clues.

Alejandro

On Thu, May 23, 2013 at 1:19 PM, Dale K. Henrichs <[hidden email]> wrote:

Alejandro,

Soon I hope to have tODE available which should give you topaz-like performance with GemTools tools support...but I am not quite there yet:)

To remove a method you write a Smalltalk expression to remove the method from the class:

run
ClassName removeSelector: #methodToBeRemoved
%
commit

Dale

From: "Alejandro Zuzek" <[hidden email]>
To: "GemStone Seaside beta discussion" <[hidden email]>
Sent: Thursday, May 23, 2013 5:59:10 AM

Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

Sorry for the too basic question that follows, but how can I eliminate a method using Topaz? I know how I could do this with GemTools, but GemTools is so slow when I try to run it on my local machine and connect it to the remote server where my GLASS instance is, that I'd rather not go through that path.

Thanks,

Alejandro

On Tue, May 21, 2013 at 2:52 PM, Dale K. Henrichs <[hidden email]> wrote:

Johan and Alejandro ...

Yes the 3.1 universe is slightly different when it comes to GsSocket and it appears that we'll have to have a branch of the SMTP package for GemStone 3.x...

Alejandro, have you tried eliminating the extra method as Johan suggests?

Dale

----- Original Message -----
| From: [hidden email]
| To: [hidden email]
| Sent: Saturday, May 18, 2013 12:45:33 AM
| Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU
|
|
| Comment #1 on issue 358 by [hidden email]: Socket error during
| SendMail >> readSmtpResult leads to #isEmpty MNU
| http://code.google.com/p/glassdb/issues/detail?id=358
|
| Just ran into this issue too. Only in gemstone 3.1
|
| We threw away the method override on SendMail>>connectTo:on: and have
| no
| problems since.
| Perhaps a different patch is required though as this was the quick
| solution
| for us :-)
|
| --
| You received this message because this project is configured to send
| all
| issue notifications to this address.
| You may adjust your notification preferences at:
| https://code.google.com/hosting/settings
|

Alejandro Zuzek

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi all,

I haven't abandoned this discussion, it's just that I have precious little moments that I can dedicate to this and I am not progressing as fast as I'd like. This is just to let you all know where I currently stand.

Dale's comment on using 'self lastErr...' got me a bit confused because I don't know which classes implement the lastErr... messages. To find that out (and avoid asking too basic questions) I ran this piece of code in Topaz:

topaz 1> printit
Smalltalk allClasses select: [ :class |
(class allSelectors select: [ :selector | selector beginsWith: #lastErr ]) isEmpty not ]
%
a Array
#1 a metaGciInterface
#2 a metaCLibrary
#3 a metaGsFile
#4 a metaGsSocket
#5 a metaRubySocket
#6 a metaGsSecureSocket
#7 a metaBinaryOrTextFile
#8 a metaSendMail

So, SendMail does implement at least one 'lastErr..' message. Apparently, I could get more information about the connection error I am experiencing by running this:

topaz 1> printit
| client |
client := SendMail new.
client
       user: 'glass';
       mailhostName: '[127.0.0.1]';
       smtpPort: 25;
       from: '[hidden email]';
       to: '[hidden email]';
       text: 'Greetings from GLASS';
       send;
       lastErr... "Exact message yet to be found"
%

I'll be sending the results of this as soon as have the opportunity to run it.

Thanks Dale for all your help.

Alejandro

On Thu, May 23, 2013 at 8:04 PM, Dale K. Henrichs <[hidden email]> wrote:

Alejandro,

IIRC, if you get a false back from the call, you should be able to do the `self lastErr....` thing to get the socket error that caused the failure and then go from there...

Dale

Dale Henrichs-3

Re: Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Alejandro,

Sorry for not being more specific. I was referring to using #lastErrorString...

I was probably thinking that you could modify SendMail>>openTcpConnection as follows:

openTcpConnection
| ok |
ok := self connectTo: self smtpPort on: self mailhostName.
ok
    ifFalse: [ self error: self lastErrorString ].
^ ok

to get a useful error message about why we aren't able to connect to the smtp port of the mail host...

BTW, the following should work as well:

topaz 1> printit
| client |
client := SendMail new.
client
       user: 'glass';
       mailhostName: '[127.0.0.1]';
       smtpPort: 25;
       from: '[hidden email]';
       to: '[hidden email]';
       text: 'Greetings from GLASS';
       send;
       lastErrorString
%

Modifying SendMail>>openTcpConnection just gets you closer to the correct solution (there should have been an error thrown in original implementation ... silent failures are difficult to debug:)

Dale

From: "Alejandro Zuzek" <[hidden email]>
To: "GemStone Seaside beta discussion" <[hidden email]>
Sent: Wednesday, June 5, 2013 7:13:43 AM
Subject: Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi all,

I haven't abandoned this discussion, it's just that I have precious little moments that I can dedicate to this and I am not progressing as fast as I'd like. This is just to let you all know where I currently stand.

Dale's comment on using 'self lastErr...' got me a bit confused because I don't know which classes implement the lastErr... messages. To find that out (and avoid asking too basic questions) I ran this piece of code in Topaz:

topaz 1> printit
Smalltalk allClasses select: [ :class |
       (class allSelectors select: [ :selector | selector beginsWith: #lastErr ]) isEmpty not ]
%
a Array
#1 a metaGciInterface
#2 a metaCLibrary
#3 a metaGsFile
#4 a metaGsSocket
#5 a metaRubySocket
#6 a metaGsSecureSocket
#7 a metaBinaryOrTextFile
#8 a metaSendMail

So, SendMail does implement at least one 'lastErr..' message. Apparently, I could get more information about the connection error I am experiencing by running this:

topaz 1> printit
| client |
client := SendMail new.
client
       user: 'glass';
       mailhostName: '[127.0.0.1]';
       smtpPort: 25;
       from: '[hidden email]';
       to: '[hidden email]';
       text: 'Greetings from GLASS';
       send;
       lastErr... "Exact message yet to be found"
%

I'll be sending the results of this as soon as have the opportunity to run it.

Thanks Dale for all your help.

Alejandro

On Thu, May 23, 2013 at 8:04 PM, Dale K. Henrichs <[hidden email]> wrote:

Alejandro,

IIRC, if you get a false back from the call, you should be able to do the `self lastErr....` thing to get the socket error that caused the failure and then go from there...

Dale

glassdb

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

In reply to this post by glassdb

Comment #2 on issue 358 by [hidden email]: Socket error during SendMail
>> readSmtpResult leads to #isEmpty MNU
http://code.google.com/p/glassdb/issues/detail?id=358

Hi,

Just stumbled on this issue again in a 3.1 stone with default GLASS 9
loaded.
Deleting the SendMail>>connectTo:on: solved the problem.

Any chance of getting this into the new GLASS release?

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Dale Henrichs-3

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Johan,

You mean GLASS 1.0-beta.9.1 as opposed to GLASS1?

Dale

On Thu, May 8, 2014 at 11:51 AM, <[hidden email]> wrote:

Comment #2 on issue 358 by [hidden email]: Socket error during SendMail

readSmtpResult leads to #isEmpty MNU

http://code.google.com/p/glassdb/issues/detail?id=358

Hi,

Just stumbled on this issue again in a 3.1 stone with default GLASS 9 loaded.
Deleting the SendMail>>connectTo:on: solved the problem.

Any chance of getting this into the new GLASS release?

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Johan Brichau-3

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Dale,

Yes, I mean GLASS 1.0-beta.9

btw: GLASS1 vs GLASS 1.0-beta is a bit a confusing name choice, no?

Johan

On 08 May 2014, at 20:52, Dale Henrichs <[hidden email]> wrote:

> Johan,
>
> You mean GLASS 1.0-beta.9.1 as opposed to GLASS1?
>
> Dale
>
>
> On Thu, May 8, 2014 at 11:51 AM, <[hidden email]> wrote:
>
> Comment #2 on issue 358 by [hidden email]: Socket error during SendMail
> readSmtpResult leads to #isEmpty MNU
> http://code.google.com/p/glassdb/issues/detail?id=358
>
> Hi,
>
> Just stumbled on this issue again in a 3.1 stone with default GLASS 9 loaded.
> Deleting the SendMail>>connectTo:on: solved the problem.
>
> Any chance of getting this into the new GLASS release?
>
>
> --
> You received this message because this project is configured to send all issue notifications to this address.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>

Dale Henrichs-3

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Yeah, GLASS1 is a placeholder name until we come up with a better name ... WebEdition or Foundation might be better names, but nothing is jumping out at me:)

On Thu, May 8, 2014 at 11:56 AM, Johan Brichau <[hidden email]> wrote:

Dale,

Yes, I mean GLASS 1.0-beta.9

btw: GLASS1 vs GLASS 1.0-beta is a bit a confusing name choice, no?

Johan

On 08 May 2014, at 20:52, Dale Henrichs <[hidden email]> wrote:

> Johan,
>
> You mean GLASS 1.0-beta.9.1 as opposed to GLASS1?
>
> Dale
>
>
> On Thu, May 8, 2014 at 11:51 AM, <[hidden email]> wrote:
>
> Comment #2 on issue 358 by [hidden email]: Socket error during SendMail
> readSmtpResult leads to #isEmpty MNU
> http://code.google.com/p/glassdb/issues/detail?id=358
>
> Hi,
>
> Just stumbled on this issue again in a 3.1 stone with default GLASS 9 loaded.
> Deleting the SendMail>>connectTo:on: solved the problem.
>
> Any chance of getting this into the new GLASS release?
>
>
> --
> You received this message because this project is configured to send all issue notifications to this address.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>

Dale Henrichs-3

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

In reply to this post by Johan Brichau-3

I can push it out in a 1.0-beta.9.2. Will that work for you?

If you don't want to move to 1.0-beta.9.1 then I can also push it out in a 1.0-beta.9.0.1 that is based off of 1.0-beta.9

Either way I'll include it GLASS1, too:)

Dale

On Thu, May 8, 2014 at 11:56 AM, Johan Brichau <[hidden email]> wrote:

Dale,

Yes, I mean GLASS 1.0-beta.9

btw: GLASS1 vs GLASS 1.0-beta is a bit a confusing name choice, no?

Johan

On 08 May 2014, at 20:52, Dale Henrichs <[hidden email]> wrote:

> Johan,
>
> You mean GLASS 1.0-beta.9.1 as opposed to GLASS1?
>
> Dale
>
>
> On Thu, May 8, 2014 at 11:51 AM, <[hidden email]> wrote:
>
> Comment #2 on issue 358 by [hidden email]: Socket error during SendMail
> readSmtpResult leads to #isEmpty MNU
> http://code.google.com/p/glassdb/issues/detail?id=358
>
> Hi,
>
> Just stumbled on this issue again in a 3.1 stone with default GLASS 9 loaded.
> Deleting the SendMail>>connectTo:on: solved the problem.
>
> Any chance of getting this into the new GLASS release?
>
>
> --
> You received this message because this project is configured to send all issue notifications to this address.
> You may adjust your notification preferences at:
> https://code.google.com/hosting/settings
>

Johan Brichau-3

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Hi Dale,

I don't want to stress things. We have it patched so I'm not waiting for you to make a release.
My ping was more about including the fix in a next GLASS for sure, which I assume you are working on in the context of GLASS for GS 3.2 :-)

So, whatever the next release plan for GLASS is, will work for us.

thanks
Johan

On 08 May 2014, at 21:08, Dale Henrichs <[hidden email]> wrote:

> I can push it out in a 1.0-beta.9.2. Will that work for you?
>
> If you don't want to move to 1.0-beta.9.1 then I can also push it out in a 1.0-beta.9.0.1 that is based off of 1.0-beta.9
>
> Either way I'll include it GLASS1, too:)
>
> Dale
>
>
> On Thu, May 8, 2014 at 11:56 AM, Johan Brichau <[hidden email]> wrote:
> Dale,
>
> Yes, I mean GLASS 1.0-beta.9
>
> btw: GLASS1 vs GLASS 1.0-beta is a bit a confusing name choice, no?
>
> Johan
>
> On 08 May 2014, at 20:52, Dale Henrichs <[hidden email]> wrote:
>
> > Johan,
> >
> > You mean GLASS 1.0-beta.9.1 as opposed to GLASS1?
> >
> > Dale
> >
> >
> > On Thu, May 8, 2014 at 11:51 AM, <[hidden email]> wrote:
> >
> > Comment #2 on issue 358 by [hidden email]: Socket error during SendMail
> > readSmtpResult leads to #isEmpty MNU
> > http://code.google.com/p/glassdb/issues/detail?id=358
> >
> > Hi,
> >
> > Just stumbled on this issue again in a 3.1 stone with default GLASS 9 loaded.
> > Deleting the SendMail>>connectTo:on: solved the problem.
> >
> > Any chance of getting this into the new GLASS release?
> >
> >
> > --
> > You received this message because this project is configured to send all issue notifications to this address.
> > You may adjust your notification preferences at:
> > https://code.google.com/hosting/settings
> >
>
>

Dale Henrichs-3

Re: [GS/SS Beta] Issue 358 in glassdb: Socket error during SendMail >> readSmtpResult leads to #isEmpty MNU

Ah, then I will put it into a 1.0-beta.9.2 and include the patch in GLASS1 ... The GLASS version that is compatible with 3.2 is GLASS 1.0-beta.9.1 ... for 3.2, I will open 1.0-beta.9.2 for development ...

Thanks!

Dale

On Thu, May 8, 2014 at 12:25 PM, Johan Brichau <[hidden email]> wrote:

Hi Dale,

I don't want to stress things. We have it patched so I'm not waiting for you to make a release.
My ping was more about including the fix in a next GLASS for sure, which I assume you are working on in the context of GLASS for GS 3.2 :-)

So, whatever the next release plan for GLASS is, will work for us.

thanks
Johan

On 08 May 2014, at 21:08, Dale Henrichs <[hidden email]> wrote:

> I can push it out in a 1.0-beta.9.2. Will that work for you?
>
> If you don't want to move to 1.0-beta.9.1 then I can also push it out in a 1.0-beta.9.0.1 that is based off of 1.0-beta.9
>
> Either way I'll include it GLASS1, too:)
>
> Dale
>
>
> On Thu, May 8, 2014 at 11:56 AM, Johan Brichau <[hidden email]> wrote:
> Dale,
>
> Yes, I mean GLASS 1.0-beta.9
>
> btw: GLASS1 vs GLASS 1.0-beta is a bit a confusing name choice, no?
>
> Johan
>
> On 08 May 2014, at 20:52, Dale Henrichs <[hidden email]> wrote:
>
> > Johan,
> >
> > You mean GLASS 1.0-beta.9.1 as opposed to GLASS1?
> >
> > Dale
> >
> >
> > On Thu, May 8, 2014 at 11:51 AM, <[hidden email]> wrote:
> >
> > Comment #2 on issue 358 by [hidden email]: Socket error during SendMail
> > readSmtpResult leads to #isEmpty MNU
> > http://code.google.com/p/glassdb/issues/detail?id=358
> >
> > Hi,
> >
> > Just stumbled on this issue again in a 3.1 stone with default GLASS 9 loaded.
> > Deleting the SendMail>>connectTo:on: solved the problem.
> >
> > Any chance of getting this into the new GLASS release?
> >
> >
> > --
> > You received this message because this project is configured to send all issue notifications to this address.
> > You may adjust your notification preferences at:
> > https://code.google.com/hosting/settings
> >
>
>