Evolution "can not send mail" message doesn't look HIG complient

Bug #97607 reported by Adam Petaccia
6
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Low
evolution (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

My school doesn't allow outgoing SMTP mail, so I have my computer set to send mail to localhost, and whenever I SSH in from another machine, portforwarding takes over, and the mail gets out. No problem. But when I don't have an SSH tunnel open, evolution tells me that it can not send mail (as expected), but there is an ugly box around the message.

Revision history for this message
Adam Petaccia (mighmos) wrote :

That bounding box should go away as I've never seen that anywhere else in Gnome.

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. What is not HIG compliant about the dialog?

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Adam Petaccia (mighmos) wrote :

Observe how there is no bounding box around this error dialog that Nautilus creates when I attempt to unmount a volume that I don't have rights to. No other Gnome app I've seen creates the bounding box visible in the previous attachment.

Revision history for this message
Sebastien Bacher (seb128) wrote :

I've forwarded your bug upstream: http://bugzilla.gnome.org/show_bug.cgi?id=424873

Changed in evolution:
status: Needs Info → Confirmed
Changed in evolution:
status: Unknown → Unconfirmed
Revision history for this message
Michael Harold (mike-harold) wrote :

In my case the complete "Evolution Error" box reads "Mail from command failed: Requested action not taken: mail box name not allowed." Settings for pop and smtp have been double checked as being correct and as required by ISP.

Changed in evolution:
status: Confirmed → Triaged
Revision history for this message
captainron042 (georgermayfield) wrote :

I am getting the same error as Michael above. I've had the e-mail account set up for 4 months now, and I just started getting these errors a few weeks ago. I have to keep opening the messege and clicking send again over an over until it finally takes it.

Revision history for this message
David (david-kahn) wrote :

I can confirm that I am also getting the same error as captainron042, with an SSL connection to smtp.att.yahoo.com, and the problem only started recently.

I am wondering what port Evolution uses to send mail with an SSL connection. AT&T says to use port 465, and Evolution may be using port 25. AT&T may have stopped accepting SSL to Port 25 for some of their SMTP servers, and that is why mail outgoing mail sometimes fails. If so, it might be necessary for Evolution to allow setting the port, which wouldn't be a bad idea in any case.

David

Revision history for this message
Pedro Villavicencio (pedro) wrote :

that's already known upstream no need to reconfirm the bug, thanks you.

Revision history for this message
David (david-kahn) wrote : Re: [Bug 97607] Re: Evolution "can not send mail" message doesn't look HIG complient

Padro,

I didn't see any reference to my observation re. the port number, and
thought it would provide a clue to whoever is fixing the problem. Also,
I am having to press "Send/Receive" 5 to 10 times to get a message sent,
which makes this bug critical.

Thanks.

David

-----Original Message-----
From: Pedro Villavicencio <email address hidden>
Reply-To: Bug 97607 <email address hidden>
To: <email address hidden>
Subject: [Bug 97607] Re: Evolution "can not send mail" message doesn't
look HIG complient
Date: Thu, 03 Apr 2008 20:49:56 -0000

that's already known upstream no need to reconfirm the bug, thanks you.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

BTW Can you please stop attaching the "unamed" file to every report you're commenting to? thanks in advance.

Changed in evolution:
importance: Unknown → Low
Changed in evolution:
status: New → Fix Released
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

change status to Fix Released (see gnome-bugs)

Changed in evolution (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.