[edgy] errors while checking yahoo email

[John Vivirito]

Binary package hint: fetchyahoo

When i run fetchyahoo from term. It tells me how many emails i have than errors out while trying to open /var/mail/gnomefreak at /usr/bin/fetchyahoo. Here is the full output.

gnomefreak@EdgyEft:~$ fetchyahoo
No username specified.
Please enter your Yahoo! username: ubuntufreak

* WARNING * Term::ReadKey is not installed. Your password will be displayed on the screen.

Either Ctrl-C and install Term::ReadKey or make sure noone is looking at your screen.

Please enter your Yahoo! password: ******
Logging in securely via SSL as ubuntufreak on Wed Sep 27 13:07:43 2006
You are using 0% of your 1.0GB limit.
Successfully logged in as ubuntufreak.
Country code : us Folder: Inbox Version: 2.10.2
Getting Message ID(s) for message(s) 1 - 1.
Got 1 Message IDs
Failed: Couldn't open output: >>/var/mail/gnomefreak at /usr/bin/fetchyahoo line 1361, <STDIN> line 2.

Also when it says Please enter your Yahoo! password: ****** It prints my password in the terminal (I dont think thats real secure) but that is just extra. im more worried about how to read my mail from fetchyahoo.

[Eric Butler (codebutler)]

This might not be a bug... can you check that /var/mail/gnomefreak exists and is owned by your user?

sudo touch /var/mail/gnomefreak
sudo chown gnomefreak /var/mail/gnomefreak

[John Vivirito (gnomefreak)]

shouldnt fetchmail make these files by default? and i get no output from either command.

[Carthik Sharma (carthik)]

The first command should have created the file.
The second would have made you the owner so it now works.

The file that fetchyahoo (not fetchmail) delivers mail to should be defined and should exist.

Since you run fetchyahoo as a normal user (without using sudo) it possibly can't create a new file in /var/mail/

Hope this answers your questions. This looks more like a misconfiguration than an error. This is not a bug since fetchyahoo behaves as it should and doesn't choke or segfault, or die upon not finding the mail-spool. Please reopen this bug if you think it is really a bug.

For the password problem, the perl module Term::Readkey is required, as the warning says.