The way email subscriptions work is by setting up a catch-all email address in your hosting panel, and then placing a special ‚.forward‘ file in the directory of the email you created under in your web space.
However for this to work, your hosting provider must have the feature which allows incoming emails to be piped through to a script or program.
If you are not sure whether your host provides this or not (most do) ask your system administrator of host provider. This is required for the autoresponder to accept subscriptions by email.
Login to your host control panel, and go to your mail settings area. Create a new email account and set it to be your „catch-all“ email address.
Using your ftp client, login to your webspace and take note of where the server placed the directory for the email account you just created. Every email account you create gets a corrosponding directory in the same name created in your webspace.
Then open notepad, or your favorite text editor and create a new file. Enter the code provided by the system in the admin area for sendmail or Exim/Qmail, depending on which system your server uses. Most of the time the code is the one provided for sendmail – unless you know otherwise. Save the file as “forward.txt” and upload it to the email directory you made note of in step 2 above. Using your ftp client, right-click on the forward.txt file you‘ve uploaded, and choose „rename“ from the menu options.
Rename the file from “forward.txt” to “.forward” – removing the “.txt” ending and adding the period at the beginning of the name.
That‘s it, now all incoming emails, to whatwever usernames that don‘t exist on your server (but created and used by 1MC) will be caught by the catch-all email account, which has the forwarding file in there to pass it to 1MC to handle.
If you get a message saying something about overwriting an existing .forward file, click “NO”. This will usually be the case if you set you master account as the catch-all email address and try placing the .forward file in your public directory – it means that you already have a .forward file in your public directory used by the server, which you do NOT want to overwrite.
If you are using cpanel, you can create an email forwarder and in the forwarding field you enter the path to the email parser script, which is the file EC uses to handle incoming email.
For example, if the autoresponder name is firstname.lastname@example.org, in cpanel you would create a forwarder called email@example.com and in the the forwading field, enter:
This will work on most cpanels and it should work on other platforms. You would only need to create the forwarder and not a real email account.
The one thing with this approach is you would have to create a forwarder for each autoresponder. Hence the catch-all idea of having one account monitor all incoming email and routing it automatically.
The one other known way, which is sometimes used with exim and qmail is by using an alias, however you have to have root access (access to your /etc folder) where you can set the parameters in the .qmail file or change your exim config settings.