[Tickets #8077] Re: Allow multiple accounts in IMP
bugs at horde.org
bugs at horde.org
Wed Mar 28 06:28:40 UTC 2012
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/8077
------------------------------------------------------------------------------
Ticket | 8077
Updated By | Michael Slusarz <slusarz at horde.org>
Summary | Allow multiple accounts in IMP
Queue | IMP
Version | Git master
Type | Enhancement
State | Accepted
Priority | 2. Medium
-Milestone | 5.1
+Milestone | 6+
Patch |
Owners | Michael Slusarz
------------------------------------------------------------------------------
Michael Slusarz <slusarz at horde.org> (2012-03-28 00:28) wrote:
> This feature is discussed (in a positive, it just works, sense) a
> lot online because it has been a feature for a long time with
> IMP3/4. It was quite hard to to find this page and properly confirm
> that it is now depreciated in IMP5. I have added a (rather terse,
> sorry, I was suffering a sense of humour failure) note to the Wiki
> page about this.
No, this ticket does not implement the previous functionality. The
old code was nothing more than a web interface to a (not very
optimized) PHP port of fetchmail. Which wasn't all that useful for
anyone with more than a few hundred messages, since PHP would time-out
or memory fail long before you could synchronize an account.
This ticket is instead a request to add foreign accounts to appear
natively in the UI. Which would allow access of these accounts
without expensive overhead (and allow the synchronization of mail
actions).
> From the search results seen before I found this page I imagine that
> hosting providers (plesk/cpanel based) will have a strong incentive
> to get this restored since they have been offering IMP as a mail
> aggregator service to their customers. They may well feel that this
> issue is a blocker for IMP5 adoption.
I would love to see this request also. But the people that currently
pay me to work on IMP do not have this as a priority. Unfortunately,
that is the reality of the situation, especially for something as
resource intensive as this request.
More information about the bugs
mailing list