Forwarder keeps a copy on the server. Then it's NOT a forwarder.
Already Exists
EMAIL FORWARDER: cpanel calls it email forward, but it leaves a copy on the server. this is duplicating all my emails in outlook and the iPhone. The way you guys have it setup, others call it " send a copy to: " - forward is to pass on the email. not keep a copy. please fix this, it's very unuseful the way it is now. When you move, you ask the US mail to forward your mail to the new address. do they leave a copy of all letters in your old house?
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Hey all! Since this request has been fulfilled I'm going to go ahead and lock comments for now. If you want to continue this conversation the best place to do so would be on the forums: forums.cpanel.net If one of you does start a thread and would like me to add it to the comments, just let me know!
Hey all! Since this request has been fulfilled I'm going to go ahead and lock comments for now. If you want to continue this conversation the best place to do so would be on the forums: forums.cpanel.net If one of you does start a thread and would like me to add it to the comments, just let me know!
If you wish to forward mail to another account without receiving mail at your cPanel account, create a forwarder from an address that does not have a corresponding account in cPanel. Alternatively, if the account already exists, you can delete it in cPanel. Afterward, all mail will be forwarded to the destination you have configured using the Forwarders feature.
This information can be found in our documentation for the Forwarders function here.
If you wish to forward mail to another account without receiving mail at your cPanel account, create a forwarder from an address that does not have a corresponding account in cPanel. Alternatively, if the account already exists, you can delete it in cPanel. Afterward, all mail will be forwarded to the destination you have configured using the Forwarders feature.
This information can be found in our documentation for the Forwarders function here.
For example, I have a cPanel email which forwards to my Gmail account and need to be able to reply as that address without the "Delivered on behalf of" message appearing. This is only achievable by having an cPanel mail account to provide a valid SMTP login but requires manual emptying of the inbox associated with that account.
A simple tickbox when creating a forwarder to "forward" or "store and forward" solve this problem.
For example, I have a cPanel email which forwards to my Gmail account and need to be able to reply as that address without the "Delivered on behalf of" message appearing. This is only achievable by having an cPanel mail account to provide a valid SMTP login but requires manual emptying of the inbox associated with that account.
A simple tickbox when creating a forwarder to "forward" or "store and forward" solve this problem.
The capability is clearly needed to forward without storing--this exists, albeit in a somewhat confusing way owing to the CPanel implementation of email forwarding and email accounts being parallel paths for mail delivery that can both be active simultaneously.
The capability to do this while still retaining an account that can be validated is also useful (although sending email under a different email address via gmail I think is the only tangible reason for that that I've come across, same as the poster), but one that comes up a lot, owing to the popularity and ubiquity of gmail, and it being the path-of-least-resistance default for Android phones, and so forth. This is what doesn't exist in CPanel.
It could be implemented in CPanel in one of three ways:
1. The easier way, given the current architecture of email accounts and forwarders being parallel delivery paths (if they both exist, i.e., if the same email address resolves to both), is to add a checkbox under the email account "Delete all incoming email to this account (not recommended)." Then the account still exists for SMTP authentication purposes, and the parallel forwarded takes care of the actual delivery. It could be a little confusing in that the user would need to under that there are parallel paths so that the email is NOT actually being deleted notwithstanding his checking the box, since the forwarder is active and "takes over," but it would work, and could be appropriately documented, even in the CPanel screen itself if necessary.
2. The cleaner way, conceptually, but would be an architectural change in CPanel and more development, would be to disallow forwarders and accounts from being able to have the same email address. I.e., if you had a forwarder with a certain name, you would not be allowed to create an email account with the same name in that domain. All the forwarding features under the Mail Forwarder option would have to be duplicate-implemented under email accounts (which would be the main reason not to do it this way).
3. A third way, actually used in other control panels that I've run into, is similar to Option 2, but eliminate the forwarders completely as a separate category. I.e., you are forced to create an account for every address you want, even if your intention is only to use it is a forwarder.
I'd favour Option 1 as being the cleanest given the current architecture and sounds rather simple to implement and test. I can't imagine it would change more than 50 lines of backend code and perhaps not much more in the web interface (but what do I know? :-)).
The capability is clearly needed to forward without storing--this exists, albeit in a somewhat confusing way owing to the CPanel implementation of email forwarding and email accounts being parallel paths for mail delivery that can both be active simultaneously.
The capability to do this while still retaining an account that can be validated is also useful (although sending email under a different email address via gmail I think is the only tangible reason for that that I've come across, same as the poster), but one that comes up a lot, owing to the popularity and ubiquity of gmail, and it being the path-of-least-resistance default for Android phones, and so forth. This is what doesn't exist in CPanel.
It could be implemented in CPanel in one of three ways:
1. The easier way, given the current architecture of email accounts and forwarders being parallel delivery paths (if they both exist, i.e., if the same email address resolves to both), is to add a checkbox under the email account "Delete all incoming email to this account (not recommended)." Then the account still exists for SMTP authentication purposes, and the parallel forwarded takes care of the actual delivery. It could be a little confusing in that the user would need to under that there are parallel paths so that the email is NOT actually being deleted notwithstanding his checking the box, since the forwarder is active and "takes over," but it would work, and could be appropriately documented, even in the CPanel screen itself if necessary.
2. The cleaner way, conceptually, but would be an architectural change in CPanel and more development, would be to disallow forwarders and accounts from being able to have the same email address. I.e., if you had a forwarder with a certain name, you would not be allowed to create an email account with the same name in that domain. All the forwarding features under the Mail Forwarder option would have to be duplicate-implemented under email accounts (which would be the main reason not to do it this way).
3. A third way, actually used in other control panels that I've run into, is similar to Option 2, but eliminate the forwarders completely as a separate category. I.e., you are forced to create an account for every address you want, even if your intention is only to use it is a forwarder.
I'd favour Option 1 as being the cleanest given the current architecture and sounds rather simple to implement and test. I can't imagine it would change more than 50 lines of backend code and perhaps not much more in the web interface (but what do I know? :-)).
This option already exists by using mail rules - you can set it to forward & then delete the original email. I'm using this on archive mailboxes I don't want to delete but where all new email is redirected.
This option already exists by using mail rules - you can set it to forward & then delete the original email. I'm using this on archive mailboxes I don't want to delete but where all new email is redirected.
A forwarder dosn't keep a copy on the server on it's own. It just doesn't stop the mailbox from working.
If you wanted to stop the mailbox from recieving the e-mail then this feature should be to allow to keep a maibox but delete any new e-mail it would have recieved.
What we do in this case is create a new mailbox, copy email to the new email box and delete the old one. What about allowing users to rename a mailbox, whould this solve the issue ?
A forwarder dosn't keep a copy on the server on it's own. It just doesn't stop the mailbox from working.
If you wanted to stop the mailbox from recieving the e-mail then this feature should be to allow to keep a maibox but delete any new e-mail it would have recieved.
What we do in this case is create a new mailbox, copy email to the new email box and delete the old one. What about allowing users to rename a mailbox, whould this solve the issue ?
Guys, just to be clear Edith is correct, you can already achieve all that you ask for using Filter Rules:
Mail -> Account Level Filtering
or
Mail -> User Level Filtering
Guys, just to be clear Edith is correct, you can already achieve all that you ask for using Filter Rules:
Mail -> Account Level Filtering
or
Mail -> User Level Filtering
You're correct Paul but it's important to note a few things...
* If you leave the mail forwarder in place and set up a mail filter to simply discard all received mails for a particular account, it does not forward any emails. The 'forwarder' setup is entirely ignored.
* So you need in fact to set up two filters. One to match all and send them on to your desired destination email address and one to discard them afterwards.
* The order of the filters is paramount. Put the one to catch all and 'redirect' (as it puts it) at the top. And the one to then discard at the bottom.
* A '*' does not match all. I used a word in the email address I was adding the filter for in order to execute a successful match all match.
* This works whether or not you leave the forwarder in place.
You're correct Paul but it's important to note a few things...
* If you leave the mail forwarder in place and set up a mail filter to simply discard all received mails for a particular account, it does not forward any emails. The 'forwarder' setup is entirely ignored.
* So you need in fact to set up two filters. One to match all and send them on to your desired destination email address and one to discard them afterwards.
* The order of the filters is paramount. Put the one to catch all and 'redirect' (as it puts it) at the top. And the one to then discard at the bottom.
* A '*' does not match all. I used a word in the email address I was adding the filter for in order to execute a successful match all match.
* This works whether or not you leave the forwarder in place.
Hey all! Since this request has been fulfilled I'm going to go ahead and lock comments for now. If you want to continue this conversation the best place to do so would be on the forums: forums.cpanel.net If one of you does start a thread and would like me to add it to the comments, just let me know!
Hey all! Since this request has been fulfilled I'm going to go ahead and lock comments for now. If you want to continue this conversation the best place to do so would be on the forums: forums.cpanel.net If one of you does start a thread and would like me to add it to the comments, just let me know!
Replies have been locked on this page!