aboutsummaryrefslogtreecommitdiffstats
path: root/contrib/fetchspool
blob: cd6c2c81ea6c6c3d563584b98b45116575caeb31 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
#!/bin/sh -
#
# Quick hack for fetchmail to locally spool messages.
#
# To spool:
#     fetchmail --mda "fetchspool -t %T %F"
# To de-spool
#     fetchspool -f
#
# Robert de Bath  <robert@mayday.cix.co.uk>
# updated by william boughton <bill@xencat.demon.co.uk>
# 4th/10/1998 and tested
#
# William Boughton comments:
# Still has some potential problems, with using inline from address.
# The use of _ is bad because fetchmails uses this if it notices
# shell escapes.
# 10th/11/1998
# Changed to using 3 _@@s to delimit the message, i hope this is ok.
# Whilst i have tested and used this script, with my demon account and
# SDPS, it may still have serious problems, that i've not noticed etc.

MAILSPOOL=/tmp/spool

if [ "$1" != "-f" ]
then
   if [ "$1" = "-t" ]
   then 
	ADDR="$2"
	FROM="$3"
   else 
	ADDR="$1"
	FROM="$2"
   fi

   cat - > $MAILSPOOL/tmp.$$ 				   || exit 1
   mv $MAILSPOOL/tmp.$$ "$MAILSPOOL/msg.`date +%j%H%M%S`$$.to.${ADDR}_@@${FROM}"  || exit 1

   exit 0
else
   for i in $MAILSPOOL/msg.*.to.*
   do
      [ -f "$i" ] || continue
     # TO="`echo \"$i\" | sed 's/^msg.[^.]*.to.//'`"
	TO=$(basename $i | sed -e 's/^msg.[^.]*.to.//' -e 's/_@@.*$//')
	FROM=$(basename $i | sed 's/^msg.[^.]*.to.*_@@//')
# need the \<\> so for bounces to have a proper from addr
echo the to was \<$TO\>  and the from \<$FROM\>
      /usr/lib/sendmail -f \<${FROM}\> -oem "$TO" < "$i" ||
      {
         echo "Sendmail failed on `basename \"$i\"`"
	 continue
      }
      rm -f "$i"
   done
   exit 0
fi
nt">i> header in one huge piece as POP3 does which makes undeliverable </I>&gt;<i> mail more expensive though. </I> Thankfully, I won't have to wait for this. Much of Domino's IMAP behavior depends on the mail storage format specified in the Person document in the Public Name and Address Book. There are three options for mail storage for incoming mail: 1. Keep in Sender's format 2. Prefers MIME 3. Prefers Notes Rich Text My setting was &quot;Prefers MIME&quot;. Switching to &quot;Keep in Sender's format&quot; solved the missing encoding header problem. According to IBM, &quot;Prefers MIME&quot; offers the best IMAP performance in Domino &quot;When you choose this option, the router converts all incoming messages to the MIME storage format at delivery time. The messages are therefore stored in your mail file in MIME format. This lets the IMAP server quickly serve all information about the document (such as size) as well as the body of the document to an IMAP client because the document is already stored in the necessary MIME format for the client to read.&quot; [0] I can only surmise this MIME storage results in some rather non-standard IMAP behavior. So long my goofy procmail hacks. Thanks to Matthias Andress and Rob Funk for helping me troubleshoot. Anthony [0] <A HREF="http://www-128.ibm.com/developerworks/lotus/library/ls-D6_IMAP_Perf/?OpenDocument">http://www-128.ibm.com/developerworks/lotus/library/ls-D6_IMAP_Perf/?OpenDocument</A> </PRE> <!--endarticle--> <HR> <P><UL> <!--threads--> <LI> Next message: <A HREF="010016.html">[fetchmail]Domino IMAP and missing Content-Transfer-Encoding </A></li> <LI> <B>Messages sorted by:</B> <a href="date.html#10015">[ date ]</a> <a href="thread.html#10015">[ thread ]</a> <a href="subject.html#10015">[ subject ]</a> <a href="author.html#10015">[ author ]</a> </LI> </UL> </body></html>