30 Mar
2010
30 Mar
'10
3:48 a.m.
Em 29-03-2010 18:58, Simon Horman escreveu:
On Mon, Mar 29, 2010 at 01:02:43PM -0300, Raul Dias
wrote:
2 - --outgoing_server* *SERVER_A,SERVER_B*
As I said before, I am about to start a mass migration of thousands
accounts (pop3)
that might take a really long time.
Before knowing Perdition, my plan was to write a pop3 proxy (have done
that in the past)
that monitors if an account has been transferred or not and points to
the right server (new/old).
What I wish that Perdition would do with two mailboxes was to simulated
them as one. So, that
if there are 4 messages in server A and 10 in server B, the client would
see them as one server
with 14 messages. Probably there will be some uid issues to resolve.
I was hoping that this would be what that option do. I really don't see
a point in using a round
robin server select for imap/pop3 in real world.
- Raul
*
It was not clear yet, how will --outgoing_server works.*
* On each connection it will connect to one of ther servers
only. Is that it?
If so, whats the advantage?
*
* Or will it connect to both servers and retrieve messages from
both? (what I need)
I understand that on a imap server this is not so easy, but on
pop3 doent seems to be a big challenge.
If this is not how it works? Is there something that could be
done achieve this behaviour?
As it stands perdition only connects to one real-server.
If more than one real-server is supplied using the outgoing_server
option then those real servers are tried in order. Though
there is a (very simple) round-robin algorithm that selects which
one to try first.
Could you describe in a little more detail what you need to achieve
with two mailboxes? It may be possible to enhance perdition in order
to meet your needs.