postfixadmin-devel — Postfix Admin development talk - users are also welcome

Re: [Postfixadmin-devel] 2.3.1 bugfix release?

[ja n. <re...@ya...>]

> I absolutely agree that 2.3 non-smarty should be maintained, and that
> the smarty branch should be tagged as 2.4...

I think we should branch the non-smarty version as 2.3 and release bugfix versions as 2.3.x. Trunk including the smarty changes should continue as 2.4.

Regards,
Sebastian

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. 
http://mail.yahoo.com 

Re: [Postfixadmin-devel] big merge/commit of smarty branch into?trunk

[Christian B. <pos...@cb...>]

Hello,

Am Freitag, 20. November 2009 schrieb David Goodwin:
> Christian Boltz wrote :
> > BTW: Is there a way to make smarty working without the templates_c
> > directory? If yes, it could serve as a fallback solution and the
> > error message could be "just" a warning. (The reduced performance
> > because of the missing cache would be better than blocking
> > everything ;-)
> 
> Yes; you can tell it to not compile templates (i.e. re-compile every
> template every time etc). No one is likely to notice the performance
> hit of this.

Sounds interesting :-)
Can you implement this, please?

I'm not sure if disabling templates_c in general is the best idea, but 
having a fallback if templates_c isn't writeable or doesn't exist would 
be good.


Regards,

Christian Boltz
-- 
> You only read the second paragraph, didn't you?
Why do you write emails where one has to read the stuff
between the first and the last word?
[> Stephan Kulow and Dirk Mueller in opensuse-packaging]

Re: [Postfixadmin-devel] 2.3.1 bugfix release?

[Tanstaafl <tan...@li...>]

On 12/5/2009 8:18 PM, Christian Boltz wrote:
> there have been some bugfixes since the 2.3 release, including the XSS 
> fix for the login form.
> 
> IMHO we should merge all bugfixes, language updates etc. into the 2.3 
> branch and do a 2.3.1 release (non-smarty).
> 
> Thoughts? Objections?

I absolutely agree that 2.3 non-smarty should be maintained, and that
the smarty branch should be tagged as 2.4...

> (Technical note: upgrade.php needs a change in the 2.3 branch - instead 
> of auto-detecting the target version from the SVN revision, we need to 
> hardcode it. Otherwise upgrades from the 2.3 branch to trunk might 
> fail.)

As long as upgrades from older version will work without incident
(barring unforeseen bugs)...

> Current trunk (with smarty) doesn't look too bad, but I'm aware of 
> several small problems which mean that it isn't release-quality.

Hence making that the next major version target (2.4? 3.0?)...

Thanks for your work on postfixadmin Christian, David and everyone else
involved! The new changes are awesome!

[Postfixadmin-devel] 2.3.1 bugfix release?

[Christian B. <pos...@cb...>]

Hello,

there have been some bugfixes since the 2.3 release, including the XSS 
fix for the login form.

IMHO we should merge all bugfixes, language updates etc. into the 2.3 
branch and do a 2.3.1 release (non-smarty).

Thoughts? Objections?

(Technical note: upgrade.php needs a change in the 2.3 branch - instead 
of auto-detecting the target version from the SVN revision, we need to 
hardcode it. Otherwise upgrades from the 2.3 branch to trunk might 
fail.)


Current trunk (with smarty) doesn't look too bad, but I'm aware of 
several small problems which mean that it isn't release-quality.


Regards,

Christian Boltz
-- 
> Genau, Office und M$-Programme haben meist alle den gleichen Stil.
Stimmt, die schaffen das Kammquoting meist besonders gut.    *g,d&r*
[> Andre Heine und Florian Gross in suse-linux]

Re: [Postfixadmin-devel] Setting up a wiki?

[Christian B. <pos...@cb...>]

Hello,

Am Samstag, 5. Dezember 2009 schrieb Tanstaafl:
> On 12/4/2009 6:11 PM, Christian Boltz wrote:
> > What do you think? Do we need a wiki? Where should it be hosted?
> 
> I think its a great idea - 

Looks like everybody likes the idea :-)

I have setup the wiki on sourceforge:
    https://sourceforge.net/apps/mediawiki/postfixadmin/

The configuration I did is very minimal - I uploaded the postfixadmin 
logo and wrote something on the main page ;-)
If anything is missing and/or doesn't work as expected, please tell me.

I also tried to change the logo positioning using MediaWiki:Common.css 
but it is not honored yet (maybe the SF theme doesn't include 
MediaWiki:Common.css)

If CSS inclusion works somehow, maybe I'll do some CSS-based styling to 
make the wiki looking more like postfixadmin - unfortunately I'm too 
busy to do it right now.

> that way us users/non-coders can
>  contribute at least a little... :)

Feel free to add content to the wiki. If you also add some structure 
(categories etc.) it would be even better ;-)

(For the beginning, I have included a link to Special:Allpages on the 
main page.)

Note: I did not test if a normal user has write permissions 
automatically (admin has ;-) - if not, send me a mail with your SF 
username and I'll give you the needed permissions.

> I see no reason to not use sourceforge... especially if you can
>  easily migrate it to your own host later if a need arose, without
>  losing any of the data, which I think you can...?

Well, the CSS problem (not including MediaWiki:Common.css) might be a 
disadvantage (or just a bug - I opened a ticket) of the SF hosting. 
Also some administrative things are not available, hopefully nothing 
I'll need ;-)

Sourceforge offers an option to download the database dump and all 
files, therefore we can start on SF and move if/whenever needed.


Regards,

Christian Boltz
-- 
Bist du Rechtsanwalt oder soll ich das persönlich nehmen?
[Marius Brehler in suse-talk]

Re: [Postfixadmin-devel] Setting up a wiki?

[Tanstaafl <tan...@li...>]

On 12/4/2009 6:11 PM, Christian Boltz wrote:
> What do you think? Do we need a wiki? Where should it be hosted?

I think its a great idea - that way us users/non-coders can contribute
at least a little... :)

I see no reason to not use sourceforge... especially if you can easily
migrate it to your own host later if a need arose, without losing any of
the data, which I think you can...?

-- 

Best regards,

Charles

Re: [Postfixadmin-devel] Setting up a wiki?

[David G. <da...@co...>]

Christian Boltz wrote :
> Hello,
> 
> I'm thinking about setting up a wiki for postfixadmin.
> 
> The most obvious usecase would be to have a place for config examples 
> for postfix, courier, dovecot etc. - some of these things are 
> somewhere[tm] in the forum, but hard to find.
> 
> I'm quite sure we (developers and users) would find other usecases once 
> the wiki exists ;-)
> 
> My proposal is to use Mediawiki - either 
> a) as hosted app on sourceforge (that would mean no maintenance work, 
>    but not too much admin access) 
> b) on my server (where I can do anything if needed)
> 
> I guess we should try the hosted app because we probably don't even need 
> to do much administration ;-)
> 
> 
> What do you think? Do we need a wiki? Where should it be hosted?
> 

Can't hurt to try; as long as it doesn't turn into some barren out of
date documentation dessert.

I think it should be hosted on sourceforge.

David.
-- 
David Goodwin 

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]

Re: [Postfixadmin-devel] Setting up a wiki?

[Robert S. <ro...@sc...>]

Christian Boltz schrieb:
> Hello,
> 
> I'm thinking about setting up a wiki for postfixadmin.
> 
> The most obvious usecase would be to have a place for config examples 
> for postfix, courier, dovecot etc. - some of these things are 
> somewhere[tm] in the forum, but hard to find.
> 
> I'm quite sure we (developers and users) would find other usecases once 
> the wiki exists ;-)
> 
> My proposal is to use Mediawiki - either 
> a) as hosted app on sourceforge (that would mean no maintenance work, 
>    but not too much admin access) 
> b) on my server (where I can do anything if needed)
> 
> I guess we should try the hosted app because we probably don't even need 
> to do much administration ;-)
> 
> 
> What do you think? Do we need a wiki? Where should it be hosted?
> 
> 
> Regards,
> 
> Christian Boltz

Hi Christian, nice idea !!!

-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

[Postfixadmin-devel] Setting up a wiki?

[Christian B. <pos...@cb...>]

Hello,

I'm thinking about setting up a wiki for postfixadmin.

The most obvious usecase would be to have a place for config examples 
for postfix, courier, dovecot etc. - some of these things are 
somewhere[tm] in the forum, but hard to find.

I'm quite sure we (developers and users) would find other usecases once 
the wiki exists ;-)

My proposal is to use Mediawiki - either 
a) as hosted app on sourceforge (that would mean no maintenance work, 
   but not too much admin access) 
b) on my server (where I can do anything if needed)

I guess we should try the hosted app because we probably don't even need 
to do much administration ;-)


What do you think? Do we need a wiki? Where should it be hosted?


Regards,

Christian Boltz
-- 
> I also prefer realnames. But if people want to use a _spellable_
> alias, it's ok for me too.
> However, I hate aliases like "fE3,x7~5X" ;-)
Noone should use his/her password as a mail name ;-)
[> Christian Boltz and meister(at)netz00.com in opensuse]

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[Tanstaafl <tan...@li...>]

On 12/4/2009, David Goodwin (da...@co...) wrote:
>> So, did anyone else see TWO attachments?? Its not a big deal, I'm just
>> curious - it could explain why the size of the email was so big, if
>> there was another 'hidden' attachment.

> I see two - postfixadmin1.bmp and postfixadmin2.bmp
> 
> Perhaps I should include a screenshot showing the offending
> attachments to fit in with this thread?  :)

Sure, if you like... :)

That is weird. I can't check again because I deleted it, but I am
absolutely sure it only showed one attachment (postfixadmin2.bmp).

I'm using Thunderbird 2.0.0.23 on Windows...

Oh well...

-- 

Best regards,

Charles

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[David G. <da...@co...>]

> So, did anyone else see TWO attachments?? Its not a big deal, I'm just
> curious - it could explain why the size of the email was so big, if
> there was another 'hidden' attachment.
> 

I see two - postfixadmin1.bmp and postfixadmin2.bmp

Perhaps I should include a screenshot showing the offending
attachments to fit in with this thread? :)

David.
-- 
David Goodwin 

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[Tanstaafl <tan...@li...>]

On 12/4/2009, Johan Hendriks (Jo...@do...) wrote:
>>> I attached 2 screenshots that i get after i updated my 2.4 developer
>>> postfixadmin version.

>> First - I only see one attachment,

> I only looked at the little one and thought that the other would be
> something of the same size.

Again, I only saw one??

>> which when saved, is only 500KB in size, so I'm not sure why the
>> email is 1.8MB in size, but regardless...

> Totally off-topic but this is because of mime encoding etc  :) 
> That's why mail should only be used for plaintext messages  ;) 

Well, yeah, I know that encoding binary attachments will increase their
size, but I've never seen a 500KB file expand to anything close to 1.8MB
when encoded. At most I would expect it to only double or so in size.

The reason I mentioned that specifically, is because the OP said there
were TWO attachments, and I only saw ONE.

So, did anyone else see TWO attachments?? Its not a big deal, I'm just
curious - it could explain why the size of the email was so big, if
there was another 'hidden' attachment.

-- 

Best regards,

Charles

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[Johan H. <Jo...@do...>]

>>> Whoah... was that really necessary? Sending huge binary attachments
to
>>> email lists is a big no-no...

>> *shrug* personally i was just glad he took the time to report the
bug!

>Well... yeah... ;)

>I only complained because that account is on a slow IMAP connection,
and
>that email took 2 minutes to download...

>-- 

>Best regards,

>Charles

Well to all sorry about the size of the mail.
Sorry for wasting 2 minutes of your life ;-)

I only looked at the little one and thought that the other would be
something of the same size.

But then again you know what they say
assumption is the mother of all f*ckups

Again sorry an it will not happen again.

Regards,
Johan

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[Tanstaafl <tan...@li...>]

On 12/3/2009 9:39 AM, David Goodwin wrote:
>> Whoah... was that really necessary? Sending huge binary attachments to
>> email lists is a big no-no...

> *shrug* personally i was just glad he took the time to report the bug!

Well... yeah... ;)

I only complained because that account is on a slow IMAP connection, and
that email took 2 minutes to download...

-- 

Best regards,

Charles

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[David G. <da...@co...>]

Tanstaafl wrote :
> On 12/2/2009 10:41 AM, Johan Hendriks wrote:
> > I attached 2 screenshots that i get after i updated my 2.4 developer
> > postfixadmin version.
> 
> Whoah... was that really necessary? Sending huge binary attachments to
> email lists is a big no-no...
> 
> First - I only see one attachment, which when saved, is only 500KB in
> size, so I'm not sure why the email is 1.8MB in size, but regardless...
> 
> There are lots of apps around for resizing graphics like that for email.
> On Windows (which you are appparently using), I like TinyPic...
> 
> It converted your 500KB to a 35KB file...
> 
> Also, you really shouldn't use .bmp format - .png (or even .jpg or .gif)
> gives much better results for screenshots...

*shrug* personally i was just glad he took the time to report the bug!

David
-- 
David Goodwin 

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[Michiel v. B. <mi...@va...>]

On 08:44, Thu 03 Dec 09, Tanstaafl wrote:
> On 12/2/2009 10:41 AM, Johan Hendriks wrote:
> > I attached 2 screenshots that i get after i updated my 2.4 developer
> > postfixadmin version.
> 
> First - I only see one attachment, which when saved, is only 500KB in
> size, so I'm not sure why the email is 1.8MB in size, but regardless...

Totally off-topic but this is because of mime encoding etc :)
That's why mail should only be used for plaintext messages ;)

-- 

Michiel van Baak
mi...@va...
http://michiel.vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer aficionados are both called users?"

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[Tanstaafl <tan...@li...>]

On 12/2/2009 10:41 AM, Johan Hendriks wrote:
> I attached 2 screenshots that i get after i updated my 2.4 developer
> postfixadmin version.

Whoah... was that really necessary? Sending huge binary attachments to
email lists is a big no-no...

First - I only see one attachment, which when saved, is only 500KB in
size, so I'm not sure why the email is 1.8MB in size, but regardless...

There are lots of apps around for resizing graphics like that for email.
On Windows (which you are appparently using), I like TinyPic...

It converted your 500KB to a 35KB file...

Also, you really shouldn't use .bmp format - .png (or even .jpg or .gif)
gives much better results for screenshots...

-- 

Best regards,

Charles

Re: [Postfixadmin-devel] after update svn rev 781 and 782 i got some errors

[David G. <da...@co...>]

Johan Hendriks wrote :
> I attached 2 screenshots that i get after i updated my 2.4 developer
> postfixadmin version.
> 
> The search box does not show the domains, also creation of a new mailbox
> does not work (i can not select domain.)
> 
> 

looks like my fault...

(the change I made to smarty yesterday)

Thanks for pointing it out; I'll fix it shortly.... 

Oddly my development version appeared totally unthemed and looked
almost broken on the login page - is everyone's like this?

David.


> 
> this is what i see in my apache log file
> 
>  
> 
> [Wed Dec 02 16:37:25 2009] [error] [client 192.168.50.114] PHP Warning:
> htmlentities() [<a
> href='function.htmlentities'>function.htmlentities</a>]: Invalid
> multibyte sequence in argument in
> /usr/local/www/postfixadmin/smarty.inc.php on line 25, referer:
> http://192.168.50.201/mailadmin/list-virtual.php?domain=xxxxxxxxxx.xxx
> 
> [Wed Dec 02 16:37:25 2009] [error] [client 192.168.50.114] PHP Notice:
> Undefined index:  domain in /usr/local/www/postfixadmin/list-domain.php
> on line 106, referer:
> http://192.168.50.201/mailadmin/list-virtual.php?domain=xxxxxxxxxxx.xxx
> 
> [Wed Dec 02 16:37:36 2009] [error] [client 192.168.50.114] PHP Warning:
> htmlentities() [<a
> href='function.htmlentities'>function.htmlentities</a>]: Invalid
> multibyte sequence in argument in
> /usr/local/www/postfixadmin/smarty.inc.php on line 25, referer: 
> http://192.168.50.201/mailadmin/list-domain.php
> 
>  
> 
>  
> 
> regards
> 



> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing. 
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel


-- 
David Goodwin 

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]

[Postfixadmin-devel] Postfixadmin + Spamassassin settings question.

[aja-lists <aja...@tn...>]

Hi,

Would this work with the latest stable PostfixAdmin version ?
http://wiki.mattrude.com/index.php/SpamAssassin#Configuring_Spamassassin_.28MySQL_.26_Virtual_Users.29

Or can someone point me to a better mysql + spamassassin settings howto ?

Postfixadmin + mysql + Dovecot + Dovecot LDA is in use.
Basically the only thing i'd like to accomplish is to have different
spamassassin settings for one (1) email-user.
Spamassassin is already in use with a simple pipe with postfix construction

Regards,
Adrian

Re: [Postfixadmin-devel] alignment

[reg9009 <re...@ya...>]

Johan Hendriks schrieb:
>
> Hello i use 2.4 just to test.
> The allignment of the tables are not in Sync.
> See the attachment
>
>  
>
> Regards,
> Johan Hendriks
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> ------------------------------------------------------------------------
>
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>   
Hi Johan,

fixed in rev 775, thx.

Regards,
Sebastian

Re: [Postfixadmin-devel] big merge/commit of smarty branch into?trunk

[David G. <da...@co...>]

Christian Boltz wrote :
> Hello,
> 
> Am Donnerstag, 5. November 2009 schrieb David Goodwin:
> [templates_c]
> > a) setup.php has a check to see whether it exists and is writeable
> 
> Good idea. Just try to write some text to a test file ;-)
> 
> > b) if templates_c is not writeable, 
> 
> Then display an error message ;-)
> 
> > we use e.g. /tmp/?
> 
> Please don't do this. The filenames in templates_c are predictable and 
> therefore at the risk of symlink attacks.
> 
> BTW: Is there a way to make smarty working without the templates_c 
> directory? If yes, it could serve as a fallback solution and the error 
> message could be "just" a warning. (The reduced performance because of 
> the missing cache would be better than blocking everything ;-)
> 

Yes; you can tell it to not compile templates (i.e. re-compile every
template every time etc). No one is likely to notice the performance
hit of this.

David.

-- 
David Goodwin 

[ david at codepoets dot co dot uk ]
[ http://www.codepoets.co.uk       ]

Re: [Postfixadmin-devel] big merge/commit of smarty branch into trunk

[Christian B. <pos...@cb...>]

Hello,

Am Donnerstag, 5. November 2009 schrieb David Goodwin:
[templates_c]
> a) setup.php has a check to see whether it exists and is writeable

Good idea. Just try to write some text to a test file ;-)

> b) if templates_c is not writeable, 

Then display an error message ;-)

> we use e.g. /tmp/?

Please don't do this. The filenames in templates_c are predictable and 
therefore at the risk of symlink attacks.

BTW: Is there a way to make smarty working without the templates_c 
directory? If yes, it could serve as a fallback solution and the error 
message could be "just" a warning. (The reduced performance because of 
the missing cache would be better than blocking everything ;-)


Regards,

Christian Boltz
-- 
Ossi-Virus
Güdn tog, isch bün än Häggr aüs Läibzsch un dis is än selbsdprögammirdr
bösardscher Gommbjudrfirus. Do isch nö nit sö vül wäis von döm Gommbjudr
is dis än mänuoöllr Firus. Alsö löschnse bidde ölle Dodein fön de
Fesdpladde und schiggnse disn Firus ön ölle di se genn.
- Dangge für de Midorbeid -

Re: [Postfixadmin-devel] Upgrade question Postfixadmin 2.3

[Christian B. <pos...@cb...>]

Hello,

Am Montag, 16. November 2009 schrieb aja-lists:
> Simone Piccardi wrote:
> > I had the same issue after running the upgrade script for a 2.2
> > database.
> >
> > It was solved just adding the quota column in the domain table
> > after the maxquota column.

Those things should not happen and qualify as bug ;-)

(Un)fortunately I never saw this problem on my system.
Do you still have a database dump of the old table (before upgrading)?
If yes, please post it (just the table structure + content of the 
"config" table which should be one line).

BTW: do you use MySQL or PgSQL?

>  I decided to put back a
>  backup and started upgrading again, that gave amongst others a
>  "config" table not found which could not be handled by the
>  upgrade.php

Hmm, another thing I've never seen...

What was the exact error message? 
Which query was executed at this time? (see upgrade.php?debug=1) 
Does your database user have permissions to create and alter tables? 
And, as above: a database dump would be helpful.


Regards,

Christian Boltz
-- 
Bei etwas größeren Dingen mit 6stelligem Budget kommt gern mal
"plötzlich" ein Onlineshop dazu. Oder ein Ticketsystem. So ganz
von alleine. Gucki, ich bin eine kleine Kundenidee - ist das viel
Arbeit? ;) [Ratti in suse-linux]

Re: [Postfixadmin-devel] Hooks

[Aaron D. <aa...@da...>]

Christian Boltz wrote:
> # Hello,
> 
> Am Samstag, 14. November 2009 schrieb Aaron Dalton:
>> I'm new to postfixadmin.  I am managing a dozen or so domains, all of
>> which I wish to use with DKIM.  Having the admins manually edit text
>> files listing domains and keys is a problem.  Are there any hooks I
>>  can attach a script to that will manage these files for me?
> 
> I'm not really familiar with DKIM and what it needs, so I'll just give
> you the list of available hooks (which can call external scripts):
> 
> # grep -B1 "CONF.*script" config.inc.php
> // Parameters: (1) username (2) domain (3) maildir (4) quota
> // $CONF['mailbox_postcreation_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postcreation.sh';
> --
> // Parameters: (1) username (2) domain (3) maildir (4) quota
> // $CONF['mailbox_postedit_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postedit.sh';
> --
> // Parameters: (1) username (2) domain
> // $CONF['mailbox_postdeletion_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postdeletion.sh';
> --
> // Parameters: (1) username
> //$CONF['domain_postcreation_script']='sudo -u courier /usr/local/bin/postfixadmin-domain-postcreation.sh';
> --
> // Parameters: (1) username
> // $CONF['domain_postdeletion_script']='sudo -u courier /usr/local/bin/postfixadmin-domain-postdeletion.sh';
> 
> It should be obvious when the hooks are called (and since two minutes 
> config.inc.php also contains the information about the parameters that 
> are handed over to the scripts ;-)
> 
> If you need other hooks, please tell us what you need.
> 
> 

Thank you for the info!  I appreciate your help.  Those scripts are
sufficient for my needs.  The DKIM-milter I'm using needs a text file
listing domains and key files.  These hooks will let me maintain them
just fine.

Cheers!
Aaron

Re: [Postfixadmin-devel] Hooks

[Christian B. <pos...@cb...>]

# Hello,

Am Samstag, 14. November 2009 schrieb Aaron Dalton:
> I'm new to postfixadmin.  I am managing a dozen or so domains, all of
> which I wish to use with DKIM.  Having the admins manually edit text
> files listing domains and keys is a problem.  Are there any hooks I
>  can attach a script to that will manage these files for me?

I'm not really familiar with DKIM and what it needs, so I'll just give
you the list of available hooks (which can call external scripts):

# grep -B1 "CONF.*script" config.inc.php
// Parameters: (1) username (2) domain (3) maildir (4) quota
// $CONF['mailbox_postcreation_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postcreation.sh';
--
// Parameters: (1) username (2) domain (3) maildir (4) quota
// $CONF['mailbox_postedit_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postedit.sh';
--
// Parameters: (1) username (2) domain
// $CONF['mailbox_postdeletion_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postdeletion.sh';
--
// Parameters: (1) username
//$CONF['domain_postcreation_script']='sudo -u courier /usr/local/bin/postfixadmin-domain-postcreation.sh';
--
// Parameters: (1) username
// $CONF['domain_postdeletion_script']='sudo -u courier /usr/local/bin/postfixadmin-domain-postdeletion.sh';

It should be obvious when the hooks are called (and since two minutes 
config.inc.php also contains the information about the parameters that 
are handed over to the scripts ;-)

If you need other hooks, please tell us what you need.


Regards,

Christian Boltz
-- 
Nichts its gefährlicher als sich in Gefahr zu begeben. das
merkst du spätestens dann, wenn du sein erstes Posting ins
Usernetz losgelassen hast.                  [WoKo in dag°]