Peter Bloomfield:
>> That all looks pretty harmless. I've seen similar Gtk-WARNINGS, with
>> no obvious issues. The "No cache..." message is normal for the first
>> time an IMAP folder is used, and "quitting" isn't serious.
>>
>> I don't see anything that would lead to problems.
Bob Goodwin:
On 06/16/16 14:15:10, Peter Bloomfield wrote:
Hi Bob,
On 06/16/2016 06:35:06 AM Thu, Bob Goodwin wrote:
I just went through the Balsa setup routine on an up to date Fedora
24 beta vm on the same computer I have been working on with the
following errors from debug.
Note: I now have balsa
On 06/16/16 06:51, Ed Greshko wrote:
On 06/16/16 18:35, Bob Goodwin wrote:
>(balsa:30114): Gtk-WARNING **: Allocating size to GtkSeparatorToolItem
0x559103114560
>without calling gtk_widget_get_preferred_width/height().
>How does the code know the size to allocate?
>No cache for mail.messaginge
On 06/16/16 18:35, Bob Goodwin wrote:
> (balsa:30114): Gtk-WARNING **: Allocating size to GtkSeparatorToolItem
> 0x559103114560
> without calling gtk_widget_get_preferred_width/height().
> How does the code know the size to allocate?
> No cache for mail.messagingengine.com - quitting.
> Message:
I just went through the Balsa setup routine on an up to date Fedora 24
beta vm on the same computer I have been working on with the following
errors from debug.
Note: I now have balsa running on three computers and I believe they
all work properly, two desktops and a Dell notebook, all Fe
On 05/27/16 20:56, Ed Greshko wrote:
There is one thing you may want to consider to make your life and the life of
those trying
to help a bit easier.
As a "Wildblue" customer are you allowed more than one email account with your
subscription? If the answer is "yes" you may want to think about
On 05/28/16 06:23, Bob Goodwin wrote:
> On 05/27/16 15:37, Samuel Sieb wrote:
>>>
>> You're right, I didn't explain what stunnel did. I suppose I expect people
>> to
>> investigate before running commands given by strangers. :-)
> +
>
> As a frequent contributor to this list you have acquired a
On 05/27/16 15:37, Samuel Sieb wrote:
You're right, I didn't explain what stunnel did. I suppose I expect
people to investigate before running commands given by strangers. :-)
+
As a frequent contributor to this list you have acquired a good degree
of credibility among those of us who need
On 05/27/2016 12:58 AM, Tim wrote:
On Thu, 2016-05-26 at 10:34 -0700, Samuel Sieb wrote:
Please follow the thread. He was getting a command error when
connecting with pop3s. I gave him a stunnel configuration so that he
could use wireshark to see what the command is. stunnel will do the
ssl p
On Thu, 2016-05-26 at 10:34 -0700, Samuel Sieb wrote:
> Please follow the thread. He was getting a command error when
> connecting with pop3s. I gave him a stunnel configuration so that he
> could use wireshark to see what the command is. stunnel will do the
> ssl part, so he needs to connect
Patrick O'Callaghan wrote:
>> Note that connecting to Gmail may require you to set up the account
>> with Gnome-Online-Accounts (GOA) because of recent changes in Google's
>> authentication policies, i.e. just inserting your password in Balsa may
>> not be enough
Bob Goodwin:
> Hmm, perhaps there
On 05/26/2016 04:23 PM, Bob Goodwin wrote:
There's a screenshot here: https://imagebin.ca/v/2iX1ciaZYak6
You're watching the wrong interface. You're getting the stunnel traffic
to the mail server. You need to listen on the loopback interface.
--
users mailing list
users@lists.fedoraproject.o
On 05/26/16 18:28, Samuel Sieb wrote:
On 05/26/2016 02:46 PM, Bob Goodwin wrote:
On 05/26/16 16:00, Samuel Sieb wrote:
It's still trying to do ssl. Make sure the protocol is set to pop3,
not pop3s and make sure there are no ssl checkboxes set.
--
In setup there is only one box for SSL and t
On 05/26/2016 02:46 PM, Bob Goodwin wrote:
On 05/26/16 16:00, Samuel Sieb wrote:
It's still trying to do ssl. Make sure the protocol is set to pop3,
not pop3s and make sure there are no ssl checkboxes set.
--
In setup there is only one box for SSL and that is checked.
Right, that needs to b
On 05/26/16 16:00, Samuel Sieb wrote:
It's still trying to do ssl. Make sure the protocol is set to pop3,
not pop3s and make sure there are no ssl checkboxes set.
--
In setup there is only one box for SSL and that is checked.
Here are the first few lines from /home/bobg/.balsa.config. This
On 05/26/2016 12:48 PM, Bob Goodwin wrote:
I set things, name, password, etc, back to Wildblue except for the
server localhost:110
Balsa protests: POP3 Error: Could not set up SSL when I click "Check."
This is a screenshot: https://imagebin.ca/v/2iW1LpVm2gMg
And I attached the data file it sa
On 05/26/16 13:36, Samuel Sieb wrote:
No, set the username and password to what you need for the server
you're connecting to. In this case, it's wildblue. The purpose of
this setup was so that you could use wireshark on the localhost
interface to see what command error you were getting. If
On 05/26/2016 10:12 AM, Bob Goodwin wrote:
On 05/26/16 12:38, Samuel Sieb wrote:
Are you trying to connect to wildblue or gmail? The stunnel
configuration was setup to connect to wildblue to see what the command
error was. So you need to set your username and password to be
whatever you use
On 05/26/2016 10:06 AM, Tim wrote:
Allegedly, on or about 26 May 2016, Samuel Sieb sent:
use pop3, not pop3s as the protocol.
That'll only work if the service provider has POP3 enabled. Their help
page didn't list anything but secure connections. So, a failure to use
POP3 has to be assessed
On 05/26/16 12:38, Samuel Sieb wrote:
Are you trying to connect to wildblue or gmail? The stunnel
configuration was setup to connect to wildblue to see what the command
error was. So you need to set your username and password to be
whatever you use for wildblue, but set the server to be
lo
On 05/26/16 12:49, Patrick O'Callaghan wrote:
Note that connecting to Gmail may require you to set up the account
with Gnome-Online-Accounts (GOA) because of recent changes in Google's
authentication policies, i.e. just inserting your password in Balsa may
not be enough (though I'm not a Balsa us
Allegedly, on or about 26 May 2016, Samuel Sieb sent:
> use pop3, not pop3s as the protocol.
That'll only work if the service provider has POP3 enabled. Their help
page didn't list anything but secure connections. So, a failure to use
POP3 has to be assessed with that in mind.
--
[tim@localho
On Thu, 2016-05-26 at 09:38 -0700, Samuel Sieb wrote:
> On 05/26/2016 09:21 AM, Bob Goodwin wrote:
> >
> > Ok, this produces output but I'm not sure how to configure balsa?
> > "set
> > Balsa to use localhost:110 as the incoming mail server" is clear
> > enough
> > but I left the rest as I would s
On 05/26/2016 09:21 AM, Bob Goodwin wrote:
Ok, this produces output but I'm not sure how to configure balsa? "set
Balsa to use localhost:110 as the incoming mail server" is clear enough
but I left the rest as I would set it for gmail.com and I suspect that
is not right since the output doesn't se
On 05/20/16 16:47, Samuel Sieb wrote:
On 05/20/2016 12:00 PM, Bob Goodwin wrote:
So I tried mail.wildblue.net:995 fir the incoming server address, still
get ERR: Invalid Command when I "check" incoming mail.
In that case, you are definitely using pop3s which would make using
wireshark a lot mo
On Wed, 2016-05-25 at 05:21 -0400, Bob Goodwin wrote:
> Your suggestion of Fastmail.com or something similar looks like a
> possible solution if we can endure the address change. I will consider
> trying that.
Sounds like it's time to do something like it. You've mentioned years
of annoying chan
On 05/25/16 02:20, Tim wrote:
Allegedly, on or about 24 May 2016, Bob Goodwin sent:
I have tried to respond to this message a number of times without
success due, at least in part, to problems with my ISP's email system,
presently when I try to send that particular responding message to the
list
Allegedly, on or about 24 May 2016, Bob Goodwin sent:
> I have tried to respond to this message a number of times without
> success due, at least in part, to problems with my ISP's email system,
> presently when I try to send that particular responding message to the
> list via gmail instead of
On 05/22/16 05:05, Tim wrote:
Tim:
>>I've uploaded some screenshots from my installation, here:
>>http://imgur.com/a/f11EE
+
I have tried to respond to this message a number of times without
success due, at least in part, to problems with my ISP's email system,
presently when I try to send t
Tim:
>> I've uploaded some screenshots from my installation, here:
>> http://imgur.com/a/f11EE
Bob Goodwin:
> Similar but different, not as ornate, display. I have only two
> options, POP3 or IMAP, choose pop3, and a check box for SSL.
>
> See: https://imagebin.ca/v/2hwHRtnmI5hU
>
Okay, that's
On 05/21/16 05:34, Tim wrote:
Tim:
The bottom half is where you set up the sending servers (SMTP).
Again, you get to give the configurations a name for your own
purposes, the server address (with a colon between address and the
port number), the login name and password, and some other options.
Tim:
>> The bottom half is where you set up the sending servers (SMTP).
>> Again, you get to give the configurations a name for your own
>> purposes, the server address (with a colon between address and the
>> port number), the login name and password, and some other options.
Bob Goodwin:
> yes
On 05/21/16 08:21, Bob Goodwin wrote:
>
> wireshark protests: "port 110" isn't a valid display filter: "110" was
> unexpected in this context.
You are entering that in the wrong place.
You want to be in "Capture Options", which can be reached by clicking on the
second icon
on the left which is
On 05/20/16 18:58, Samuel Sieb wrote:
It's possible that the Fedora maintainer may have added patches, but
in this case, there are none.
Ok, I was grasping at a straw there.
"Start wireshark and listen to the localhost interface with the filter
rule "port 110"."
I'm having trouble doing th
On 05/20/2016 02:43 PM, Bob Goodwin wrote:
On 05/20/16 16:47, Samuel Sieb wrote:
What difference will that make? It will still be the same software
and it seems to be more of a configuration issue.
.
I believe applications provided by dnf can have changes that may not
exist when obtained from
On 05/20/16 16:47, Samuel Sieb wrote:
What difference will that make? It will still be the same software
and it seems to be more of a configuration issue.
.
I believe applications provided by dnf can have changes that may not
exist when obtained from other sources?
In order for you to find o
On 05/20/2016 12:00 PM, Bob Goodwin wrote:
So I tried mail.wildblue.net:995 fir the incoming server address, still
get ERR: Invalid Command when I "check" incoming mail.
In that case, you are definitely using pop3s which would make using
wireshark a lot more difficult. See below for a solution
On 05/20/16 13:15, Tim wrote:
---
I've just installed Balsa, on my out-of-date system, to have a play, and
got it working within a couple of minutes of fiddling. I had to
manually create a /var/spool/mail/timtesting file to make it happy, as
root, then chown tim:mail /var/spool/mail/
On Fri, 2016-05-20 at 12:15 -0400, Bob Goodwin wrote:
> After adding my username via gedit on the bottom line of
> "config-private" below, sending a message from balsa compose requested
> a password and the message is received by Thunderbird. I then checked
> remember password too.
>
> [bobg@Bo
On 05/20/16 10:41, Tim wrote:
Perhaps there is
>something in the configuration that I am missing and what is being
>sent is not what I expect.
Okay, after looking back through the thread, is wildblue.net different
from your ISP? They may require you to authenticate with them as one of
their use
On Fri, 2016-05-20 at 10:13 -0400, Bob Goodwin wrote:
> I sent test messages to my usual e-mail address, e.g.
> bobgood...@wildblue.net or my working gmail address, both entered via
> the balsa "compose" and/or set-up GUI. However this leaves me
> wondering about what my ISP is actually getting.
On 05/20/16 03:57, Tim wrote:
On Thu, 2016-05-19 at 12:23 -0400, Bob Goodwin wrote:
>I haven't been able to make any sense out of the wireshark data yet
>but this morning I tried again from gnome instead of xfce, the problem
>remains the same, however trying to send a test message from Balsa
>pr
On Thu, 2016-05-19 at 13:35 -0400, Bob Goodwin wrote:
> I subscribed to a balsa list a week or more ago but got no response
> and saw no activity there at all.
You might want to give the list the details, in case it's been
superseded, and someone here knows the alternative.
--
tim@localhost ~]$
On Thu, 2016-05-19 at 12:23 -0400, Bob Goodwin wrote:
> I haven't been able to make any sense out of the wireshark data yet
> but this morning I tried again from gnome instead of xfce, the problem
> remains the same, however trying to send a test message from Balsa
> produced an error:
>
> "Bals
On 05/19/16 13:21, Patrick O'Callaghan wrote:
If it works with other mail clients (e.g. Thunderbird) then it's a
configuration issue. I can't help you with Balsa config, but I presume
your ISP has a help page on what you need to set up.
poc
.
Yes, but I have probably set up e-mail accounts on T
On Thu, 2016-05-19 at 13:01 -0400, Bob Goodwin wrote:
> On 05/19/16 12:37, Patrick O'Callaghan wrote:
> >
> > >
> > > >
> > > > "Balsa Relaying refused550: Relaying Refused
> > > > Message left in your Outbox."
> > > >
> > > >
> > > > Which once more makes me wonder if it is som
On 05/19/16 12:37, Patrick O'Callaghan wrote:
>"Balsa Relaying refused550: Relaying Refused
> Message left in your Outbox."
>
>
>Which once more makes me wonder if it is something my ISP is doing
>that
>causes the no-connect problem?
Looks like your ISP has a no-relay policy, whic
On Thu, 2016-05-19 at 12:23 -0400, Bob Goodwin wrote:
> I haven't been able to make any sense out of the wireshark data yet
> but
> this morning I tried again from gnome instead of xfce, the problem
> remains the same, however trying to send a test message from Balsa
> produced an error:
>
> "B
On 05/18/16 07:55, g wrote:
Dunno where to start ...
>
===>
hello Bob.
from main menu;
Edit > Preferences > Capture
also, look at "Name Resolution", decide
what address numbers you want resolved.
hth.
.
I haven't been able to make any sense out of the wireshark data yet but
this m
On 05/18/16 21:36, Bob Goodwin wrote:
> Edit > Preferences > Capture
>
> I set to Ethernet port, seems like that ought to show everything?
>
> Default Interface: enp1s0
>
> I would like it to show data for "mail.wildblue.net." Don't see where to tell
> it that ...
In the "Capture Options" yo
On 05/18/16 07:55, g wrote:
On 05/18/2016 03:44 AM, Bob Goodwin wrote:
<<<>>>
Ok, I have wireshark installed now but using it appears to be a
formidable task! First it wants an interface and I have not been able to
satisfy that?
Dunno where to start ...
===>
hello Bob.
from main menu;
On 05/18/2016 03:44 AM, Bob Goodwin wrote:
<<<>>>
> Ok, I have wireshark installed now but using it appears to be a
> formidable task! First it wants an interface and I have not been able to
> satisfy that?
>
> Dunno where to start ...
>
===>
hello Bob.
from main menu;
Edit > Preference
On 05/17/16 20:33, Samuel Sieb wrote:
On 05/17/2016 02:37 PM, Bob Goodwin wrote:
When I click on "Check" it says it is checking the mail at "POP3:
mail.wildblue.net" but then produces "ERR Invalid Command"
That sounds like Balsa is sending a command that your pop server isn't
understanding. T
On 05/17/2016 02:37 PM, Bob Goodwin wrote:
When I click on "Check" it says it is checking the mail at "POP3:
mail.wildblue.net" but then produces "ERR Invalid Command"
That sounds like Balsa is sending a command that your pop server isn't
understanding. Try using wireshark to see what it is.
On 05/12/16 06:38, Ed Greshko wrote:
FWIW, I installed balsa on a VM and was able to collect mails from gmail.
.
Well I think I have tried everything suggested without much success.
When I click on "Check" it says it is checking the mail at "POP3:
mail.wildblue.net" but then produces "ERR In
On Thu, 2016-05-12 at 10:48 -0400, Tony Nelson wrote:
> if you have another email account to check from another provider, try
> it (even if it won't have any mail).
To test email on-demand, send yourself emails.
--
tim@localhost ~]$ uname -rsvp
Linux 3.19.8-100.fc20.i686 #1 SMP Tue May 12 17:4
On 16-05-12 03:53:49, Bob Goodwin wrote:
> I have installed Balsa in this updated Fedora 23 computer, it runs but
> will not connect to the mail server.
>
> I can click on "check" and it appears to be checking for mail but
> produces an error message ending in "ERR Invalid Command." I've been
>
On 05/12/16 15:53, Bob Goodwin wrote:
> I have installed Balsa in this updated Fedora 23 computer, it runs but will
> not connect
> to the mail server.
>
> I can click on "check" and it appears to be checking for mail but produces an
> error
> message ending in "ERR Invalid Command." I've been
On 10-12-07 13:15:20, Tony Nelson wrote:
> Are other balsa users seeing wrong or missing icons in the balsa main
> window toolbar or message status columns?
> https://bugzilla.redhat.com/show_bug.cgi?id=660732
The bug is fixed by balsa-2.4.9-1.fc14 which is now in updates-testing
(but wasn't w
On Tue, 07 Dec 2010 13:20:29 -0500
Tony Nelson wrote:
> Do other balsa users find balsa vanishing during use at unpredictable
> times? I had to rebuild balsa --without-threads to make it stable in
> F12, and (as I just got it working at all again) I've done the same on
> F14. If it happens t
60 matches
Mail list logo
