Building A Complete Email Setup For Sl-c3000

[daniel3000]

Hello,

I have started the project to build a complete convenient to use and configurable email setup. I write down each step I do, so I'll be able to provide step-by-step instructions to anyone who is willing to duplicate the setup.

However, I ran into a problem I'd like to discuss here. My progress: fetchmail 6.2.5 works well (compiled from source), all other programs are installed at least (mutt_1.5.8-1_arm.ipk, procmail 3.22 compiled from sources and nbsmtp 0.99 compiled from sources).

I'm following the instructions on http://www.gentoo.de/doc/en/guide-to-mutt.xml

I passed the fetchmail test (fetchmail wrote the downloaded email intot eh /var/spool/mail/zaurus file) and tried to configure procmail. I have the MAILDIR on /hdd3/Documents/Mail, i.e. on a vfat drive. procmail reports errors on each access to that directory (writing the log file and changing to the directory:

Code: [Select]

...
fetchmail: POP3< +OK message follows
reading message xy@pop.gmx.net:11 of 18 (2728 octets)
"***********procmail: Couldn't chdir to "/hdd3/Documents/Mail
procmail: Error while writing to "/hdd3/Documents/Mail/procmail_log
"
"rocmail: Skipped "
"rocmail: Skipped "
"rocmail: Skipped "
"rocmail: Skipped "
...

..and so on.

Anyone have an idea what the problem could be? On the vfat drive, all owner and group info is shown as "root", but OTOH all files and dirs are world readable and writable. Of course I have created the directory /hdd3/Documents/Mail.

Thanks for any input!



daniel

[daniel3000]

Okay, I solved my own problem:

I created .procmailrc using an editor which puts CRLF at each end of line, which screwed procmail totally. Hence also the strange lines

"rocmail...

and so on.
Now, with only LF at the end of lines, it works nicely.

Now I'll continue my work on the mail setup.

daniel

[maslovsky]

Let us know when you have packages ready, would be great to have them in the Cacko feed...

[daniel3000]

Let us know when you have packages ready, would be great to have them in the Cacko feed...
[div align=\"right\"][a href=\"index.php?act=findpost&pid=88738\"][{POST_SNAPBACK}][/a][/div]

Well, I'm stuck with two strange problems (or maybe it is only one problem):

1. mutt and the qkonsole (and all other consoles i tried) seem to be incompatible.
When I start mutt on the console after terminating qtopia, it displays well (colors, and the arrows for thread visualiziation). Under the qkonsole, the vertical arrow lines are screwed up and no colors are displayed.

2. Under all environments (qkonsole and outside qtopia), the german special characters (Umlauts) are displayed as 3-digit codes with a backslash. I could not find any locale / muttrc-charset setting which decodes the Umlauts correctly. However, I am able to enter the umlauts via keyboard on the console (Fn-a gives ä (ae) etc.), so the fints contain these characters. Strange.

I'd appreciate any pointers.

I also tried to compile mutt from source (I think the mutt package I have installed is a Japanese one and thus may be unaböe at all to decode European characters correctly), but was unable to, because a tool called "aclocal" is missing. That is said to be in the package automake, but in order to compile that one, I need the package autoconf... and there I gave up for now.

Any pointers would be much appreciated!

All the other setup works well already. I only have to find a convenient way to use mutt offline. It's by default optimized for usage in a always-online-environment.

But I'm still hoping to be able to provide an all-in-one package soon.

daniel

[maslovsky]

1. mutt and the qkonsole (and all other consoles i tried) seem to be incompatible.
When I start mutt on the console after terminating qtopia, it displays well (colors, and the arrows for thread visualiziation). Under the qkonsole, the vertical arrow lines are screwed up and no colors are displayed.

You may try different environment variables, ex TERM=linux, etc.

Under all environments (qkonsole and outside qtopia), the german special characters (Umlauts) are displayed as 3-digit codes with a backslash. I could not find any locale / muttrc-charset setting which decodes the Umlauts correctly. However, I am able to enter the umlauts via keyboard on the console (Fn-a gives ä (ae) etc.), so the fints contain these characters. Strange.

There must be some info on that in mutt docs

I also tried to compile mutt from source (I think the mutt package I have installed is a Japanese one and thus may be unaböe at all to decode European characters correctly), but was unable to, because a tool called "aclocal" is missing. That is said to be in the package automake, but in order to compile that one, I need the package autoconf... and there I gave up for now.

You gave up too soon     Install the following packges and you'll be able to build most of the programs:

Perl
m4
autoconf
automale

[jochen-02]

1. mutt and the qkonsole (and all other consoles i tried) seem to be incompatible.
When I start mutt on the console after terminating qtopia, it displays well (colors, and the arrows for thread visualiziation). Under the qkonsole, the vertical arrow lines are screwed up and no colors are displayed.

Probably you found it out yourself but embeddedkonsole displays colors. No umlauts here so far. Which environment variables do you have set to get umlauts?

2. Under all environments (qkonsole and outside qtopia), the german special characters (Umlauts) are displayed as 3-digit codes with a backslash. I could not find any locale / muttrc-charset setting which decodes the Umlauts correctly.

Did you find a solution meanwhile?

[daniel3000]

1. mutt and the qkonsole (and all other consoles i tried) seem to be incompatible.
When I start mutt on the console after terminating qtopia, it displays well (colors, and the arrows for thread visualiziation). Under the qkonsole, the vertical arrow lines are screwed up and no colors are displayed.

Probably you found it out yourself but embeddedkonsole displays colors. No umlauts here so far. Which environment variables do you have set to get umlauts?

2. Under all environments (qkonsole and outside qtopia), the german special characters (Umlauts) are displayed as 3-digit codes with a backslash. I could not find any locale / muttrc-charset setting which decodes the Umlauts correctly.

Did you find a solution meanwhile?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=115610\"][{POST_SNAPBACK}][/a][/div]

Hi Jochen,

no solution so far, unfortunately.
Under qconsole, I now have all the colors I need etc., it works very well. On ly remaining problem is that Umlaut issue. I discussed it woth very knowledgable people on the mutt-users mailinglist. It is probably a problem with the locale configuration on the Zaurus, because many files are missing for a complete locale configuration. I don't remember the details. I have set charset="us-ascii" for mutt, so now I don't have the annoying three-digit octal codes for Umlauts anymore, but much more convenient quotation marks (one per Umlaut).

daniel

[jochen-02]

Under qconsole, I now have all the colors I need etc., it works very well. On ly remaining problem is that Umlaut issue. I discussed it woth very knowledgable people on the mutt-users mailinglist. It is probably a problem with the locale configuration on the Zaurus, because many files are missing for a complete locale configuration.

If it is only the lack of some locale files, did you try to copy them from a standad Linux installation (on a PC)?

I don't remember the details. I have set charset="us-ascii" for mutt, so now I don't have the annoying three-digit octal codes for Umlauts anymore, but much more convenient quotation marks (one per Umlaut).

That is weird, as I get the escaped octals even with charset=us-ascii. Which environment variables are set for your mutt sessions?

[daniel3000]

Under qconsole, I now have all the colors I need etc., it works very well. On ly remaining problem is that Umlaut issue. I discussed it woth very knowledgable people on the mutt-users mailinglist. It is probably a problem with the locale configuration on the Zaurus, because many files are missing for a complete locale configuration.

If it is only the lack of some locale files, did you try to copy them from a standad Linux installation (on a PC)?

I don't remember the details. I have set charset="us-ascii" for mutt, so now I don't have the annoying three-digit octal codes for Umlauts anymore, but much more convenient quotation marks (one per Umlaut).

That is weird, as I get the escaped octals even with charset=us-ascii. Which environment variables are set for your mutt sessions?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

For the complete setup, please see [a href=\"http://www.daniel-hertrich.de/zaurus/zps]http://www.daniel-hertrich.de/zaurus/zps[/url]
The page layout is still a bit unfinished, but the information is there, see chapter "Email".

daniel

[jochen-02]

For the complete setup, please see http://www.daniel-hertrich.de/zaurus/zps
The page layout is still a bit unfinished, but the information is there, see chapter "Email".

Thank you. Now I am sure that I configured mutt to show question marks rather than escaped octals (?). But "my" version of mutt still shows these \xxx.
I have mutt 1.5.8  from mutt_1.5.8-1_arm.ipk.
Did you comile it yourself? May I try "your" version? Please let me know if you are willing to share "your" mutt. I'll then let you know my email address.
Thanks.

[bam]

any way of posting links to your ipk versions? or tar(s)? I would be interested in getting a nice offline setup running.

[daniel3000]

any way of posting links to your ipk versions? or tar(s)? I would be interested in getting a nice offline setup running.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=122606\"][{POST_SNAPBACK}][/a][/div]

Sorry, no IPK yet.
I have prepared it but never got around to finish the IPK, because I have so many things to take out of it from my setup.
Now my main C3000 was stolen, so I have to use the second one for daily life.
Actually I intended to use that second one to test such IPKs... :-(

Maybe I'll work on it during my vacations next week.

If I finish an IPK, I'll announce it on the forums of course.

daniel