Email forwarding for autoresponder list.

4 posts / 0 new
Last post
#1 Fri, 09/21/2007 - 07:44

Email forwarding for autoresponder list.

I need to forward email to my autoresponder list I am testing. Is there a way to create a catch all email address?

Or preferably using one of the following mehtods, that I can't get to work. I made a .forward and a .procmailrc file and put ithem in the directory above public_html. Any ideas on this?


Mike Murphy

Just make sure the path is correct:

\username, "|/usr/bin/perl /home/username/public_html/cgi-bin/parabots/uamemailcap.cgi"

(all this should be on a single line)

Upload this file in ascii mode to the root directory on your hosting account. Try subscribing to one of your newsletters by email and see if you get a message back (you should have created the newsletter in question and entered at least one outgoing message to see any result).

If your server uses QMail instead of exim, then you will have to upload the .procmailrc file instead of the .forward. Below is the syntax to use for the .procmailrc file:

:0c |/usr/bin/perl /home/username/public_html/cgi-bin/parabots/uamemailcap.cgi

Sat, 09/22/2007 - 04:35

Doesn't anybody know how to do email piping in Debian 4 or create a catch all email address in virtualmin?

Sat, 09/22/2007 - 05:40 (Reply to #2)

OK, I found in an email that I can feed it to a program, so I created the autoresponder email address and forwarded it to the cgi file as follows:
/usr/bin/perl /home/confirming-email/cgi-bin/ar/uamemailcap.cgi

it returns the email with the following error:

<> (expanded from
<>): Command died with status 13: "/usr/bin/perl
/home/confirming-email/cgi-bin/ar/uamemailcap.cgi". Command output: Can't
open perl script "/home/confirming-email/cgi-bin/ar/uamemailcap.cgi":
Permission denied

So am I on the right track here? How can I give permission for the forwarder to execute the cgi file?


Sun, 09/23/2007 - 23:05 (Reply to #3)
Joe's picture

procmail becomes the user receiving the mail, so the script must be executable by the user. It may also need write privileges somewhere.

It's also worth checking to be sure the shebang (#!/usr/bin/perl, or whatever) actually points to the perl on your system.


Check out the forum guidelines!

Topic locked