If you use balsa, in Fedora 26 you may have trouble sending mail
(see Bug 1479177 - since upgrade balsa is no longer able to send
emails[1]).
balsa uses libesmtp to send the mail, but libesmtp was accidentally
built without SSL support (fixed in my Bug 1483350 - libesmtp built
w/o SSL support
; there are strange problems that happen. If the install works right off
> then Balsa seems to just work.
It's disconcerting to see a pile of warnings when you run programs from
the command line, sometimes they are completely unimportant to you, only
of interest to those writing the software, but
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?
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 - quit
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
ngs worked again. Until I booted
Monday morning and found that I was locked out of my email account, so
after thrashing around again I was back on the phone at four in the
morning, got someone who remembered me and was aware of my problem and
he fixed things again.
Since I last wrote ab
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
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
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
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
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
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
Name=Inbox
[mailbox-Outbox]
Path=/home/bobg/mail/outbox
Type=LibBalsaMailboxMbox
Name=Outbox
As a side note, the same Wildblue configuration settings that I use for
Thunderbird also work with Claws. It's just Balsa that chokes ...
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db
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
. If it's not
doing that now, then forget this whole thread and connect directly as
pop3s. :-)
--
+
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 screens
for wildblue, but set the server to be
localhost:110. And use pop3, not pop3s as the protocol.
--
+
Wildblue actually, but I just thought I'd try Gmail this morning and see
if balsa would work with the same settings as it does on Thunderbird.
Either way my question seems to be the same, perhaps
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
to be
localhost:110. And use pop3, not pop3s as the protocol.
--
+
Wildblue actually, but I just thought I'd try Gmail this morning and see
if balsa would work with the same settings as it does on Thunderbird.
Either way my question seems to be the same, perhaps it doesn't matter.
perhaps I should
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
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.
--
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
> >
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 outp
n "stunnel stunnel.conf". Now, set Balsa to use
localhost:110 as the incoming mail server. Start wireshark and listen
to the localhost interface with the filter rule "port 110". Tell
Balsa to check for emails. Hopefully you get the same error message.
Right-click one of the
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
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
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
spam
and dumped without notice.
In addition I found that they had disabled my e-mail account which lead to
problems with my list subscription, the whole mess has been a nightmare with a
lot of time spent on the telephone. There has been no explanation for any of
this.
I am still interested in mak
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,
is greyed-out, something else?
+
I can put the cursor on the box, nothing happens, typing produces
nothing. Greyed out? I dunno what to call it since Balsa acts
differently, block turns black when the cursor is on it, white when I
click, and should then accept input, in this case does not.
I
the text entry area is greyed-out, something else?
> I completely removed every vestige of balsa I could find and
> re-installed anew with dnf install balsa. No improvement resulted but
> I know there's nothing corrupted from my earlier efforts ...
Remove and reinstalling only affect
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
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
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
uot;. Now, set Balsa to use
localhost:110 as the incoming mail server. Start wireshark and listen
to the localhost interface with the filter rule "port 110". Tell
Balsa to check for emails. Hopefully you get the same error message.
Right-click one of the packets and select "
at command is causing the trouble, you
can use stunnel (you will probably need to install it). Put the
following lines in a file called stunnel.conf:
foreground=yes
syslog=no
[pop3]
client=yes
accept=localhost:110
connect=mail.wildblue.net:995
As root, run "stunnel stunnel.conf". N
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 pas
m 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@Box10 .balsa]$ cat config-private
[mailbox-1]
Username=bobgood...@wildblue.net
Password=encrypted gibberish
[smt
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 I
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 f
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@loc
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
> produ
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 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.
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
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
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:
"Balsa Relaying refused550: Relaying Refused
Message left in your Outbox."
Which once more makes me
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"
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 >
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 p
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/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" bu
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
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 "E
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 &
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
through the account set up pr
The balsa email program draws unthemed on my system after upgrading to
F20. Actually, the adwaita theme works, but none of the other themes
do. I get no complaints from Gtk in .xsession-errors or journalctl when
changing themes. Other programs are OK.
Does anyone else see this or know what
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
--
TonyN.:' mailto:tonynel
Are any balsa users unable to fetch new mail if NetworkManager is not
running? I needed to rebuild balsa --without-nm in order to get it to
work here, where NetworkManager is not used.
https://bugzilla.redhat.com/show_bug.cgi?id=660735
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 to others, I'll submit a bug
On Tue, 07 Dec 2010 13:20:29 -0500
Tony Nelson tonynel...@georgeanelson.com 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 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
66 matches
Mail list logo
