hello, how do i save outgoing messages? i tried playing with the configuration files with no luck. preferably, i'd like to save a copy of each sent mail in seperate files -- Nehal ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
Nehal <nehalmistry@...> wrote: > how do i save outgoing messages? i tried playing with > the configuration files with no luck. A simple search for "outgoing" in the manual page shows all three possible methods. > preferably, i'd like to save a copy of each sent mail > in seperate files If you want to save all mails to more than one file, use the "autobcc" mechanism with the filenames as recipients. The "Mail" command saves outgoing messages to files named after their first recipient. It is not practical for batch mailing, though; in that case, use the "-b" option with a filename argument. If you use the maildir format for your record folder, each mail is put into a single file anyway. Otherwise, if your record folder is in mbox format, a few lines of awk or Perl suffice to copy each messages to a different file. Gunnar ------------------------------------------------------- This SF.Net email is sponsored by:(Continue reading)
Hi, As per the subject line, nail 11.13 10/27/04 OpenBSD 3.3 i386 builds fine using defaults. Regards, S. -- -- -------------------------------------------------------------------------- Simon B. http://kaizo.org/simonb (finger simonb@... | gpg --import) mail simonb@... -------------------------------------------------------------------------- ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
Simon B <simonb@...> wrote: > As per the subject line, > > nail 11.13 10/27/04 OpenBSD 3.3 i386 > > builds fine using defaults. Fine. Thank you. I'll add it to the README. > X-include: <stupid/disclaimer.h> > X-Copyright: (C)2004 Forwarding *not* allowed without prior permision > X-Notice: You may *NOT* store this email on a public system. That's a bit problematic since you're posting to a public list whose traffic is stored in a public archive . . . . Gunnar ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
On Tue, 2 Nov 2004, Gunnar Ritter wrote: GR! > X-include: <stupid/disclaimer.h> GR! > X-Copyright: (C)2004 Forwarding *not* allowed without prior permision GR! > X-Notice: You may *NOT* store this email on a public system. GR! GR! That's a bit problematic since you're posting to a public list GR! whose traffic is stored in a public archive . . . . Yes, I hereby dispense the copyright for that email and this one. Oddly enough, in the 3 or so years I have had that X-Header, you are the first person to comment on it. It is mainly to give me some "legal" power should an email I send turn up somewhere I do not approve of. Thanks, S. -- -- -------------------------------------------------------------------------- Simon B. http://kaizo.org/simonb (finger simonb@... | gpg --import) mail simonb@... -------------------------------------------------------------------------- ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE(Continue reading)
Running nail 11.13 on a linux redhat 9 system, making an imap connection
to a server.
With a very large mail folder (~5000 messages), a typo in a header
command, e.g.,
h typo
which normally provokes an error message:
No applicable messages from {typo}
causes nail to freeze until it is killed with kill -9.
Nail also freezes if I delete a large number of messages, e.g.,
d 1-5000
and then try to quit with q. If I kill nail and restart, no messages
have been removed from the server.
Deleting a smaller number of messages, say 1500, and quitting with q
works. Nail doesn't freeze and the messages are gone from the server.
Stephen Isard
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
"Stephen Isard" <3s9xh9m02@...> wrote: > Running nail 11.13 on a linux redhat 9 system, making an imap connection > to a server. > > With a very large mail folder (~5000 messages), a typo in a header > command, e.g., > h typo > which normally provokes an error message: > No applicable messages from {typo} > causes nail to freeze until it is killed with kill -9. The problem here is that most forms of "h typo" are correct commands for nail. So it just does what it was instructed to do; it searches for messages sent by "typo". Now since searches of this form are case-sensitive but IMAP searches are not, nail has to download all the data it needs and to check for matches on the client machine. This can take a lot of time before nail can finally print "No applicable messages from {typo}". I'm sorry to say, but the only way to avoid the problem completely is not to make typos in message specifications when reading large IMAP folders. Actually there is a design decision involved at this point. When it needs the contents of any header field of an IMAP message, nail will currently request the entire message header from the server. This is actually a speed advantage in many situations. First, performance in networking does not only depend on the amount of data transmitted, but also on the number of transmission requests. Thus it can well be that it is faster to download an entire message header than to fetch two or three individual header fields in separate operations. Second,(Continue reading)
(Resend of earlier message because the first try doesn't seem to have
reached the list - apologies if you eventually get it twice)
Thanks for your extremely quick, helpful and informative response.
> nail has to download all
> the data it needs and to check for matches on the client machine. This
> can take a lot of time before nail can finally print "No applicable
> messages from {typo}". I'm sorry to say, but the only way to avoid
> the problem completely is not to make typos in message specifications
> when reading large IMAP folders.
Or not to have ridiculously large folders 
If it is downloading the
headers that is the problem, would using a cache help? You seem to suggest
that below.
> Second,
> the performance of nail is optimized with regard to the IMAP cache.
> If caching is enabled, the header of a message needs to be downloaded
> only once for the entire lifetime of the message on the server.
...
> There is room for improvement in the IMAP message deletion code too. Nail
> currently generates one STORE request for each deleted message. But it
> would be much faster to use message ranges for the STORE command too, as
> it is done when fetching message headers. I'll consider to implement that
> in the future, but it has a low priority for me since I never waited very
> long at this point. Was the time for deleting 1500 message acceptable to
> you?
(Continue reading)
"Stephen Isard" <3s9xh9m02@...> wrote: > > nail has to download all > > the data it needs and to check for matches on the client machine. This > > can take a lot of time before nail can finally print "No applicable > > messages from {typo}". I'm sorry to say, but the only way to avoid > > the problem completely is not to make typos in message specifications > > when reading large IMAP folders. > Or not to have ridiculously large folders(Continue reading)
Hi, nail 11.14 has been released and is available from <http://nail.sourceforge.net> as usual. Changes are: [11.14] released 11/4/04 * A 'Z' command was introduced. It is similar to the 'z' command, but scrolls only to header groups that contain at least one new or flagged message. This is useful for reading large mailing lists. * The attachment decoding functions have been rewritten. As a result, nail is now able to decrypt and display encrypted parts of multipart messages. * For MIME messages of type 'multipart/alternative', only the text/plain part is displayed now if one is present with the 'print'-like commands. The 'print-alternatives' variable can be set to print all parts, as it was done previously. The 'Print'-like commands always print all parts. * The ~F and ~M escapes now cause all parts of MIME multipart messages to be included in the message being composed. * A 'show' command was introduced to make the raw MIME-encoded message text visible. * Modifications to messages made using the 'edit' and 'visual' commands do no longer cause changes to the current folder. This is the behavior demanded by POSIX.1-2004. MIME decoding and decryption are now performed before each message is passed to the editor. If you prefer the old behavior, set the new 'writebackedited' variable. * When large amounts of messages were deleted on an IMAP server (or many other STORE commands were generated e.g. because many messages were marked as read), nail sent all of these commands asynchronously. This did slow down operation with some servers and eventually lead to a deadlock after some thousand commands were sent. Nail now waits for server responses in defined intervals. (Bugreport by Stephen Isard.)(Continue reading)
RSS Feed5 | |
|---|---|
7 | |
28 | |
9 | |
3 | |
10 | |
5 | |
19 | |
2 | |
1 | |
4 | |
23 | |
1 | |
7 | |
5 | |
6 | |
2 | |
2 | |
1 | |
1 | |
3 | |
10 | |
9 | |
13 | |
8 | |
6 | |
4 | |
2 | |
11 | |
16 | |
4 | |
9 | |
1 | |
2 | |
5 | |
16 | |
7 | |
8 | |
4 | |
16 | |
13 | |
7 | |
9 | |
4 | |
14 | |
15 | |
9 | |
13 | |
16 | |
2 | |
6 | |
2 | |
20 | |
20 | |
4 | |
12 | |
7 | |
4 | |
15 | |
5 | |
18 | |
7 | |
6 | |
11 | |
12 | |
1 | |
4 | |
12 | |
21 | |
9 | |
14 | |
31 | |
16 | |
6 | |
7 | |
19 | |
7 | |
26 | |
33 | |
47 | |
23 | |
4 | |
1 |
