29 Mar
2010
29 Mar
'10
4:02 p.m.
Hi,
I am planning a large pop3 -> pop3 + imap migration across data centers
and countries.
I just found out about perdition and I need to understand if it will
help solve a few problems.
1 - Usernames with ' . ' (dots) in it.
There are several usernames with dots in it. The destination
server is a Cyrus Imapd with the default
hierarchy setup (no dots).
For what I read in the pertitiondb man page, I could use
something like:
(.*)\.(.*):$1_$2@newserver:port
Where the account in the new server will obviously have an
underscore to replace the dot.
Is this right?
2 - --outgoing_server* *SERVER_A,SERVER_B*
*
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?
3 - virtual domain support: user@domain
This is not clear to me.
For what I understood, this will be split into user as the
login and domain will be the host to connect.
Is that right?
If so, how can I prevent it?
Also How do I map it?
e.g.: user@domain to server:port
user@domain:user@domain@server:port
is that it?
Thanks,
Raul
*
*
29 Mar
29 Mar
9:58 p.m.
On Mon, Mar 29, 2010 at 01:02:43PM -0300, Raul Dias wrote:
Hi,
I am planning a large pop3 -> pop3 + imap migration across data centers
and countries.
I just found out about perdition and I need to understand if it will
help solve a few problems.
1 - Usernames with ' . ' (dots) in it.
There are several usernames with dots in it. The destination
server is a Cyrus Imapd with the default
hierarchy setup (no dots).
For what I read in the pertitiondb man page, I could use
something like:
(.*)\.(.*):$1_$2@newserver:port
Where the account in the new server will obviously have an
underscore to replace the dot.
Is this right?
Yes, that should work as you describe. You will also to enable the
username_from_database configuration directive.
2 - --outgoing_server* *SERVER_A,SERVER_B*
*
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.
3 - virtual domain support: user@domain
This is not clear to me.
For what I understood, this will be split into user as the
login and domain will be the host to connect.
Is that right?
If so, how can I prevent it?
There are several different ways that perdition can work in this regard.
It can split on the @ or it can treat user@domain as an atomic unit.
Firstly, if you have client_server_specification enabled,
then the user can specify the server using user@server.
This option is off by default.
Secondly there key used to lookup the user in the popmap.
This may or may be controlled using the query_key option.
The default is \U which means the full username, that is
user@domain and not just user.
Lastly there is the strip_domain option which allows
the domain name to be removed when querying the popmap;
performing local authentication (local authentication is disabled by default),
performing remote authentication; or some combination of these.
By default strip_domain is disabled.
There is some overlap between the query_key and strip_domain as they
were added to the perdition at different times.
Also How do I map it?
e.g.: user@domain to server:port
user@domain:user@domain@server:port
is that it?
I would need to check the code for this case, but yes, that should work
as perdition should search from the end for the last @ and use it
to split the user from the server/port information. And if the
user contains a @, that should be fine.
An alternative is to choose a different delimiter, which can be more
than one character long. This required recompiling perdition.
Some popmap mechanisms, for example LDAP, don't require such complex
string composition as the user, server and port can be stored as
discreet elements.
30 Mar
30 Mar
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.
4:28 a.m.
On Tue, Mar 30, 2010 at 12:48:19AM -0300, Raul Dias wrote:
Em 29-03-2010 18:58, Simon Horman escreveu:
Understood.
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. *
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.
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).
I have made some one-off customisations to perdition in the past
to do things like this. If you are interested I'd be happy
to talk over what something that does this in a generic way
that could be merged into the main code might look like.
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 believe that Cyrus murder allows merging of mailboxes,
but I'm not familiar with the details.
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.
Good point. I believe that it was added because someone had a use for
it at some point. But I don't recall what that was.
8:35 a.m.
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).
I have made some one-off customisations to perdition in the past
to do things like this. If you are interested I'd be happy
to talk over what something that does this in a generic way
that could be merged into the main code might look like.
10:07 a.m.
Em 30-03-2010 01:28, Simon Horman escreveu:
Yes, please.
:)
Not really.
It distributes accounts on different servers.
But the same account is always on the same server.
-Raul
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).
I have made some one-off customisations to perdition in the past
to do things like this. If you are interested I'd be happy
to talk over what something that does this in a generic way
that could be merged into the main code might look like.
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 believe that Cyrus murder allows merging of mailboxes,
but I'm not familiar with the details.
10:27 a.m.
On Tue, Mar 30, 2010 at 09:35:25AM +0100, Jonathan Gilpin wrote:
Understood.
This is exactly what I need to do too... I need to migrate accounts from
one mail system to another system. So I need to be able to say.. this
email login is on this server while this is on another and then update
the table when the account has been moved..
Are those customisations available to use?
I think that should be possible.
I just need to distil the changes out (as a patch against 1.17).
>
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.
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).
I have made some one-off customisations to perdition in the past
to do things like this. If you are interested I'd be happy
to talk over what something that does this in a generic way
that could be merged into the main code might look like.
5164
days inactive
5165
days old
6 comments
3 participants
participants (3)
-
Jonathan Gilpin -
Raul Dias -
Simon Horman