http://ideas.mailtrust.com Webmail.us Idea Central Wed, 27 Aug 2008 17:58:26 -0400 http://mnm.uib.es/gallir/meneame/ en http://ideas.mailtrust.com/story.php?id=2530 http://ideas.mailtrust.com/story.php?id=2530 Wed, 27 Aug 2008 17:58:26 -0400 brains Webmail http://ideas.mailtrust.com/story.php?id=2530
I know personally this would increase our dependability to Mailtrust because it would make our jobs that much easier. Sharing informatin effectively is important and increases sales - it's a no brainer.]]> http://ideas.mailtrust.com/story.php?id=1989 http://ideas.mailtrust.com/story.php?id=1989 Tue, 12 Aug 2008 17:20:02 -0400 knowledgelinkllc Webmail http://ideas.mailtrust.com/story.php?id=1989 http://ideas.mailtrust.com/story.php?id=1645 http://ideas.mailtrust.com/story.php?id=1645 Fri, 01 Aug 2008 17:36:11 -0400 atelford Sync http://ideas.mailtrust.com/story.php?id=1645
I propose adding that functionality so that under the Account settings on the plugin you can associate one sync account information per email profile setup in Outlook.]]> http://ideas.mailtrust.com/story.php?id=1661 http://ideas.mailtrust.com/story.php?id=1661 Thu, 31 Jul 2008 14:21:52 -0400 sharrett Group Lists http://ideas.mailtrust.com/story.php?id=1661 http://ideas.mailtrust.com/story.php?id=1591 http://ideas.mailtrust.com/story.php?id=1591 Thu, 24 Jul 2008 13:10:38 -0400 rhoneycu2 Calendar http://ideas.mailtrust.com/story.php?id=1591 We would propose that a configuration setting be created such that a user would have any appointment that he accepts automatically added to his calendar (without the need for another dialog box).]]> http://ideas.mailtrust.com/story.php?id=1585 http://ideas.mailtrust.com/story.php?id=1585 Tue, 22 Jul 2008 08:53:47 -0400 engkaram Website http://ideas.mailtrust.com/story.php?id=1585 http://ideas.mailtrust.com/story.php?id=1584 http://ideas.mailtrust.com/story.php?id=1584 Tue, 22 Jul 2008 08:45:23 -0400 engkaram Sync http://ideas.mailtrust.com/story.php?id=1584 http://ideas.mailtrust.com/story.php?id=1560 http://ideas.mailtrust.com/story.php?id=1560 Fri, 18 Jul 2008 04:16:42 -0400 kevin.donohue Control Panel http://ideas.mailtrust.com/story.php?id=1560
Considering we pay for each mailbox by size, I think a tool for finding the space hogs or presenting a report to the accounting department a measurable need to increase the budget for bigger mailboxes would be useful.]]> http://ideas.mailtrust.com/story.php?id=1570 http://ideas.mailtrust.com/story.php?id=1570 Thu, 17 Jul 2008 12:09:05 -0400 kylejhunt Control Panel http://ideas.mailtrust.com/story.php?id=1570 http://ideas.mailtrust.com/story.php?id=1565 http://ideas.mailtrust.com/story.php?id=1565 Thu, 17 Jul 2008 11:11:58 -0400 cls Webmail http://ideas.mailtrust.com/story.php?id=1565 http://ideas.mailtrust.com/story.php?id=1569 http://ideas.mailtrust.com/story.php?id=1569 Thu, 17 Jul 2008 10:34:04 -0400 w1dancer Control Panel http://ideas.mailtrust.com/story.php?id=1569 http://ideas.mailtrust.com/story.php?id=1558 http://ideas.mailtrust.com/story.php?id=1558 Tue, 08 Jul 2008 11:54:09 -0400 mike.strock Webmail http://ideas.mailtrust.com/story.php?id=1558
If an attachment was sent to my email (particularly a ZIP file), the originating user would get a delivery error because GMail doesn't allow ZIP attachments, apparently.

So I was hoping that I could forward ONLY email that didn't have an attachment. That way, I'd still be able to read/get most of my email....]]> http://ideas.mailtrust.com/story.php?id=1550 http://ideas.mailtrust.com/story.php?id=1550 Mon, 07 Jul 2008 08:44:26 -0400 trampanzee APIs http://ideas.mailtrust.com/story.php?id=1550 http://ideas.mailtrust.com/story.php?id=1543 http://ideas.mailtrust.com/story.php?id=1543 Tue, 01 Jul 2008 17:27:32 -0400 bristef Contacts http://ideas.mailtrust.com/story.php?id=1543
Thanks.

-Brian]]> http://ideas.mailtrust.com/story.php?id=1527 http://ideas.mailtrust.com/story.php?id=1527 Thu, 26 Jun 2008 07:40:05 -0400 thuro Webmail http://ideas.mailtrust.com/story.php?id=1527 I just spoke with a fellow admin on an interesting idea. He was concerned about users logging into webmail at an internet cafe and forgetting to log out of their session. I was unable to find it in the settings and I have never had mine timeout before. This ought to be an option that can be enabled!]]> http://ideas.mailtrust.com/story.php?id=1533 http://ideas.mailtrust.com/story.php?id=1533 Tue, 24 Jun 2008 14:54:29 -0400 cortech74 Calendar http://ideas.mailtrust.com/story.php?id=1533
Thanks]]> http://ideas.mailtrust.com/story.php?id=1532 http://ideas.mailtrust.com/story.php?id=1532 Tue, 24 Jun 2008 11:51:55 -0400 jason Webmail http://ideas.mailtrust.com/story.php?id=1532 http://ideas.mailtrust.com/story.php?id=1530 http://ideas.mailtrust.com/story.php?id=1530 Tue, 24 Jun 2008 11:44:03 -0400 ryan http://ideas.mailtrust.com/story.php?id=1530 http://ideas.mailtrust.com/story.php?id=1522 http://ideas.mailtrust.com/story.php?id=1522 Tue, 17 Jun 2008 10:42:48 -0400 cortech74 Calendar http://ideas.mailtrust.com/story.php?id=1522
Thanks!]]> http://ideas.mailtrust.com/story.php?id=1521 http://ideas.mailtrust.com/story.php?id=1521 Tue, 17 Jun 2008 10:42:36 -0400 cortech74 Webmail http://ideas.mailtrust.com/story.php?id=1521
Thanks!]]> http://ideas.mailtrust.com/story.php?id=1520 http://ideas.mailtrust.com/story.php?id=1520 Tue, 17 Jun 2008 10:39:34 -0400 jason Search http://ideas.mailtrust.com/story.php?id=1520 http://ideas.mailtrust.com/story.php?id=1516 http://ideas.mailtrust.com/story.php?id=1516 Fri, 13 Jun 2008 15:40:03 -0400 ryan http://ideas.mailtrust.com/story.php?id=1516 http://ideas.mailtrust.com/story.php?id=1507 http://ideas.mailtrust.com/story.php?id=1507 Tue, 10 Jun 2008 00:36:04 -0400 dongo APIs http://ideas.mailtrust.com/story.php?id=1507
Making this parameter optional would allow us to modify the user account information without changing the current status of the account. For instance, the account may have been set to 0(inactive) by MailTrust due to spamming, but the account is later modified through an API call and reset back to an active state by mistake. Currently, the only way to avoid this is to lookup the current status prior to modifying the account and then using that value in the ModifyUser() call. Seems like it should be simpler than that.]]> http://ideas.mailtrust.com/story.php?id=1501 http://ideas.mailtrust.com/story.php?id=1501 Tue, 10 Jun 2008 00:26:07 -0400 jackcollins Control Panel http://ideas.mailtrust.com/story.php?id=1501 http://ideas.mailtrust.com/story.php?id=1506 http://ideas.mailtrust.com/story.php?id=1506 Tue, 10 Jun 2008 00:22:30 -0400 dongo APIs http://ideas.mailtrust.com/story.php?id=1506
Here is why this is needed...

Customer-A is using mail services provided by Reseller-#1. Then, Customer-A decides to switch services over to Reseller-#2 ( for whatever reason ), not realizing that their domain is already hosted by MailTrust, where MailTrust is powering services for Reseller-#1 ( their current provider ). Reseller #2 cannot provision an account for this user because Customer-A's domain name is already being hosted by MailTrust, but the reseller will not find this out until they attempt to add the domain name into the system. So, there needs to be an API call to help head this off during the signup process for new customers.

I understand this is probably not a common problem, but it does happen, and when it does, it will cause some strange errors that could be hard to detect unless an API call was made available to head this off prior to this scenario taking place. Something like CheckDomainIsHosted() maybe?

Waiting until the domain is actually being added into the system using Subaccount_AddDomain() is usually too late. That would be after a client has already had an account setup with the Reseller. And then the Reseller would have the dilemma of trying to handle this situation.]]> http://ideas.mailtrust.com/story.php?id=1504 http://ideas.mailtrust.com/story.php?id=1504 Sat, 07 Jun 2008 11:52:20 -0400 dongo Control Panel http://ideas.mailtrust.com/story.php?id=1504
In the control panel header/footer HTML:
%%ADMIN_ID%% = currently logged in admin id.
[ plus more information related to the admin ]

In the private label webmail header/footer HTML:
%%EMAIL%% = currently logged in email address.
[ plus more information related to the user ]]]> http://ideas.mailtrust.com/story.php?id=1503 http://ideas.mailtrust.com/story.php?id=1503 Sat, 07 Jun 2008 00:00:08 -0400 dongo Webmail http://ideas.mailtrust.com/story.php?id=1503
Pre-Defined/Canned Messages...
Give users the ability to highlight a portion of their outgoing email, allowing them to save the selected portion into a Snippet that could be re-used in future replies.

Step 1. Implement a "Snippet Saver" in the composition window.

Step 2. Add a drop down menu to the composition window, with the user's currently defined Snippets; for easy insertion into future replies!

Step 3. ( optional ) Add an organizer for Snippets into the webmail system that could be used to better organize and group pre-defined replies. Giving user's the ability to create, rename, modify, and/or delete existing Snippets.

Some additional uses...
1. This idea could also be used to create multiple outgoing signatures, and/or signatures with HTML content.

2. Could also be setup to provide a one-click reply option from the message list. Instead of having to open a new message and write a reply, a user could simply right-click the message from the list and choose a pre-defined reply.]]> http://ideas.mailtrust.com/story.php?id=1500 http://ideas.mailtrust.com/story.php?id=1500 Thu, 05 Jun 2008 08:01:41 -0400 fall_0ut APIs http://ideas.mailtrust.com/story.php?id=1500
I can use this limited account through the control panel, and some API functions can also be executed correctly.

Anyway I found that the function AddSubaccount() does not honor the permission "Sub-Accounts (Resellers)", while for example the function AddUser() does indeed honor the permission "Mailboxes (Email Accounts)"

The request is for a validation of all API functions to correctly honor their respective account permissions.]]> http://ideas.mailtrust.com/story.php?id=1499 http://ideas.mailtrust.com/story.php?id=1499 Wed, 04 Jun 2008 09:39:48 -0400 mheathcote Control Panel http://ideas.mailtrust.com/story.php?id=1499
Each time I have to contact your support team (who are great by the way) asking to look in the logs for signs of activity regarding the mail in question.

Providing access to the mail logs for the domains via the admin interface would reduce support tickets whilst providing more transparency & visibility for the account admins. You'd naturally have to ensure that the domain logs remain partitioned from a data privacy point of view and reading the logs would obviously require a level of technical understanding from the domain admins.]]> http://ideas.mailtrust.com/story.php?id=1475 http://ideas.mailtrust.com/story.php?id=1475 Wed, 04 Jun 2008 08:36:58 -0400 ankupan Spam Filtering http://ideas.mailtrust.com/story.php?id=1475
I have domain in my control panel and I want to add almost 10 domains in safelist. But now I need to add all 10 domains in each domain for adding them.

any option, where it can be centralized for all domains.]]> http://ideas.mailtrust.com/story.php?id=1431 http://ideas.mailtrust.com/story.php?id=1431 Fri, 30 May 2008 03:48:36 -0400 jnkeefe Control Panel http://ideas.mailtrust.com/story.php?id=1431 http://ideas.mailtrust.com/story.php?id=1402 http://ideas.mailtrust.com/story.php?id=1402 Tue, 20 May 2008 15:39:43 -0400 reellover Control Panel http://ideas.mailtrust.com/story.php?id=1402 http://ideas.mailtrust.com/story.php?id=1262 http://ideas.mailtrust.com/story.php?id=1262 Mon, 19 May 2008 07:21:43 -0400 dynamicdesign http://ideas.mailtrust.com/story.php?id=1262 http://ideas.mailtrust.com/story.php?id=1380 http://ideas.mailtrust.com/story.php?id=1380 Mon, 19 May 2008 07:21:36 -0400 magico Webmail http://ideas.mailtrust.com/story.php?id=1380 1. Customer information cannot have any accents
2. We cannot copy text from other places, because it will have strange characters

It should be upgraded to use only UTF8 solving a problem for non-english marketing emails.]]> http://ideas.mailtrust.com/story.php?id=1322 http://ideas.mailtrust.com/story.php?id=1322 Wed, 14 May 2008 12:25:28 -0400 progscape Group Lists http://ideas.mailtrust.com/story.php?id=1322
Within our Cruise Critic mailtrust, we have an "alias" called "Employees" - we use that so all of the employees can be mailed in one mailing. We have 3 domains - cruisecritic.com, cruisecritic.co.uk & independenttraveler.com. These are all internal customers within Mailtrust/Rackspace/Noteworthy. Keep that in mind.

In your aliases, you are only allowed 50 people. That's acceptable - for now. What isn't is that you're only allowed only 4 "external" addresses. Now, I understand you're doing that for spam purposes, that's fine. What needs to be added is something for internal customers not on the same domain. This means I can only send to 4 people who aren't on cruisecritic.com within this mailing list, yet are internal employees!

I am unwilling to create an alias for each domain (for example, "employees@cruisecritic.co.uk) and then put that in the aliases table within employees@cruisecritic.com. That's just, well, dumb. As long as they are internal employees (and that's the key here), there should be another box available to have as many people in there as possible.

Nannette, from "Customer Care", agrees - "I agree that it is a very frustrating limitation to have to set up aliases to point to the users on a particular domain and then point another alias to the several aliases you have created to represent each domain just so you can email them."

This should be very easy to set up. Have another box set up, where you're able to select any domain that Mailtrust has authority over, and plug it in the same way you do with your "main" domain.

Any questions? Please ask. Thanks.]]> http://ideas.mailtrust.com/story.php?id=1290 http://ideas.mailtrust.com/story.php?id=1290 Wed, 14 May 2008 12:25:28 -0400 progscape Group Lists http://ideas.mailtrust.com/story.php?id=1290
Within our Cruise Critic mailtrust, we have an "alias" called "Employees" - we use that so all of the employees can be mailed in one mailing. We have 3 domains - cruisecritic.com, cruisecritic.co.uk & independenttraveler.com. These are all internal customers within Mailtrust/Rackspace/Noteworthy. Keep that in mind.

In your aliases, you are only allowed 50 people. That's acceptable - for now. What isn't is that you're only allowed only 4 "external" addresses. Now, I understand you're doing that for spam purposes, that's fine. What needs to be added is something for internal customers not on the same domain. This means I can only send to 4 people who aren't on cruisecritic.com within this mailing list, yet are internal employees!

I am unwilling to create an alias for each domain (for example, "employees@cruisecritic.co.uk) and then put that in the aliases table within employees@cruisecritic.com. That's just, well, dumb. As long as they are internal employees (and that's the key here), there should be another box available to have as many people in there as possible.

Nannette, from "Customer Care", agrees - "I agree that it is a very frustrating limitation to have to set up aliases to point to the users on a particular domain and then point another alias to the several aliases you have created to represent each domain just so you can email them."

This should be very easy to set up. Have another box set up, where you're able to select any domain that Mailtrust has authority over, and plug it in the same way you do with your "main" domain.

Any questions? Please ask. Thanks.]]> http://ideas.mailtrust.com/story.php?id=1289 http://ideas.mailtrust.com/story.php?id=1289 Wed, 14 May 2008 12:25:28 -0400 progscape Group Lists http://ideas.mailtrust.com/story.php?id=1289
Within our Cruise Critic mailtrust, we have an "alias" called "Employees" - we use that so all of the employees can be mailed in one mailing. We have 3 domains - cruisecritic.com, cruisecritic.co.uk & independenttraveler.com. These are all internal customers within Mailtrust/Rackspace/Noteworthy. Keep that in mind.

In your aliases, you are only allowed 50 people. That's acceptable - for now. What isn't is that you're only allowed only 4 "external" addresses. Now, I understand you're doing that for spam purposes, that's fine. What needs to be added is something for internal customers not on the same domain. This means I can only send to 4 people who aren't on cruisecritic.com within this mailing list, yet are internal employees!

I am unwilling to create an alias for each domain (for example, "employees@cruisecritic.co.uk) and then put that in the aliases table within employees@cruisecritic.com. That's just, well, dumb. As long as they are internal employees (and that's the key here), there should be another box available to have as many people in there as possible.

Nannette, from "Customer Care", agrees - "I agree that it is a very frustrating limitation to have to set up aliases to point to the users on a particular domain and then point another alias to the several aliases you have created to represent each domain just so you can email them."

This should be very easy to set up. Have another box set up, where you're able to select any domain that Mailtrust has authority over, and plug it in the same way you do with your "main" domain.

Any questions? Please ask. Thanks.]]> http://ideas.mailtrust.com/story.php?id=1288 http://ideas.mailtrust.com/story.php?id=1288 Wed, 14 May 2008 12:25:28 -0400 progscape Group Lists http://ideas.mailtrust.com/story.php?id=1288
Within our Cruise Critic mailtrust, we have an "alias" called "Employees" - we use that so all of the employees can be mailed in one mailing. We have 3 domains - cruisecritic.com, cruisecritic.co.uk & independenttraveler.com. These are all internal customers within Mailtrust/Rackspace/Noteworthy. Keep that in mind.

In your aliases, you are only allowed 50 people. That's acceptable - for now. What isn't is that you're only allowed only 4 "external" addresses. Now, I understand you're doing that for spam purposes, that's fine. What needs to be added is something for internal customers not on the same domain. This means I can only send to 4 people who aren't on cruisecritic.com within this mailing list, yet are internal employees!

I am unwilling to create an alias for each domain (for example, "employees@cruisecritic.co.uk) and then put that in the aliases table within employees@cruisecritic.com. That's just, well, dumb. As long as they are internal employees (and that's the key here), there should be another box available to have as many people in there as possible.

Nannette, from "Customer Care", agrees - "I agree that it is a very frustrating limitation to have to set up aliases to point to the users on a particular domain and then point another alias to the several aliases you have created to represent each domain just so you can email them."

This should be very easy to set up. Have another box set up, where you're able to select any domain that Mailtrust has authority over, and plug it in the same way you do with your "main" domain.

Any questions? Please ask. Thanks.]]> http://ideas.mailtrust.com/story.php?id=1287 http://ideas.mailtrust.com/story.php?id=1287 Wed, 14 May 2008 12:25:28 -0400 progscape Group Lists http://ideas.mailtrust.com/story.php?id=1287
Within our Cruise Critic mailtrust, we have an "alias" called "Employees" - we use that so all of the employees can be mailed in one mailing. We have 3 domains - cruisecritic.com, cruisecritic.co.uk & independenttraveler.com. These are all internal customers within Mailtrust/Rackspace/Noteworthy. Keep that in mind.

In your aliases, you are only allowed 50 people. That's acceptable - for now. What isn't is that you're only allowed only 4 "external" addresses. Now, I understand you're doing that for spam purposes, that's fine. What needs to be added is something for internal customers not on the same domain. This means I can only send to 4 people who aren't on cruisecritic.com within this mailing list, yet are internal employees!

I am unwilling to create an alias for each domain (for example, "employees@cruisecritic.co.uk) and then put that in the aliases table within employees@cruisecritic.com. That's just, well, dumb. As long as they are internal employees (and that's the key here), there should be another box available to have as many people in there as possible.

Nannette, from "Customer Care", agrees - "I agree that it is a very frustrating limitation to have to set up aliases to point to the users on a particular domain and then point another alias to the several aliases you have created to represent each domain just so you can email them."

This should be very easy to set up. Have another box set up, where you're able to select any domain that Mailtrust has authority over, and plug it in the same way you do with your "main" domain.

Any questions? Please ask. Thanks.]]> http://ideas.mailtrust.com/story.php?id=1286 http://ideas.mailtrust.com/story.php?id=1286 Wed, 14 May 2008 12:25:28 -0400 progscape Group Lists http://ideas.mailtrust.com/story.php?id=1286
Within our Cruise Critic mailtrust, we have an "alias" called "Employees" - we use that so all of the employees can be mailed in one mailing. We have 3 domains - cruisecritic.com, cruisecritic.co.uk & independenttraveler.com. These are all internal customers within Mailtrust/Rackspace/Noteworthy. Keep that in mind.

In your aliases, you are only allowed 50 people. That's acceptable - for now. What isn't is that you're only allowed only 4 "external" addresses. Now, I understand you're doing that for spam purposes, that's fine. What needs to be added is something for internal customers not on the same domain. This means I can only send to 4 people who aren't on cruisecritic.com within this mailing list, yet are internal employees!

I am unwilling to create an alias for each domain (for example, "employees@cruisecritic.co.uk) and then put that in the aliases table within employees@cruisecritic.com. That's just, well, dumb. As long as they are internal employees (and that's the key here), there should be another box available to have as many people in there as possible.

Nannette, from "Customer Care", agrees - "I agree that it is a very frustrating limitation to have to set up aliases to point to the users on a particular domain and then point another alias to the several aliases you have created to represent each domain just so you can email them."

This should be very easy to set up. Have another box set up, where you're able to select any domain that Mailtrust has authority over, and plug it in the same way you do with your "main" domain.

Any questions? Please ask. Thanks.]]>