mail_addr field [split from (HowTo) Replace courier with dovecot]

[jmeyerdo]

Hi!

I moved my complete email-handling to mysql - I changed to dovecot before and moved to postfix-mysql-handling additional so that the hash-files are not needed any longer.

I posted my postfix-mysql-configuration here:
http://www.isp-control.net/forum/domain-...-1781.html

If anybody can confirm this you/I can add this to the WIKI, too.

Kind regards, Jens

[BeNe]

Fine! Big thanks @jmeyerdo.
I will take a look about it. German comments in it, nice

So we need the mail_adress field for dovecot and the $mail_id variable for the WebmailPass changer right ?
--> http://www.isp-control.net/ispcp/wiki/howto_webmailpass
Joxi already did a patch - thanks here also.

So we could release the next Version with a PW Changer per default.

Greez BeNe

[Zothos]

mail_addr field is on the way.

[jmeyerdo]

Hi!

Just for understanding: Is it possible to describe the "mail_addr field"-discussion in 2-3 sentences?

Thx, Jens

[rbtux]

yeah...

In the database there is a mail_addr field, but its not filled in by ispcp. When it would provide the mail adresse all the nasty joins between mail and domain tables would be past us ;-)

[BeNe]

And maybe joxi can patch the trunk for the $mail_id variable.
So Dovecot with AvelSieve and PW changer is welcome in ispCP

Greez BeNe

[joximu]

Hi

the mail_id has to be patch into the passwd-plugin - but there are more things to change.

With the mail_address field thing would be *far* easier.

I'd suggest: make use of mail_address and then we can provide a webmail including password change (then the idea of including squirrel with ispCP makes (little) more sense...)

/J
PS: Sure I can commit this into the trunk... when it's ready..

[joximu]

Hi Zothos, what about with the patch.
I added one to ticket 747 http://www.isp-control.net/ispcp/ticket/747 months ago.

Either I'll update this or you can send me your patch then I take the best.

Or did you sent it to RatS?

Cheers J

[joximu]

Hi people

I try here because it's on topic... (not in the title but in the thread..)

I had a look over my old patch and made many corrections based on a php file by deptray (http://www.isp-control.net/forum/thought...#pid12506)

My first tests were ok - 3 adresses (normal dom, alias & subdomain).

at the moment we only use the field mail_addr for normal mail accounts (no forwardings and catchall) - but for the sql phrases maybe it should be kept in mind that maybe sometime also the forwards have an entry in mail_addr. So there should also be another check if we only want the real mail accounts - let's choose the best...
mail_pass != _no_
mail_forward = _no_ (beware -> catchall)
mail_type = %\_mail

Please check the new client/add_mail_acc.php - for all installations since december at least...

If it's ok, we need an update script :-)
some sort of php piece to go through the table and set all mail_addr for the mail accounts till today...

/Joxi

[Zothos]

My patch im currently wirking on is mostly the same as yours. Could you make a patch out of it if you have tested it?
So i can concentrate on my update functions.
Im currently creating a gui for this. Every DB update could take place there.
More informations in the dev forum when im ready Should be ready by the end of the week.