Closed Bug 93096 Opened 24 years ago Closed 21 years ago

can't read local mail

Categories

(MailNews Core :: Movemail, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: billw, Assigned: pkwarren)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-20mdksmp i686; en-US; rv:0.9.1) Gecko/20010607 BuildID: 2001060713 following the instructions I found elsewhere on mozilla.org, i created a pop3 account and then modified it within prefs.js to use movemail. When I click on 'Get Msg', the following line is printed to stderr: Exception : In mail commands Reproducible: Always Steps to Reproduce: 1.create a movemail account 2.get messages from that account 3.
Smoketest blocker.
Severity: normal → blocker
Keywords: smoketest
not a smoketest, not a blocker.
Severity: blocker → major
Keywords: smoketest
Just curious, what is movemail?
<qa_ignore> It's the mechanism by which mozilla slurps local unix mail spools, ie /var/spool/mail/username </qa_ignore>
Marking these all WORKSFORME sorry about lack of response but were very overloaded here. Only reopen the bug if you can reproduce with the following steps: 1) Download the latest nightly (or 0.9.6 which should be out RSN) 2) Create a new profile 3) test the bug again If it still occurs go ahead and reopen the bug. Again sorry about no response were quite overloaded here and understaffed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
reopening.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Status: UNCONFIRMED → NEW
Ever confirmed: true
Might be, this is a duplicate of bug 56671. Have you tried changing the permission of /var/spool/mail to 1777?
-> movemail owner
Assignee: adam → pkw
QA Contact: esther → stephend
This should have been working for a while. If not, please open a new bug.
Status: NEW → RESOLVED
Closed: 23 years ago21 years ago
Resolution: --- → WORKSFORME
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.