"$ !" is not a valid integer value

Found a serious/minor bug in PopTray? Tell me about it.

Moderators: KY Dave, jojobear99, Rdsok

Locked
User avatar
Seth77
Groupie
Posts: 51
Joined: Wed May 26, 2004 9:16 pm
Contact:

"$ !" is not a valid integer value

Post by Seth77 » Sat Jan 15, 2005 1:32 pm

This error become in the new version of poptray

yet this problem stop the mail checking

Alejandro
First Timer
Posts: 1
Joined: Tue Jan 18, 2005 8:28 pm

Error "$_!"

Post by Alejandro » Tue Jan 18, 2005 8:33 pm

Este error ocurre cuando un mail tiene un subject muy largo.
This error is when is very long subject. sorry my english is poor..

User avatar
Renier
Site Admin
Posts: 1957
Joined: Mon Oct 15, 2001 12:54 pm
Location: Cape Town, South-Africa
Contact:

Post by Renier » Mon Oct 17, 2005 6:17 pm

Hopefully this bug is fixed in PopTray 3.2 (beta 2)

EMPI
First Timer
Posts: 1
Joined: Thu Oct 20, 2005 12:58 am
Location: Poland
Contact:

Bug still egzist...

Post by EMPI » Thu Oct 20, 2005 1:04 am

version 3.2 beta2 Windows Xp Pro.
I have 3 account to check. While I'm checking one of them :
'$ b' is not a valid integer value
while checking another :
Access violation at address 004A3475 in module 'PopTray.exe'. Read of address 00D3C000.

hayke
First Timer
Posts: 1
Joined: Sat Jan 14, 2006 6:19 pm
Location: Netherlands

Re: Error "$_!"

Post by hayke » Sat Jan 14, 2006 6:30 pm

Alejandro wrote:Este error ocurre cuando un mail tiene un subject muy largo.
This error is when is very long subject. sorry my english is poor..
The same over here: I was still using version 3.03, working perfect, until I received a mail from Symantec Club with a very long subject line.
"$_t" is not a valid integer value. was the error message.
Had to go to Webmail to (temporary) delete that message. Now I could check my POP3-account again using PopTray.
I installed version 3.2 beta2 and tried again after putting back the long subject mail to the inbox in webmail and trying to check the POP3-account with this version I got the message "Acces violation....."
So version 3.2 beta2 did not resolve the problem. It just changed the error message. I am almost shure the Subject-line length is the cause of that error.
(I know Symantec Club really is the problem maker, sending such an oversized Subject-line..... :evil: but can you fix it??? :oops: )
Thank you.

Locked

Who is online

Users browsing this forum: No registered users and 5 guests