8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear,
I want to migrate mailbox from ISP Config (postfix) to zimbra. and have tried import maildir to zimbra with script :
#!/bin/bash
#
# Maildir to Zimbra import
# Drop in your user root and run as superuser.
#
ZMM="/opt/zimbra/bin/zmmailbox"
domain="psmti.org" # change to... (0 Replies)
Discussion started by: arsyam
0 Replies
2. AIX
Hi,
Can anyone please explain a little about df command. I have following question:
Following example is showing % used as 4 where as total free blocks are 15.46 out of 16.00 MB blocks.
df -m /test
Filesystem MBblocks Free %Used Iused %Iused ... (5 Replies)
Discussion started by: itsabhi9
5 Replies
3. Shell Programming and Scripting
I'm setting up a cronjob that will hopefully dump the contents of a email delivered to Maildir/new/ to /home/user/raw.txt (and then delete that email)
I could manually remove the bottom line of the raw email, then place the contents in the next line up in the /home/user/raw.txt, but it seems to... (5 Replies)
Discussion started by: unclecameron
5 Replies
4. Red Hat
Friends,
I am new to the postfix mail servers. My setup was configured with the below
Mail Server(MTA,MRA) Postfix, Courier-IMAP
Operating System Redhat Enterprise Linux 5.4 .
SPAM Protection/Content Filter IMSS 7.1
DNS,LDAP BIND,OPENLDAP
WebMail ... (0 Replies)
Discussion started by: kmvinay
0 Replies
5. Shell Programming and Scripting
Hello. I have a variable $num that has values 1-9.
I want to put in a statement saying
if $num != seq 1 9
then
echo "Invalid entry. Use numbers 1-9. "
Do I put it before, in, or after my "while" code?
while (( $var <= $num ))
do
f=(( $f * $var ))
let var++
done
Also i wrote... (3 Replies)
Discussion started by: Ccccc
3 Replies
6. UNIX for Dummies Questions & Answers
Hi buddies,
Anybody has any script to delete mails from Maildir/cur???
I mean is it possible to delete mails from Maildir/cur matching a particular subject like spam or fax???
Thanks in advance (1 Reply)
Discussion started by: squid04
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I was wondering if someone can tell me what the difference is exactly between maildir and mbox.
We have a few solaris 9 systems here and would like to get an imap server running on them. I have setup fetchmail so that it retrives remote pop3 mail into an account, and that mail is then... (3 Replies)
Discussion started by: sugarat
3 Replies
8. Programming
Hi a am writing a C Programe on Vi Editor (File Handelling),and i am compiling it using fcc but it not compiling ,Even Vi not saving my file.Tell me how can i do that.One More Thing I want to know that ,Is their any subsitute of conio.h. (3 Replies)
Discussion started by: at_renai2001
3 Replies
LEARN ABOUT DEBIAN
mailexec
mailexec(1) Mail Avenger 0.8.3 mailexec(1)
NAME
mailexec - run program on messages in mbox file or maildir
SYNOPSIS
mailexec [-nvFR] mailbox program [arg ...]
DESCRIPTION
mailexec runs a program over every message in mailbox, which must be an mbox-format mail file or maildir directory. For each message
encountered, mailexec executes program with the specified arguments, supplying the message as standard input. mailexec synthesizes a
"From " line and a "Return-Path:" header field for each message if the message does not already contain one. (This behavior can be
modified by the -F and -R flags, described below.)
When parsing mbox format files, mailexec unescapes "From " lines. If a line begins with one or more ">" characters followed by "From ",
mailexec deletes one of the ">" characters. If you do not want this unescaping behavior, see the formail(1) utility, which has a -s flag
that performs a similar function to mailexec.
OPTIONS
-n When processing a maildir, causes mailexec to look exclusively at "new" messages that have not yet been moved to the cur directory.
-v Turns on verbose mode. If mailbox is a maildir, mailexec prints out the name of each file it processes inside the maildir. If mailbox
is an mbox format file, mailexec prints the message-id of each message it processes (as long as messages have a message-id header).
-F Suppresses printing of the initial "From " line at the beginning of each message.
-R Suppresses printing of initial "Return-Path:" lines.
EXAMPLES
To get the same behavior as the Unix from(1) command on a mail directory dir, you can run either of the following two commands:
mailexec -n dir head -1
mailexec -n dir sed -ne 1p
To convert an mbox-format file mbox into a maildir directory dir, you can run:
mailexec mbox deliver dir/
Conversely, to convert maildir dir into an mbox-format file mbox, run:
mailexec dir deliver mbox
To train the spamassassin filter on a mail folder called spam containing unwanted messages, run:
mailexec spam sa-learn --spam
Note that this works whether spam is an mbox format file or a maildir directory.
If you have an old mbox file or maildir directory box and wish to "import" the old mail into your web mail account, say example@gmail.com,
you can run:
mailexec -F box sendmail example@gmail.com
Note again that this works whether box is an mbox format file or a maildir directory.
SEE ALSO
avenger(1), deliver(1), dotlock(1), avenger.local(8)
The Mail Avenger home page: <http://www.mailavenger.org/>.
BUGS
When reading from a maildir and synthesizing a "From " line, mailexec guesses the delivery date of the message based on the name of the
file, which works in practice but could be considered dangerous since file names in maildirs are supposed to be opaque. Thus, while
generally mailexec places sensible dates in "From " lines and processes maildir messages in order of delivery, it might be unwise to rely
on this behavior.
mailexec generates the time for the "From " line in the local time zone, as is customary on Unix. This could lead to loss of information
when transferring mailboxes across time zones or combining mailboxes created in different timezones. Moreover, this practice is
incompatible with qmail, which uses GMT in the "From " line.
mailexec expects that if there is a "Return-Path:" header field, it will be the first header field in the message (possibly after the
initial "From " line, which is not itself a header field).
There are many different variants of the mbox message format. mailexec expects the "mboxrd" variant, in which each message is delimited by
a "From " line at the beginning and a blank line at the end, and every line beginning with either "From " or one or more ">" characters
followed by "From " is escaped by adding another ">" character. In particular, this means mailexec will incorrectly parse System V
"mboxcl2" files, which use "Content-Length:" header fields to determine message boundaries rather than "From " lines.
mailexec attempts to lock mbox format files, but will execute anyway even if it cannot obtain the lock. This allows it to work on read-
only files, but if you are highly unlucky could result in the last message being truncated.
There is no locking for maildir files. If a maildir is modified while mailexec is running over it, mailexec could miss messages. If you
are concurrently manipulating the maildir with a mail reader, maildir could even miss old messages that just happen to have been moved from
the new to the cur directory. mailexec will issue a warning if it fails to open a file that it had previously seen when scanning the
directory.
AUTHOR
David Mazieres
Mail Avenger 0.8.3 2012-04-05 mailexec(1)