My generic autoresponder recipe that I simply clone over and over again for new
uses works fine (see below but with 'me(_at_)myaddress' substituted).
After the autoreply is done, the email shows up in the AAAAinlogs.IN mailfolder
okay, but any attachments are missing which I need to keep! These will be
text files with either a <unique>.log filename.
===
:0 hc
* !^FROM_DAEMON
* !^X-Loop:me(_at_)myaddress\(_dot_)com
* ^TOme(_at_)myaddress\(_dot_)com
{
:0 fh
| formail -r -A"Precedence: junk" \
-I"From: MY NAME<me(_at_)myaddress\(_dot_)com>" \
-I"Subject: RE: MY SUBJECT" \
-A"X-Loop:me(_at_)myaddress\(_dot_)com" ; cat
$HOME/procmail/inlogs/autoreply.txt
:0
| $SENDMAIL -oi -t
}
:0 c:
* ^TOme(_at_)myaddress\(_dot_)com
| formail -rtzxTo: >> $HOME/procmail/inlogs/emailsenders.log
:0 a:
AAAAinlogs.IN
===
A 'Wish List' item would be to also copy/save any <uniquename>.log files in a
separate folder for subsequent downloading. In these cases, the
<uniquename>.log filename would be the only entry in the incoming Subject line.
I searched back almost 2 years in posts, and found the following snippet, but
not sure exactly how to integrate it so that everything works as needed
witthout disrupting the autoreply venue. There would be no 'processing' script
involved on the Unix, however.
===
:0 i
* ^To:(_dot_)*address(_at_)somedomaine(_dot_)tld
* ^Content-Type:.*multipart/mixed
* B ?? filename=.*\.dat
|/path/to/your/script
===
Thanks very much for any help.
Regards,
Eric
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail