275363 - Blank Emails dated 12/31/69, 7:00 pm appearing in Inbox

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Michael Natale]

(first time using bugzilla so feel free to beat me if i do this wrong)

Using TB version 1.0 (20041206) on OSX 10.3.7, connected up to Microsoft
Exchange Server 2000.  Minor annoyance - sometimes I will see I have unread mail
in my inbox.  If i use the filter to just show Unread messages, i see i have
email with blank sender, blank subject, and a date listed as 12/31/69, 7:00 pm.

I am able to manually delete this message.  If I open it up, it has no message
body.  I did search for this bug and found similar posting on the windows side
but not on OSX (and details of that bug didnt seem exactly the same).

Thanks for a great product - works flawlessly for me other than this one little
thing.

./Dingo

Comment 1

[Michael Natale]

Attachment: Screengrab of the described issue

just a screen grab showing the odd email.

Comment 2

[WADA:World Anti-bad-Duping Agency]

DUP of one of next three? (probably same as Bug 209501)
> Bug 73565 : Messages that lack a Date: header are displayed as "sent in
1969/12/31"(or 1970/01/01, Epoc time)
> Bug 209501 : Phantom mail from 1/01/1970 11:00 AM or 12/31/1969 keeps
reappearing in my inbox
> Bug 238189 : Mark email with no Date: header (e.g., 1969/12/31) as junk

By the way, above bugs and DUPed many bugs can be easily found by searching
"1969" in summary.
Michael Natale, did you use new "Find a Specific Bug" of "Search" of Bugzilla?
If not, what is used for search?
And what search keys(words,product,component etc.) did you use on search?
(Don't misunderstand my question, and don't feel bad by my question, please.)
(This is question to improve "Find a Specific Bug". See Bug 274365.         )

Comment 3

[Michael Natale]

(In reply to comment #2)
> DUP of one of next three? (probably same as Bug 209501)
> > Bug 73565 : Messages that lack a Date: header are displayed as "sent in
> 1969/12/31"(or 1970/01/01, Epoc time)
> > Bug 209501 : Phantom mail from 1/01/1970 11:00 AM or 12/31/1969 keeps
> reappearing in my inbox
> > Bug 238189 : Mark email with no Date: header (e.g., 1969/12/31) as junk
> 
> By the way, above bugs and DUPed many bugs can be easily found by searching
> "1969" in summary.
> Michael Natale, did you use new "Find a Specific Bug" of "Search" of Bugzilla?
> If not, what is used for search?
> And what search keys(words,product,component etc.) did you use on search?
> (Don't misunderstand my question, and don't feel bad by my question, please.)
> (This is question to improve "Find a Specific Bug". See Bug 274365.         )



Sorry dont recall which search.  I plugged in 12/31/69 into the search box and
spent about 20 mins looking through the hits that came up.  Sorry if this is a dupe.

Comment 4

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #3)
> Sorry if this is a dupe.
Michael, you needn't say sorry.
Since some bugs have "1969/12/31" in summary, some bugs could be found if you
specified "69/12/31" in your search (but if and only if all other keys for
search were specified appropriately.)
But how can usual human beings like you or me imagine "69/12/31" from "12/31/69"?
I already knew above three bugs, so I could easily find them again by searching
with "1969" when I saw your "12/31/69". 
This is the trick :-) 

As you see, a bug says "1969/12/31" but another says "1/01/1970".
Term or description for something depends on person and there are too many
term/description variations for a something.
This is one of the biggest reason why searching is very difficult.
Bugzilla should have AI capability! :-)

Anyway, is your problem same as Bug 209501?

Comment 5

[Chris Messina]

I get these too. My host says that they're most likely spam related.

Comment 6

[Frank Wein [:mcsmurf]]

Michael: Can you post the header of one such e-mail (so we know which bug to
dupe this one here to)?

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.