muttzilla-users Mailing List for muttzilla

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Has anyone been successful at getting syplpheed to work with muttzilla?
Sylpheed starts OK, but the "TO" field doesn't get filled in.
Thanks in advance for any help that you can offer!

George

On Wed, Jul 25, 2001 at 12:20:35PM -0700, Darlene Wong wrote:
> I am having trouble installing muttzilla for use with Mozilla.  I got it

Sorry for the slow reply.  I've just created a FAQ for
muttzilla/mozilla issues:  http://www.pteranodon.org/mutt/faq.html

Brian
-- 
A computer without COBOL and Fortran is like a piece of chocolate cake
without ketchup and mustard.

Hi,

I am having trouble installing muttzilla for use with Mozilla.  I got it
working with Netscape, and I followed the exact same steps in the README
file for both browsers, but it doesn't work with Mozilla.  Could
somebody please let me know what the difference is between installing
muttzilla for Mozilla and for Netscape?  Thank you!

dw

Hello,

Is there any APIs provided by APIs which i can use to develop a GI
application from which to send mail.

Regards

Manoj

To Get That Quote Absolutely Free Now!

We can save you time and money! 
We have quick access to car quotes!
We have all makes and models available to you.
Now all you have to do to take advantage of this free,
no-hassle service is simply click on the link below,
to get low prices on all makes and models of new and used cars,
without having to negotiate with a
dealer. It's painless and stress-free!

http://193.231.217.172/autos.pl

This mailing is done by an independent marketing co.
We apologize if this message has reached you in error.
Save the Planet, Save the Trees! Advertise via E mail.
No wasted paper! Delete with one simple keystroke!
Less refuse in our Dumps. This is the new way of
the new millennium.

To be removed from hearing about all future
products and services please send
a seperate email to: mailto://re...@nj...

On Wed, Oct 11, 2000 at 10:18:47AM -0700, Brian D. Winters wrote:
> Copy the attached file (which someone else sent me independently,

Sigh...now it's atached.

Brian

On Sun, Oct 08, 2000 at 07:40:36AM -0400, David Boles wrote:
> Maher Awamy, one of the authors of Pronto, suggested that I try
> Muttzilla so that I might be able to use Pronto for Netscape mailto:'s.
> Not being any kind of a programer and a Linux user for only about three
> months, I am from DOS and OS/2 Warp, I am asking for some help.
> 
> What do I change, write, or whatever do get Mutzilla and Netscape to
> work together?

Copy the attached file (which someone else sent me independently,
within a day or so of your question) into the muttzilla-0.40 source
directory, and change this line in the Makefile:

MAILERLIBS = mutt pine dtmail VM tin

to:

MAILERLIBS = mutt pine dtmail VM tin pronto

Then run make, do the install, and set the following in your rc file
(either /etc/muttzilla.conf, or ~/.muttzillarc):

mailscript=mzmail.sh   # The attached file doesn't provide pronto
                       # support for the .py, just the .sh.
mailprog=pronto
mailargs=pronto

The rest of the installation instructions should be the same.  I use
redhat, which is closely related to mandrake, so the installation
itself should be relatively painless.

Good luck, and let us know if you run into any specific problems along
the way.

Brian

Maher Awamy, one of the authors of Pronto, suggested that I try
Muttzilla so that I might be able to use Pronto for Netscape mailto:'s.
Not being any kind of a programer and a Linux user for only about three
months, I am from DOS and OS/2 Warp, I am asking for some help.

What do I change, write, or whatever do get Mutzilla and Netscape to
work together?

Linux-Mandrake v7.1
Netscape Navigator v4.75
Pronto v2.2.1 (www.muhri.net/pronto)

-- 

David Boles
dg...@em...

Sorry for the slow reply.  I'm in the process of graduating...

On Thu, Sep 21, 2000 at 05:46:15PM +0200, ola...@av... wrote:
> ..works fine with Debian 2.2 (potato)
> and netscape naviator-smotif
> (Package: navigator-smotif-473, is glibc22-based)
> and muttzilla-0.40

Good.  I'm glad the latest Debian uses glibc navigator.  I'll update
the errata.

> I think it is ready for a debian package.

Ok.  I won't be the one creating it, but everything is GPL or LGPL, so
someone else certainly can.

> subjects are taken from the link, body text as well.
> I could not (yet) experience any problems from the library-

That's good to hear.

Brian

..works fine with Debian 2.2 (potato)
and netscape naviator-smotif
(Package: navigator-smotif-473, is glibc22-based)
and muttzilla-0.40

I think it is ready for a debian package.
subjects are taken from the link, body text as well.
I could not (yet) experience any problems from the library-

Olaf Schulz

On Wed, Sep 13, 2000 at 04:39:55PM +0200, Ulrich Scholz wrote:
> Oops, I just read the note on Birans page, so I send my question again.

I answered his personal message before seeing this one to the list.
After getting more info from him, his problem is that he gets mutt
when he tries to browse news.  The ERRATA file mentions this as known
behavior with older versions of the browser (A bug in Communicator?!?!
Nah...), roughly 4.6 and earlier.  He is using 4.72, which I thought
was a working version, but since there are some really huge security
problems with < 4.75, I recommended an upgrade anyway.

Brian

Oops, I just read the note on Birans page, so I send my question again.

Hi everybody,

I just tried muttzilla and it's a thing I waited for a long time.

... but I only want to use it for email.  For news, I want to use the built-in
news reader.  How do I configure muttzilla such that get this functionality.

Thanks, Uli

-- 
Ulrich Scholz

sc...@in...
http://www.intellektik.informatik.tu-darmstadt.de/~scholz/

On Fri, Aug 04, 2000 at 01:41:02PM -0700, Brian D. Winters <bri...@pt...> wrote:
> >     - Changed copyright string for Tru64's compiler
> 
> I wonder if gcc is broken in allowing embedded newlines in strings, or
> are all of the unix vendors (well, Compaq, Sun and SGI at least)
> shipping horribly outdated and limited cc's?  My GNU bias makes me
> think it is the latter, but I haven't actually read the C standards to
> be sure.

    As a user of both, I think I have a balanced perspective.  To be
honest, Compaq's cc is quite good.  It produces *much* better code than
gcc and is very standards compliant (evidence: some Linux-Alpha Beowulf
clusters run one DEC/Compaq machine to compile code on).  Often, gcc has
a lot of extensions to the standards and lets a lot of non-compliant
code go by without so much as a warning.

    That said, I haven't read the C standard on it.

-- 
Bob Bell <bo...@zk...>
-------------------------------------------------------------------------
 "Linux, WinNT, MS-DOS - also known as the Good, the Bad and the Ugly."
   -- Anonymous

On Mon, Jul 31, 2000 at 02:23:03PM -0400, Bob Bell wrote:
>     I've made a few changes to muttzilla on my system.  I've attached
> the patch I use to build muttzilla, although it wouldn't be appropriate
> for everyone.  Some of my changes should probably go into the CVS tree,
> though.

Setting up autoconf is on my to-do list.  That should hopefully fix
some of the problems you mention.  In particular...

>     - Adjusted CFLAGS to proper warning string ('-w0') on Tru64 UNIX.

Autoconf may not handle this?  Since I write perfect code, maybe I
don't need to show warnings after all... :)

>     - Changed copyright string for Tru64's compiler

I wonder if gcc is broken in allowing embedded newlines in strings, or
are all of the unix vendors (well, Compaq, Sun and SGI at least)
shipping horribly outdated and limited cc's?  My GNU bias makes me
think it is the latter, but I haven't actually read the C standards to
be sure.

>     - Added '#include <string.h>' to mzbase.c

Oops.

>     Also, I had to change the lib/muttzilla/mutt script to start mutt.
> I believe there was a problem with where the To address was being put on
> the command line.  I've attached my mutt script.

Yeah, somewhere along the way I screwed that up, and I'm not sure why
or how I didn't notice it, since I do test with mutt.  I have some
uncommitted changes that I need to bring into the sourceforge CVS
tree, and I think this is one of them.

Thanks for the info.

Brian

    I've made a few changes to muttzilla on my system.  I've attached
the patch I use to build muttzilla, although it wouldn't be appropriate
for everyone.  Some of my changes should probably go into the CVS tree,
though.

    The changes I've made [as I recall, it's been a while :-) ]:

    - Adjusted CFLAGS to proper warning string ('-w0') on Tru64 UNIX.
    - Changed LDFLAGS to Tru64 equivalent
    - Change `make clean` to remove additional file on Tru64
    - Changed copyright string for Tru64's compiler
    - Added '#include <string.h>' to mzbase.c

    The first three items are specific to Tru64 UNIX and would probably
be solved by using the GNU distribution system (autoconf, automake,
libtool, etc.).  The fourth was to allow proper compilation on Tru64,
but should proper be changed in the main source tree.  The final item
should also be changed to allow compilation on other platforms.

    Also, I had to change the lib/muttzilla/mutt script to start mutt.
I believe there was a problem with where the To address was being put on
the command line.  I've attached my mutt script.

-- 
Bob Bell		Compaq Computer Corporation
Software Engineer	110 Spit Brook Rd - ZKO3-3/U14
TruCluster Group	Nashua, NH 03062-2698
bo...@zk...	603-884-0595

FYI:  It looks like I may finally have the time to work on muttzilla
again.  I'm setting up muttzilla with sourceforge.  -users and
-announce mailing lists are up, but the CVS repository hasn't been
populated yet.  Hopefully there will be a slightly more user-friendly
version available soon.

Anyway, Brad's questions...

On Fri, Jul 28, 2000 at 06:42:21PM -0500, Brad Cramer wrote:
> Is anyone suing muttzilla with Eterm? I am having a heck of a time getting

I don't remember hearing from anyone who is using Eterm, but that
doesn't mean much.

> it configured to work properly. I set mailterm=Eterm in my muttzilla.conf
> file it starts and work but I get an error box (I think these errors have to
> do With Eterm)

What does the error box say?  My guess is that Eterm doesn't accept
the same arguments as xterm and clones (like rxvt), and is choking on
them.

> I try to set mailterm=Eterm -t mutt which is how I normaly
> call mutt but I get an error about expecting = but gettin -t instead. If
> someone could give me some ideas I would be thankful.

That definitely won't work.  To get the effect you desired from a
parsing standpoint, you would need to quote it like this:

mailterm="Eterm -t mutt"

However, please don't do that.  You would find that the argument
handling doesn't behave the way you want it to behave.  That mailterm
line will cause mzmail.{py,sh} to attempt to execute a program named
Eterm\ -t\ mutt.  I doubt that is what you intend.

[Installing an Eterm rpm...`man Eterm`...]

Well, -t ("load theme") is definitely something normal xterm doesn't
do.  You have stumbled upon the reason why muttzilla.so does as little
as possible, handing off most of the interesting work to a wrapper
script:  it will be relatively easy for you to hack up mzmail.{py,sh}
to properly spawn your Eterm, or to ditch mzmail.{py,sh} entirely and
write your own simple wrapper script that just spawns mutt in an Eterm
for you.

Brian

This is a test message to see if the list is working properly.

Brian

2000	Jan	Feb	Mar	Apr	May	Jun	Jul (3)	Aug (2)	Sep (3)	Oct (4)	Nov	Dec (1)
2001	Jan	Feb	Mar	Apr	May (1)	Jun	Jul (1)	Aug (1)	Sep	Oct	Nov	Dec
2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep (1)	Oct	Nov	Dec

muttzilla-users Mailing List for muttzilla

muttzilla-users — General discussion and questions on using muttzilla.