Re: trying repository mutt again

2014-11-09 Thread JaviMicro

Hi,

> echo "Test" | /usr/bin/mutt -s Hello d...@dalekelly.org
> Error in /home/dale/.muttrc, line 353: smtp_user: unknown variable
> source: errors in /home/dale/.muttrc
> SMTP session failed: 530 authentication required
> Could not send the message.

I have needed some days to understand your problem.

All we need read carefully the error:
 smtp_user: unknown variable

After reading manual pages of both stable and devel mutt releases:
  http://www.mutt.org/doc/manual/manual-6.html
  http://www.mutt.org/doc/devel/manual.html
we can see that both
   imap_user
   pop_user
are valid variables, BUT PLEASE NOTE THAT
   smtp_user
is_not_a_valid_variable!.


Please use both email address and SMTP server combined in one line,
something like:
   set smtp_url="smtps://myusern...@dalekelly.org@smtpout.secureserver.net:465"
   set smtp_pass="MYPASSWORD"

Regards
--
Javi


Re: Troubles with html attachments

2015-02-08 Thread JaviMicro
* On  8 feb 2015, Philippe Delavalade wrote:

> 
> When I receive an attachment in html format, I hope it is read with lynx
> but in fact, I can see it as a txt file. In ~/.mailcp I have the line : 
> text/html; lynx -force_html '%s'; description=HTML Text; nametemplate=%s.html
> 
> I have also tried 
> text/html; /usr/bin/lynx -force_html %s; needsterminal; copiousoutput; 
> nametemplate=%s.html
> 
> But neither works.
> 
> In the mime.types file I have just the line
> text/html html htm shtml
> 

You need:

1- To define a viewer in mailcap for text/html attachments (you have
already done it)


2- 'auto_view' parameter in .muttrc:
auto_view text/html

Read the section with this sentence
"automatically viewing MIME attachments while in the pager"
in manual:
http://www.mutt.org/doc/devel/manual.html#auto-view


3- Maybe you also need an 'alternative_order' parameter in .muttrc.



> attachments   +A */.*
> attachments   +I text/plain
> attachments   +I text/html
> 
> I don't understand what they mean and didn't find explanations in the manual.
> 

For 'attachments', look here:
http://www.mutt.org/doc/devel/manual.html#ex-attach-count

--
J


Re: Troubles with html attachments

2015-02-11 Thread JaviMicro
* On  9 feb 2015, Philippe Delavalade wrote:

> > > I want to do 'v' and then click on the html attachment as I do 
> > > successfully
> > > with mpeg or pdf attachments.
> > > 
> > > If I do this with html, I see things like
> > > 
> > > 
> > > 
> > > ...
> > > ...
[...]
> 
> I tried "m" but it does nothing...

Let's we see the list of your keybindings.

In any of your messages with _html_ attachments, please
press 'v' to see list of attachments, and then press '?' to get
the list of active binding keys (It is a long list).

Search in the second column following entries:
"view-attach"
"view-text"
"view-mailcap"

Send to the maillist the keybindings of these entries.
For example:
   view-attach
T  view-text
m  view-mailcap


Repeat the same procedure in a message with _pdf_ or _mpeg_ attachment.

--
J


Re: mutt and archivemail

2015-02-19 Thread JaviMicro
* On 19 feb 2015, Philippe Delavalade wrote:

> Hi.
> 
> I use archivemail which produces, for instance, inbox_archive.gz.
> 
> When issuing the command
> 
> mutt -f inbox_archive.gz
> 
> I have an error message because it is not a mailbox.
> 
> Previously, before my migration from debian to slackware, this worked
> fineĀ ; I can't find what to configure so that it works. Maybe it's not a
> mutt problem but...
> 

Hi,


Debian uses a patch

http://ftp.de.debian.org/debian/pool/main/m/mutt/mutt_1.5.21-6.2+deb7u3.diff.gz
that includes non-official support for compressed folders (starting at line 
"debian/patches/features/compressed-folders" in referenced diff above).


Slackware does not include that patch, so no support for compressed folders.
You would need to include the patch and compile yourself in Slackware.

--
J


Re: mutt configuration problems for gmail

2015-03-27 Thread JaviMicro
* On 26 mar 2015, Peng Yu wrote:

> Hi,
> 
> ~$ mutt
> Error in /Users/py/.muttrc, line 10: trash: unknown variable
> Error in /Users/py/.muttrc, line 11: any_label: unknown variable
> Error in /Users/py/.muttrc, line 14: header_cache: unknown variable
> Error in /Users/py/.muttrc, line 15: message_cachedir: unknown variable
> Error in /Users/py/.muttrc, line 19: smtp_url: unknown variable
> Error in /Users/py/.muttrc, line 20: smtp_pass: unknown variable
> Error in /Users/py/.muttrc, line 26:
> source: errors in /Users/py/.muttrc
> Press any key to continue...
> 

Hi,

The problem may reside in /Users/py/.muttrc syntax.


Could you post your complete .muttrc? 
(Obfuscate your passwords and confidential data prior to posting).




Re: sending from mutt to fastmail back from the dead?

2015-05-20 Thread JaviMicro
* On 19 may 2015, Tom Fowle wrote:

> All,
> Tried to solve this a year or so back, gave up but now trying again.
> running Debian wheezie
> Below is my .muttrc file for my fastmail account with passwords removed.
> Mutt receives fine, but when sending says:
> "connecting to fastmail.fm
> connection refused could not connect to fastmail.fm



Hi Tom,

welcome, again ;-)


Please, follow all these steps:

1) backup your muttrc config file
mv ~/.muttrc ~/muttrcbackup

2) It is difficult to debug your problem because
your muttrc has many lines. 

Please, compose a new & simplified ~/.muttrc, 
with ONLY these five lines:


set from="Tom Fowle "
set mbox = "~/mbox"
set editor = joe
set smtp_url="smtps://wa6iv...@fastmail.fm@mail.messagingengine.com:465"
unset smtp_pass
- 

Dont use $my_user/$my_pass/$my_smtp_server variables.
Dont put your password in muttrc: mutt will ask you to enter the password
manually. It will let us determinate where the problem is.

3) open muttrc with this command line:
mutt -F ~/.muttrc

4) send a message to someone. Use my own address, if you want

5) post your success or failures in this list.


PS: do you have a paid Fastmail account, or a free trial account?


Regards,
--
Javi


Re: Cannot render Spanish accents in builtin pager

2015-06-02 Thread JaviMicro
* On  2 jun 2015, bastian-muttu...@t6l.de wrote:

>
> I am happy to hear that.
> My understanding is that the configure script checks first for ncurses
> and afterwards for ncursesw. Thus, it will prefer the use of ncursesw
> over ncurses.
> 

True. See:
http://dev.mutt.org/hg/mutt/file/70b85d8b232b/configure.ac#l271
and check how occurrence of "ncursesw" has precedence over "ncurses"


A simple:
ldd /usr/bin/mutt
gives which ncurses* library is used by mutt binary.