|
|
 | | From: | Walter Dnes (delete the 'z' to get my real address) | | Subject: | Push stopped working | | Date: | 11 Dec 2004 04:35:50 GMT |
|
|
 | It's been a long while since I last posted here. Mutt "just works",
and it's been serving me well for years. I switched my Pentium III
system over to Gentoo linux in the past couple of weeks, and I notice
that the push command no longer works. Here's the situation...
- pulling mail via POP over an ssh-tunnel from a remote ISP.
- the script is...
#!/bin/bash -i
/usr/bin/ssh -P -f -L 10110:pop3.clss.net:110 userid@remote.isp sleep 25
/usr/bin/mutt -F /home/waltdnes/.mymail/remotemuttrc
and remotemuttrc contains the line...
push Gqy
Running on Debian and CRUX linux, "push Gqy" has always retrieved my
inbox, and quit, including the "y" reply to the quit confirmation. Now
I have to manually press the "Gqy" sequence. This isn't a matter of
mere laziness. When swen was pounding away at my inbox, I had to set up
my system to automatically poll my inbox every few hours to prevent it
running out of space and bouncing legit emeail. That was also the time
I started munging my address on usenet (sigh).
I copied my old remotemuttrc file. I commented out /etc/mutt/Muttrc
entirely (The Gentoo distro defaults to maildir format, grrrrrrr). The
only change I had to make in remotemuttrc was to change from
set alternates blah blah blah
to the new format...
alternates blah blah blah
I wish mutt would stop doing things like that every so often. I presume
you also want the following info (quoted to protect against linewrap)...
> [m450][waltdnes][~]mutt -v
> Mutt 1.5.6i (2004-02-01)
> Copyright (C) 1996-2002 Michael R. Elkins and others.
> Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
> Mutt is free software, and you are welcome to redistribute it
> under certain conditions; type `mutt -vv' for details.
>
> System: Linux 2.6.9-gentoo-r6-production (i686) [using slang 10409]
> Compile options:
> -DOMAIN
> -DEBUG
> +HOMESPOOL -USE_SETGID +USE_DOTLOCK +DL_STANDALONE
> -USE_FCNTL +USE_FLOCK
> +USE_POP -USE_IMAP -IMAP_EDIT_THREADS -USE_GSS +USE_SSL -USE_SASL -USE_SASL2
> -HAVE_REGCOMP +USE_GNU_REGEX +COMPRESSED
> +HAVE_COLOR -HAVE_START_COLOR -HAVE_TYPEAHEAD -HAVE_BKGDSET
> -HAVE_CURS_SET -HAVE_META -HAVE_RESIZETERM
> +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME -CRYPT_BACKEND_GPGME
> -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT
> -ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR
> +HAVE_ICONV -ICONV_NONTRANS -HAVE_LIBIDN +HAVE_GETSID +HAVE_GETADDRINFO +USE_HCACHE
> -ISPELL
> SENDMAIL="/usr/sbin/sendmail"
> MAILPATH="Maildir"
> PKGDATADIR="/usr/share/mutt"
> SYSCONFDIR="/etc/mutt"
> EXECSHELL="/bin/sh"
> -MIXMASTER
> To contact the developers, please mail to .
> To report a bug, please use the flea(1) utility.
>
> patch-1.5.6.dw.pgp-timeout.1
> patch-1.5.6.tg.hcache.8
> patch-1.5.6.dw.mbox-hook.1
> rr.compressed
> patch-1.5.5.1.cd.edit_threads.9.5
> [m450][waltdnes][~]
--
Walter Dnes; my email address is *ALMOST* like wzaltdnes@waltdnes.org
Delete the "z" to get my real address. If that gets blocked, follow
the instructions at the end of the 550 message.
|
|
| | From: | Sven Guckes | | Subject: | Re: Push stopped working | | Date: | 11 Dec 2004 08:05:39 GMT |
|
|
| * Walter Dnes [2004-12-11]:
> I switched my Pentium III system over to Gentoo linux in the past
> couple of weeks, and I notice that the push command no longer works.
> - pulling mail via POP over an ssh-tunnel from a remote ISP.
> - the script is...
>
>#!/bin/bash -i
> /usr/bin/ssh -P -f -L 10110:pop3.clss.net:110 userid@remote.isp sleep 25
> /usr/bin/mutt -F /home/waltdnes/.mymail/remotemuttrc
>
> and remotemuttrc contains the line...
>
> push Gqy
> Running on Debian and CRUX linux, "push Gqy" has always retrieved my
> inbox, and quit, including the "y" reply to the quit confirmation.
> Now I have to manually press the "Gqy" sequence. ..
so much for "automatic download".. ;-)
but why don't you use "fetchmail" to get your mail?
starting mutt just to be using its internel
"fetch-mail" command seems like overkill.
> I copied my old remotemuttrc file.
> I commented out /etc/mutt/Muttrc entirely
does gentoo's mutt ignore /etc/Muttrc then?
> (The Gentoo distro defaults to maildir format, grrrrrrr).
;-)
> The only change I had to make in remotemuttrc was to change from
> "set alternates blah blah blah" to the new format
> "alternates blah blah blah"
ok..
> I wish mutt would stop doing things like that every so often.
> I presume you also want the following info
> (quoted to protect against linewrap)...
>> [m450][waltdnes][~]mutt -v
>> Mutt 1.5.6i (2004-02-01)
>> System: Linux 2.6.9-gentoo-r6-production (i686) [using slang 10409]
"-HAVE_TYPEAHEAD"? hmm..
(ah, well... the docs to compile options suck.)
Sven
|
|
| | From: | Walter Dnes (delete the 'z' to get my real address) | | Subject: | Re: Push stopped working | | Date: | 11 Dec 2004 17:36:35 GMT |
|
|
| On 11 Dec 2004 08:05:39 GMT, Sven Guckes, wrote:
> but why don't you use "fetchmail" to get your mail?
> starting mutt just to be using its internel
> "fetch-mail" command seems like overkill.
One less program to install/configure/etc. When swen hit, I had to
come up with a solution on my home machine *NOW*. It was a Sunday
evening when I figured out what was going on, and I had to be at work
7:45 AM the following morning. I had a choice between...
1) downloading/installing/RTFM'ing/configuring a brand new (to me)
program and hoping that it would work. With luck, I might have it
running by midnight.
2) copying a config-file for a program that I know and use, adding 1
line to the config file, and putting the mutt invocation in a script
with a "sleep 14400" command (repeat every 4 hours). This took about 10
minutes to plan/test/implement.
Being able to get it done quickly was my main worry. Since it
worked, I didn't have an overwhelming urge to "upgrade" anything. I know
that Bill Gates hates that type of attitude, but so what?
> does gentoo's mutt ignore /etc/Muttrc then?
[m450][waltdnes][~]ll /etc/Muttrc
ls: /etc/Muttrc: No such file or directory
> "-HAVE_TYPEAHEAD"? hmm..
> (ah, well... the docs to compile options suck.)
I take it that "-HAVE_TYPEAHEAD" means no typeahead buffer? And
therefore "push" can't work? How would I enable it in a build? This is
beyond my current level of knowledge.
I can dive into a configure file, look through all the various
double-dash options and then...
../configure --with-various-options && make && make install
but I don't really know what's going on "under the hood". HAVE_TYPEAHEAD
appears to require setting a macro or something. It's probably quite
simple, but I've never done it before.
--
Walter Dnes; my email address is *ALMOST* like wzaltdnes@waltdnes.org
Delete the "z" to get my real address. If that gets blocked, follow
the instructions at the end of the 550 message.
|
|
| | From: | Sven Guckes | | Subject: | Re: Push stopped working | | Date: | 11 Dec 2004 22:10:09 GMT |
|
|
| * Walter Dnes [2004-12-11]:
> On 11 Dec 2004 08:05:39 GMT, Sven Guckes, wrote:
>> but why don't you use "fetchmail" to get your mail?
>> starting mutt just to be using its internel
>> "fetch-mail" command seems like overkill.
>
> One less program to install/configure/etc. When swen hit,
> I had to come up with a solution on my home machine *NOW*.
and it is still that way *now*?
> 1) downloading/installing/RTFM'ing/configuring a
> brand new (to me) program and hoping that it would work.
sample setup files exist. why not try them *now*?
> Being able to get it done quickly was my main worry. Since it
> worked, I didn't have an overwhelming urge to "upgrade" anything.
> I know that Bill Gates hates that type of attitude, but so what?
there - one more reason, eh?! ;-)
>> does gentoo's mutt ignore /etc/Muttrc then?
>
> [m450][waltdnes][~]ll /etc/Muttrc
> ls: /etc/Muttrc: No such file or directory
my point was: mutt looks at /etc/Muttrc.
does the gentoo version have that patched?
then i hope they have adjusted the docs, too.
>> "-HAVE_TYPEAHEAD"? hmm..
>> (ah, well... the docs to compile options suck.)
>
> I take it that "-HAVE_TYPEAHEAD" means no typeahead buffer?
> And therefore "push" can't work?
it's all in the docs.... NOT.
i briefly looked at the code -
but i figured that i would lose
way too much time doing that.
> How would I enable it in a build?
> I can dive into a configure file, look through
> all the various double-dash options and then...
>
> ./configure --with-various-options && make && make install
>
> but I don't really know what's going on "under the hood".
> HAVE_TYPEAHEAD appears to require setting a macro or something.
> It's probably quite simple, but I've never done it before.
# The following templates should be used with newer automakes
# instead of acconfig.h
#
#AH_TEMPLATE([sig_atomic_t],
# [/* Define to `int' if doesn't define.])
#AH_TEMPLATE([HAVE_START_COLOR],
# [Define if you have start_color, as a function or macro.])
#AH_TEMPLATE([HAVE_TYPEAHEAD],
# [Define if you have typeahead, as a function or macro.])
simply uncomment those lines?
>
please add the ".invalid" suffix
so clients can warn users about it!
Sven
|
|
|
