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

Re: [Postfixadmin-devel] missing layout for postfixadmin on web site

[J4 <ju...@kl...>]

Hi David,

# ls -l css/default.css
-rw-r--r-- 1 root root 5637 Jan  3 12:38 css/default.css
	
$CONF['theme_css'] = 'css/default.css';

Just to be sure the default.css was not the problem, I copied the
default.css from the svn I had downloaded into the htdoc location for my
postfixadmin install, but it did not change anything.

Is there anywhere else that could cause a problem with the style sheets?



On 01/18/2011 11:00 AM, David Goodwin wrote:
> I suspect you've somehow broken the stylesheet(s).
> 
> Look in config.inc.php for $CONF['theme_css'] - it should be set to something like 'css/default.css'.
> 
> 
> 
> David.
> 
> 
> On 17 Jan 2011, at 10:39, J4 wrote:
> 
>> Hi there,
>>
>>     I had postfixadmin working well, but sadly made a change last Friday and have forgotten what it was :(  The result is that postfixadmin works, but the (presumably) style sheets are not read. The web page is displayed only in ascii with URL links, but not the nice way it was afore.  
>>
>> I took a screen-shot and upload it here as it better explains what I mean:
>> http://tinypic.com/r/zn629w/7
>>
>> Does anyone know what might have caused this?
>>
>> Best regards, J.
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand 
>> malware threats, the impact they can have on your business, and how you 
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl_______________________________________________
>> Postfixadmin-devel mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
> 

Re: [Postfixadmin-devel] missing layout for postfixadmin on web site

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

I suspect you've somehow broken the stylesheet(s).

Look in config.inc.php for $CONF['theme_css'] - it should be set to something like 'css/default.css'.



David.


On 17 Jan 2011, at 10:39, J4 wrote:

> Hi there,
> 
>     I had postfixadmin working well, but sadly made a change last Friday and have forgotten what it was :(  The result is that postfixadmin works, but the (presumably) style sheets are not read. The web page is displayed only in ascii with URL links, but not the nice way it was afore.  
> 
> I took a screen-shot and upload it here as it better explains what I mean:
> http://tinypic.com/r/zn629w/7
> 
> Does anyone know what might have caused this?
> 
> Best regards, J.
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl_______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

Re: [Postfixadmin-devel] Requesting comment on a modification of vacation.pl

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

diff -u ??

David Goodwin 
Pale Purple Ltd. 
http://www.palepurple.co.uk
0845 0046746
07792 380669

On 17 Jan 2011, at 18:59, Tanstaafl <tan...@li...> wrote:

> On 2011-01-17 1:35 PM, Rudi Floren wrote:
>> Can you post a sun patch? It is better to see Your changes.
> 
> Attached is a patch, but what is a 'sun patch'?
> <my_vacation.patch>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand 
> malware threats, the impact they can have on your business, and how you 
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

Re: [Postfixadmin-devel] Requesting comment on a modification of vacation.pl

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

On 2011-01-17 3:09 PM, David Goodwin wrote:
> diff -u ??

I guess - thats what I did anyhow... ;)

> On 17 Jan 2011, at 18:59, Tanstaafl <tan...@li...> wrote:
> 
>> On 2011-01-17 1:35 PM, Rudi Floren wrote:
>>> Can you post a sun patch? It is better to see Your changes.
>>
>> Attached is a patch, but what is a 'sun patch'?
>> <my_vacation.patch>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand 
>> malware threats, the impact they can have on your business, and how you 
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Postfixadmin-devel mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

Re: [Postfixadmin-devel] Requesting comment on a modification of vacation.pl

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

On 2011-01-17 1:35 PM, Rudi Floren wrote:
> Can you post a sun patch? It is better to see Your changes.

Attached is a patch, but what is a 'sun patch'?

Re: [Postfixadmin-devel] Requesting comment on a modification of vacation.pl

[Rudi F. <rud...@go...>]

Can you post a sun patch? It is better to see Your changes.
Am 17.01.2011 18:52 schrieb "Tanstaafl" <tan...@li...>:
> Hello,
>
> After conversing with Christian on irc, I have attempted a slight
> modification of the section of vacation.pl that deals with deciding
> whether or not to send a vacatiopn response based on the headers.
>
> I am not sure at all whether this will work as I think oir expect, so
> would appreciate some comments.
>
> What I'm after is a reasonable way to add simple strings that will cause
> the vacation message to NOT be sent...
>
> Here is what I have so far:
>
>> # Take headers apart
>> $cc = '';
>> $replyto = '';
>>
>> # To Add:
>> # elsif (/^x\-assp\-spam:\s+yes/i) { $logger->debug('X-Assp-Spam: Yes
found; ignoring'); exit (0); }
>>
>> $logger->debug("Script argument SMTP recipient is : '$smtp_recipient' and
smtp_sender : '$smtp_sender'");
>> while (<STDIN>) {
>> last if (/^$/);
>> if (/^\s+(.*)/ and $lastheader) { $$lastheader .= " $1"; next; }
>> elsif (/^from:\s*(.*)\n$/i) { $from = $1; $lastheader = \$from; }
>> elsif (/^to:\s*(.*)\n$/i) { $to = $1; $lastheader = \$to; }
>> elsif (/^cc:\s*(.*)\n$/i) { $cc = $1; $lastheader = \$cc; }
>> elsif (/^reply-to:\s*(.*)\s*\n$/i) { $replyto = $1; $lastheader =
\$replyto; }
>> elsif (/^subject:\s*(.*)\n$/i) { $subject = $1; $lastheader = \$subject;
}
>> elsif (/^message-id:\s*(.*)\s*\n$/i) { $messageid = $1; $lastheader =
\$messageid; }
>> # new 'multi-string' line is for adding any string you want to test for
in any header - but be careful what you put in here
>> elsif (/^(.*):\s+(bounce\@|facebook|list-|myspace|twitter)/i) {
$logger->debug("Header matching $1: $2 found; exiting"); exit (0); }
>> elsif (/^x-spam-(flag|status):\s+yes/i) { $logger->debug("x-spam-$1: yes
found; exiting"); exit (0); }
>> # next line is a candidate for removal, since 'facebook' is included in
the new 'multi-string' line above
>> elsif (/^x-facebook-notify:/i) { $logger->debug('Mail from facebook,
ignoring'); exit(0); }
>> elsif (/^precedence:\s+(bulk|junk|list|spam)/i) {
$logger->debug("precedence: $1 found; exiting"); exit (0); }
>> elsif (/^x-loop:\s+postfix\ admin\ virtual\ vacation/i) {
$logger->debug("x-loop: postfix admin virtual vacation found; exiting");
exit (0); }
>> elsif (/^auto-submitted:\s*no/i) { next; }
>> elsif (/^auto-submitted:/i) { $logger->debug("Auto-Submitted: something
found; exiting"); exit (0); }
>> # next line is a candidate for removal, since 'bounce\@' is included in
the new 'multi-string' line above
>> elsif (/^from:\s+bounce\@/i) { $logger->debug("From-$1: found; exiting");
exit (0); }
>> # next line is a candidate for removal, since 'list-' is included in the
new 'multi-string' line above
>> elsif (/^list-(.*):/i) { $logger->debug("List-$1: found; exiting"); exit
(0); }
>> elsif (/^(x-assp-spam:\s+yes)/i) { $logger->debug("$1: $3 found;
exiting"); exit (0); }
>> elsif (/^(x-(barracuda-)?spam-status):\s+(yes)/i) { $logger->debug("$1:
$3 found; exiting"); exit (0); }
>> elsif (/^(x-dspam-result):\s+(spam|bl[ao]cklisted)/i) {
$logger->debug("$1: $2 found; exiting"); exit (0); }
>> elsif (/^(x-(anti|avas-)?virus-status):\s+(infected)/i) {
$logger->debug("$1: $3 found; exiting"); exit (0); }
>> elsif (/^(x-(avas-spam|spamtest|crm114|razor|pyzor)-status):\s+(spam)/i)
{ $logger->debug("$1: $3 found; exiting"); exit (0); }
>> elsif (/^(x-osbf-lua-score):\s+[0-9\/\.\-\+]+\s+\[([-S])\]/i) {
$logger->debug("$1: $2 found; exiting"); exit (0); }
>> else {$lastheader = "" ; }
>> }
>
> Thanks for any comments/thoughts criticism...
>
>
------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

[Postfixadmin-devel] Requesting comment on a modification of vacation.pl

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

Hello,

After conversing with Christian on irc, I have attempted a slight
modification of the section of vacation.pl that deals with deciding
whether or not to send a vacatiopn response based on the headers.

I am not sure at all whether this will work as I think oir expect, so
would appreciate some comments.

What I'm after is a reasonable way to add simple strings that will cause
the vacation message to NOT be sent...

Here is what I have so far:

> # Take headers apart
> $cc = '';
> $replyto = '';
> 
> # To Add:
> #    elsif (/^x\-assp\-spam:\s+yes/i) { $logger->debug('X-Assp-Spam: Yes found; ignoring'); exit (0); }
> 
> $logger->debug("Script argument SMTP recipient is : '$smtp_recipient' and smtp_sender : '$smtp_sender'");
> while (<STDIN>) {
>     last if (/^$/);
>     if (/^\s+(.*)/ and $lastheader) { $$lastheader .= " $1"; next; }
>     elsif (/^from:\s*(.*)\n$/i) { $from = $1; $lastheader = \$from; }
>     elsif (/^to:\s*(.*)\n$/i) { $to = $1; $lastheader = \$to; }
>     elsif (/^cc:\s*(.*)\n$/i) { $cc = $1; $lastheader = \$cc; }
>     elsif (/^reply-to:\s*(.*)\s*\n$/i) { $replyto = $1; $lastheader = \$replyto; }
>     elsif (/^subject:\s*(.*)\n$/i) { $subject = $1; $lastheader = \$subject; }
>     elsif (/^message-id:\s*(.*)\s*\n$/i) { $messageid = $1; $lastheader = \$messageid; }
> # new 'multi-string' line is for adding any string you want to test for in any header - but be careful what you put in here
>     elsif (/^(.*):\s+(bounce\@|facebook|list-|myspace|twitter)/i) { $logger->debug("Header matching $1: $2 found; exiting"); exit (0); }
>     elsif (/^x-spam-(flag|status):\s+yes/i) { $logger->debug("x-spam-$1: yes found; exiting"); exit (0); }
> # next line is a candidate for removal, since 'facebook' is included in the new 'multi-string' line above
>     elsif (/^x-facebook-notify:/i) { $logger->debug('Mail from facebook, ignoring'); exit(0); }
>     elsif (/^precedence:\s+(bulk|junk|list|spam)/i) { $logger->debug("precedence: $1 found; exiting"); exit (0); }
>     elsif (/^x-loop:\s+postfix\ admin\ virtual\ vacation/i) { $logger->debug("x-loop: postfix admin virtual vacation found; exiting"); exit (0); }
>     elsif (/^auto-submitted:\s*no/i) { next; }
>     elsif (/^auto-submitted:/i) { $logger->debug("Auto-Submitted: something found; exiting"); exit (0); }
> # next line is a candidate for removal, since 'bounce\@' is included in the new 'multi-string' line above
>     elsif (/^from:\s+bounce\@/i) { $logger->debug("From-$1: found; exiting"); exit (0); }
> # next line is a candidate for removal, since 'list-' is included in the new 'multi-string' line above
>     elsif (/^list-(.*):/i) { $logger->debug("List-$1: found; exiting"); exit (0); }
>     elsif (/^(x-assp-spam:\s+yes)/i) { $logger->debug("$1: $3 found; exiting"); exit (0); }
>     elsif (/^(x-(barracuda-)?spam-status):\s+(yes)/i) { $logger->debug("$1: $3 found; exiting"); exit (0); }
>     elsif (/^(x-dspam-result):\s+(spam|bl[ao]cklisted)/i) { $logger->debug("$1: $2 found; exiting"); exit (0); }
>     elsif (/^(x-(anti|avas-)?virus-status):\s+(infected)/i) { $logger->debug("$1: $3 found; exiting"); exit (0); }
>     elsif (/^(x-(avas-spam|spamtest|crm114|razor|pyzor)-status):\s+(spam)/i) { $logger->debug("$1: $3 found; exiting"); exit (0); }
>     elsif (/^(x-osbf-lua-score):\s+[0-9\/\.\-\+]+\s+\[([-S])\]/i) { $logger->debug("$1: $2 found; exiting"); exit (0); }
>     else {$lastheader = "" ; }
> }

Thanks for any comments/thoughts criticism...

[Postfixadmin-devel] missing layout for postfixadmin on web site

[J4 <ju...@kl...>]

Hi there,

    I had postfixadmin working well, but sadly made a change last Friday
and have forgotten what it was :(  The result is that postfixadmin
works, but the (presumably) style sheets are not read. The web page is
displayed only in ascii with URL links, but not the nice way it was afore. 

I took a screen-shot and upload it here as it better explains what I mean:
http://tinypic.com/r/zn629w/7

Does anyone know what might have caused this?

Best regards, J.

Re: [Postfixadmin-devel] postfixadmin-cli deb where ?

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

Hello,

Am Freitag, 14. Januar 2011 schrieb Robert Schetterer:
> Am 14.01.2011 15:33, schrieb Robert Schetterer:

> > /postfixadmin-cli  domain view domain.org

> > PHP Fatal error:  Class 'DomainHandler' not found in
> > /usr/share/postfixadmin/scripts/shells/domain.php on line 332

> sorry for the noise, i see you have to use the whole trunk for use
> not for mixed use with current stable

Yes, the classes are in a directory outside of "scripts/" because we 
use/plan to use[1] them for the web interface also to avoid duplicate 
code. This means you need the complete tree, not just the scripts/ 
directory.

However, you can use the 2.3.x web interface and the CLI from SVN at the 
same time - but if you want to beta-test the new web interface, I won't 
object ;-)


Regards,

Christian Boltz

[1] users/* and the XMLRPC interface already use the classes, the admin
    part doesn't use them yet
-- 
Wenn man keine Vögel mag, ist es völlig in Ordnung, mit Kanonen auf
Spatzen zu schiessen.                         [Ratti in suse-linux]

Re: [Postfixadmin-devel] postfixadmin-cli deb where ?

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

Am 14.01.2011 15:33, schrieb Robert Schetterer:
> Am 14.01.2011 13:41, schrieb Christian Boltz:
>> Hello,
>>
>> Am Freitag, 14. Januar 2011 schrieb Robert Schetterer:
>>> http://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=Po
>>> stfixadmin-CLI
>>>
>>> talks about postfixadmin-cli deb package, wher can i download it
>>> the normal source files and deb packs seems not to inlude
>>> postfixadmin-cli
>>
>> At the moment it's only available in SVN trunk. You can check it out 
>> with:
>>
>> svn co 
>> https://postfixadmin.svn.sourceforge.net/svnroot/postfixadmin/trunk
>>
>> Let the script explain its usage itsself: ;-)
>>
>> cd [where your SVN checkout is]/scripts
>> ./postfixadmin-cli alias help
>> ./postfixadmin-cli user help # hmmm, should we rename that to "mailbox"?
>> ./postfixadmin-cli domain help
>>
>>
>> Regards,
>>
>> Christian Boltz
> 
> thx Christian,
> using on ubuntu server lucid 64
> 
> /postfixadmin-cli  domain view domain.org
> 
> Welcome to Postfixadmin-CLI v0.2
> ---------------------------------------------------------------
> Path: /usr/share/postfixadmin
> ---------------------------------------------------------------
> PHP Fatal error:  Class 'DomainHandler' not found in
> /usr/share/postfixadmin/scripts/shells/domain.php on line 332
> 
> Fatal error: Class 'DomainHandler' not found in
> /usr/share/postfixadmin/scripts/shells/domain.php on line 332
> 
> are there additional depencies to solve ?

sorry for the noise, i see you have to use the whole trunk for use not
for mixed use with current stable


-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Postfixadmin-devel] postfixadmin-cli deb where ?

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

Am 14.01.2011 13:41, schrieb Christian Boltz:
> Hello,
> 
> Am Freitag, 14. Januar 2011 schrieb Robert Schetterer:
>> http://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=Po
>> stfixadmin-CLI
>>
>> talks about postfixadmin-cli deb package, wher can i download it
>> the normal source files and deb packs seems not to inlude
>> postfixadmin-cli
> 
> At the moment it's only available in SVN trunk. You can check it out 
> with:
> 
> svn co 
> https://postfixadmin.svn.sourceforge.net/svnroot/postfixadmin/trunk
> 
> Let the script explain its usage itsself: ;-)
> 
> cd [where your SVN checkout is]/scripts
> ./postfixadmin-cli alias help
> ./postfixadmin-cli user help # hmmm, should we rename that to "mailbox"?
> ./postfixadmin-cli domain help
> 
> 
> Regards,
> 
> Christian Boltz

thx Christian,
using on ubuntu server lucid 64

/postfixadmin-cli  domain view domain.org

Welcome to Postfixadmin-CLI v0.2
---------------------------------------------------------------
Path: /usr/share/postfixadmin
---------------------------------------------------------------
PHP Fatal error:  Class 'DomainHandler' not found in
/usr/share/postfixadmin/scripts/shells/domain.php on line 332

Fatal error: Class 'DomainHandler' not found in
/usr/share/postfixadmin/scripts/shells/domain.php on line 332

are there additional depencies to solve ?
-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Postfixadmin-devel] postfixadmin-cli deb where ?

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

Hello,

Am Freitag, 14. Januar 2011 schrieb Robert Schetterer:
> http://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=Po
> stfixadmin-CLI
> 
> talks about postfixadmin-cli deb package, wher can i download it
> the normal source files and deb packs seems not to inlude
> postfixadmin-cli

At the moment it's only available in SVN trunk. You can check it out 
with:

svn co 
https://postfixadmin.svn.sourceforge.net/svnroot/postfixadmin/trunk

Let the script explain its usage itsself: ;-)

cd [where your SVN checkout is]/scripts
./postfixadmin-cli alias help
./postfixadmin-cli user help # hmmm, should we rename that to "mailbox"?
./postfixadmin-cli domain help


Regards,

Christian Boltz
-- 
Aus technischen Grunden befindet sich die Signatur
auf der Rückseite dieser Mail.

[Postfixadmin-devel] postfixadmin-cli deb where ?

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

Hi @ll,


http://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=Postfixadmin-CLI

talks about postfixadmin-cli deb package, wher can i download it
the normal source files and deb packs seems not to inlude
postfixadmin-cli
-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria

Re: [Postfixadmin-devel] Integration with MLM?

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

Hello,

Am Dienstag, 11. Januar 2011 schrieb Aaron:
> On 1/11/2011 4:55 AM, Christian Boltz wrote:
> > Am Dienstag, 11. Januar 2011 schrieb Aaron:
> >> Here's a dumb question, what about integrating some kind of post
> >> hook  when using option #1?  ie, some kind of pluggable script
> >> spot where you could pass something like
> >> 
> >> external-command.sh [add|remove|modify] aliasname ?
> > 
> > I don't see a real need for script hooks when aliases are created,
> > modified or deleted. If you have a usecase, tell me ;-)
> 
> Other than handling potential MLM integration?  I can't think of
> another use currently, no. 

I'm afraid I don't get your point (yet) - how would you handle this? 
Creating a mailinglist is much more than just adding an alias...

> There may be additional cases where
> you'd pipe an alias out to an external command for handling, but I
> haven't run across them yet.

You don't even *want* to control aliases with a pipe as target in the 
web interface - the security risk is too big. (What about piping a mail 
to "| rm -rf /"? ;-)  (and it's forbidden for databases in postfix 
anyways - pipe targets have to be in text-based maps.)

[post-* scripts]
> That's kind of what I was thinking would be right for aliases.
> 
> Creating the aliases in postfixadmin first, then running whatever
> additional commands manually isn't an impossible task, but I have to
> admit being able to do everything in one place has it's benefits.  I
> can see how it would add complexity, you'd certainly need to add
> something like "enable external script" as an unselected checkbox to
> avoid running the external hook on every alias transaction.
> 
> Would it be difficult to extend the existing script options to
> include a set for aliases ? (and make it selectable on the alias
> page?)

Difficult is relative ;-) but I don't see how adding an alias can be 
used to create a mailinglist - it misses some important information like 
the list owner's mail address, admin password for the mailinglist etc.

OTOH, creating a mailinglist is a totally different task and unrelated 
to creating an alias (creating an alias is only a very small part of 
creating a mailinglist), so I'd prefer to have a separate page/script to 
do that.

At the risk of disappointing you: I have several things on my TODO list 
that are more important, therefore I won't have time to work on this. 
However, if you come up with a good solution, we'll probably accept your 
patch ;-) (And, BTW, which MLM are you talking about?)


Regards,

Christian Boltz
-- 
    Trojanisches Pferd
Zum Thema "Trojaner" muss doch vielleicht mal jemand sagen, dass ein
Trojanisches Pferd kein Trojaner ist. Im Gegenteil. Sein Bauch ist
nämlich mit Griechen gefüllt, die dann die Stadttore öffnen. Wäre das
trojanische Pferd ein Trojaner, wäre es völlig ungefährlich.
[Werner Hintze]

Re: [Postfixadmin-devel] Integration with MLM?

[Aaron <ar...@gr...>]

On 1/11/2011 4:55 AM, Christian Boltz wrote:
> Hello,
>
> (Was it intentional to reply off-list? If not, feel free to reply to
> this mail on the list.)
>
Indeed, it wasn't intentional, sorry about that.
> Am Dienstag, 11. Januar 2011 schrieb Aaron:
>> Here's a dumb question, what about integrating some kind of post
>> hook  when using option #1?  ie, some kind of pluggable script spot
>> where you could pass something like
>>
>> external-command.sh [add|remove|modify] aliasname ?
> I don't see a real need for script hooks when aliases are created,
> modified or deleted. If you have a usecase, tell me ;-)
>
Other than handling potential MLM integration?  I can't think of another 
use currently, no.  There may be additional cases where you'd pipe an 
alias out to an external command for handling, but I haven't run across 
them yet.
>> I realize that may be a slippery slope, but I could see a few places
>> where having a post-action script might have value (like delete
>> having  an option to tgz the user's folder, etc).
> We have that already (for mailboxes and domains), however it's disabled
> in the default config.
>
> grep 'CONF.*script' config.inc.php
> // $CONF['mailbox_postcreation_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postcreation.sh';
> // $CONF['mailbox_postedit_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postedit.sh';
> // $CONF['mailbox_postdeletion_script']='sudo -u courier /usr/local/bin/postfixadmin-mailbox-postdeletion.sh';
> // $CONF['domain_postcreation_script']='sudo -u courier /usr/local/bin/postfixadmin-domain-postcreation.sh';
> // $CONF['domain_postdeletion_script']='sudo -u courier /usr/local/bin/postfixadmin-domain-postdeletion.sh';
>
That's kind of what I was thinking would be right for aliases.

Creating the aliases in postfixadmin first, then running whatever 
additional commands manually isn't an impossible task, but I have to 
admit being able to do everything in one place has it's benefits.  I can 
see how it would add complexity, you'd certainly need to add something 
like "enable external script" as an unselected checkbox to avoid running 
the external hook on every alias transaction.

Would it be difficult to extend the existing script options to include a 
set for aliases ? (and make it selectable on the alias page?)

Thank you for your time, regardless.

Aaron

Re: [Postfixadmin-devel] Integration with MLM?

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

Hello,

Am Saturday 08 January 2011 schrieb Geoff Shang:
> On Sat, 8 Jan 2011, Christian Boltz wrote:
...
> > - add hash:/var/lib/mailman/data/aliases to alias_maps
> 
> This path is used by the Debian package at least, but other
> installations (including from source) may place this file elsewhere.

openSUSE uses the same path, therefore I'd say it's quite common.
People who installed mailman from source will probably know they might 
have to adopt the path ;-)

[...]
> This part isn't necessary if you use Mailman's in-built postfix
> virtual domain support.
> 
> Put your virtual domain in POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py

Exactly that is what I want to avoid - I run mailinglists on lots of 
domains, and adding them in mm_cfg.py would mean lots of work. 
Additionally there's another admin on the server who needs to create 
mailinglists, but shouldn't need to edit config files.

I have a simple script to add a mailinglist in the way I described - 
that's easy enough for him. If he would need to edit mm_cfg.py all the 
time, I would probably have to spend some time on phone-supporting him 
;-)

> and add hash:/var/lib/mailman/data/virtual-mailman to
> virtual_alias_maps in main.cf (the same applies here about the
> location of this file).

That brings up the next "problem" - the aliases aren't visible in 
PostfixAdmin. So a domain admin could create an alias with the same name 
as a mailinglist - needless to say that either the mailinglist or the 
alias wouldn't work afterwards. (The risk that a domain admin deletes 
one of the mailman aliases isn't that big IMHO.)

> This issue is discussed further in the Mailman installation guide at
> http://list.org/./mailman-install/node12.html

I'd say the exact page is
http://list.org/mailman-install/postfix-virtual.html

I have updated the wiki page 
https://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=Mailman_integration
In detail, I have added a link for the mailman virtual domain setup and 
added pros and cons of every method.

If you think the page needs more changes, just tell me. Or, easier, ask 
for write access to the wiki as described on 
https://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=About
(sorry for the paperworks, but that's how SF has implemented it...)


Regards,

Christian Boltz
-- 
>Gibt es hier in dieser Liste eigentlich ausser mir noch jemanden ??
Nein, aber es laufen einige Robots, die Traffic vortäuschen. Ich bin
auch einer davon.
[Tobias Korb und Thorsten Haude in suse-programming]

Re: [Postfixadmin-devel] Integration with MLM?

[Geoff S. <ge...@Qu...>]

On Sat, 8 Jan 2011, Christian Boltz wrote:

> However, I can tell you how I integrate mailman - it's quite simple and
> works ;-)
>
> a) /etc/postfix/main.cf
> - add a domain like lists.yourdomain.com in mydestination

This isn't strictly necessary.  If you want to just use yourdomain.com you 
can set it up as a virtual mailbox domain.

> - add hash:/var/lib/mailman/data/aliases to alias_maps

This path is used by the Debian package at least, but other installations 
(including from source) may place this file elsewhere.

> - restart postfix
>
> b) create the list in mailman (on the lists.yourdomain.com domain)
>
> c) add redirects in postfixadmin:
> - lis...@yo... -> lis...@li...
> - lis...@yo... ->
>      lis...@li...
> - [same for the other mailman aliases]

This part isn't necessary if you use Mailman's in-built postfix virtual 
domain support.

Put your virtual domain in POSTFIX_STYLE_VIRTUAL_DOMAINS in mm_cfg.py and 
add hash:/var/lib/mailman/data/virtual-mailman to virtual_alias_maps in 
main.cf (the same applies here about the location of this file).

The virtual-mailman file will be generated by Mailman and can take the 
place of the entries in postfixadmin.

This issue is discussed further in the Mailman installation guide at 
http://list.org/./mailman-install/node12.html

As you can gather, there's more than one way to slice this, but IMHO 
postfixadmin doesn't really add anything to the process.

Geoff.

Re: [Postfixadmin-devel] Integration with MLM?

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

Hello,

Am Friday 07 January 2011 schrieb Aaron:
> I come from a primarily qmail background, and that's one thing that's
> stopped me from doing a full conversion -- I like Postfixadmin, but I
> can't imagine not having MLM integrated at the top level, especially
> if someone less technical might be doing management work.
> 
> I don't know if anyone's asked this before, but do you have a guide
> for, or plans to do integration with any of the mailing list
> manager?

We don't have a "direct" integration of any mailinglist manager, and 
also (at least I) don't have plans to do so.

There is also the limitation that virtual aliases in a database can't 
redirect to a pipe instead of a mail address (security restriction by 
postfix).

However, I can tell you how I integrate mailman - it's quite simple and 
works ;-)

a) /etc/postfix/main.cf
- add a domain like lists.yourdomain.com in mydestination
- add hash:/var/lib/mailman/data/aliases to alias_maps
- restart postfix

b) create the list in mailman (on the lists.yourdomain.com domain)

c) add redirects in postfixadmin:
- lis...@yo... -> lis...@li...
- lis...@yo... -> 
      lis...@li...
- [same for the other mailman aliases]

I can send you a script that does part c) if you want - however it is 
more or less becoming obsolete with the PostfixAdmin command line 
interface we have in SVN trunk.

BTW: I just put a similar text to the wiki for future reference:
https://sourceforge.net/apps/mediawiki/postfixadmin/index.php?title=Mailman_integration


Regarding more integration in postfixadmin: Mailman doesn't use MySQL 
databases, so it would be *lots* of work to integrate it.

I have no idea about other MLMs because mailman does all I need ;-)


Regards,

Christian Boltz
-- 
Ich wollte auf etwas anderes hinaus. Normale Anwender loggen sich doch
i.d.R.  nicht in irgendwelche Shells ein. Heutzutage muss doch alles
bunt sein. Denn nur was bunt ist, ist professionell. Das ist doch die
gängige Meinung der Schlipse. Seufz. [Jürgen Knelangen in suse-linux]

Re: [Postfixadmin-devel] Integration with MLM?

[Geoff S. <ge...@Qu...>]

On Fri, 7 Jan 2011, Aaron wrote:

> I don't know if anyone's asked this before, but do you have a guide for,
> or plans to do integration with any of the mailing list manager?

IMHO, an MTA and an MLM are two entirely different beasts and there's 
little to be gained by trying to integrate them.

We're quite happily running PFA and Gnu Mailman side-by-side with no 
problems whatsoever.

Full-on mail server administration is not something for the inexperienced, 
and really neither is list server administration.   If you're simply 
talking about those who would use the web interfaces, they shouldn't have 
to worry about the underlying details.

Geoff.

[Postfixadmin-devel] Integration with MLM?

[Aaron <ar...@gr...>]

I come from a primarily qmail background, and that's one thing that's 
stopped me from doing a full conversion -- I like Postfixadmin, but I 
can't imagine not having MLM integrated at the top level, especially if 
someone less technical might be doing management work.

I don't know if anyone's asked this before, but do you have a guide for, 
or plans to do integration with any of the mailing list manager?

Thanks!

Re: [Postfixadmin-devel] Email account created via postfixadmin not recognised by imap (dovecot)

[J4 <ju...@kl...>]

On 01/07/2011 04:07 PM, Valkum wrote:
> The error says that in where clause second part of your query the column
> email non exist.
> 
> check it theres still email.
> Am 07.01.2011 15:46, schrieb ju...@kl...:
>>  On Fri, 07 Jan 2011 14:32:50 +0100, "ju...@kl..." 
>>  <ju...@kl...> wrote:
>>> On Fri, 7 Jan 2011 14:02:12 +0100, Christian Boltz
>>> <pos...@cb...> wrote:
>>>> Am Friday 07 January 2011 schrieb J4:
>>>>>     I had postfixadmin working, and a few days I created an account
>>>>> in it (1234@xxxinfo).  The account could login, send email & so on.
>>>>> Today, I added another test account, but the account would not log
>>>>> in.
>>>>> I compared the entries for each account in mysql and noticed that
>>>>> these differed:
>>>>>
>>>>> mysql> select * from mailbox;
>>>>>
>>>>> | 12...@xx...   | $1111111111111 | S.L TEST         | ...
>>>>> | te...@xx... | $11111111111111 | test Test     | xxx.info/test/ 
>>>>> ...
>>>>> mysql> select * from virtual_users;
>>>>> |  1 |         1 | xxxx | 12...@xx... |
>>>>> mysql> select * from virtual_aliases;
>>>>> |  1 |         1 | 12...@xx... | 12...@xx... |
>>>>> |  2 |         1 | 12...@xx... | fre...@kl...     |
>>>> Seeing your table names, I'd say you must be zed1 from IRC ;-)
>>> Hi Christian ,
>>> Yep. I'm still having mix-up problems.
>>>
>>>> It looks like you still suffer from the mixup of
>>>> a) the HOWTO you found somewhere on the web (virtual_* tables)
>>>> b) postfixadmin's tables (mailbox, alias etc. tables)
>>>>
>>>> I'm quite sure that your dovecot still uses the "virtual_users" 
>>>> table -
>>>> change it to use the "mailbox" table and it should work.
>>> Changed the dovecot file dovecot-sql.conf to read:
>>> driver = mysql
>>> connect = host=127.0.0.1 dbname=xxxx user=xxxx password=xxxxx
>>> default_pass_scheme = PLAIN-MD5
>>> password_query = SELECT email as user, password FROM mailbox WHERE
>>> email='%u';
>>> ###password_query = SELECT email as user, password FROM virtual_users
>>> WHERE email='%u';
>>>
>>>
>>> I restarted dovecot, and now no-one could log in, so I deleted all
>>> accounts and domains via postfixadmin, and added one again, but the
>>> IMAP login still failed.  Luckily there was a useful error messag:e
>>> Jan  7 14:20:24 logout dovecot: auth-worker(default):
>>> sql(te...@xx...,127.0.0.1): Password query failed: Unknown column
>>> 'email' in 'field list'
>>>
>>> Is the above query contained in the dovecot-sql.conf correct?
>>>
>>> I shall drop the virtual* tables.
>>
>>
>>
>>  There is something wrong with the mailbox table.
>>
>>  mysql> select email from mailbox;
>>  ERROR 1054 (42S22): Unknown column 'email' in 'field list'
>>  mysql> describe mailbox;
>>  +------------+--------------+------+-----+---------------------+-------+
>>  | Field      | Type         | Null | Key | Default             | Extra 
>>  |
>>  +------------+--------------+------+-----+---------------------+-------+
>>  | username   | varchar(255) | NO   | PRI | NULL                |       
>>  |
>>  | password   | varchar(255) | NO   |     | NULL                |       
>>  |
>>  | name       | varchar(255) | NO   |     | NULL                |       
>>  |
>>  | maildir    | varchar(255) | NO   |     | NULL                |       
>>  |
>>  | quota      | bigint(20)   | NO   |     | 0                   |       
>>  |
>>  | local_part | varchar(255) | NO   |     | NULL                |       
>>  |
>>  | domain     | varchar(255) | NO   | MUL | NULL                |       
>>  |
>>  | created    | datetime     | NO   |     | 0000-00-00 00:00:00 |       
>>  |
>>  | modified   | datetime     | NO   |     | 0000-00-00 00:00:00 |       
>>  |
>>  | active     | tinyint(1)   | NO   |     | 1                   |       
>>  |
>>  +------------+--------------+------+-----+---------------------+-------+
>>  10 rows in set (0.00 sec)
>>
>>  I thought that maybe query should have been:
>>
>>  password_query = SELECT username as user, password FROM mailbox WHERE 
>>  email='%u';
>>
>>  mysql> select username as user,password from mailbox;
>>  +------------------------+------------------------------------+
>>  | user                   | password                           |
>>  +------------------------+------------------------------------+
>>  | te...@xx...          | $1$xxxxxxx |
>>  +------------------------+------------------------------------+
>>
>>  ...But this did only gave the message:
>>  Jan  7 15:36:49 logout dovecot: auth-worker(default): 
>>  sql(te...@xx...,127.0.0.1): Password query failed: Unknown column 
>>  'email' in 'where clause'
>>
>>


Problem solved :)  Thank-you.
I had used the wrong template for mySQL. I should have used:
dovecot-mysql.conf

when I had used dovecot-sql.conf

It all seems to work right now.


Many thanks again for your advise.

J

Re: [Postfixadmin-devel] Email account created via postfixadmin not recognised by imap (dovecot)

[Rudi F. <rud...@go...>]

Check the mysql table and our documentation.
There is no column called email. It is called username.
Am 07.01.2011 15:31 schrieb "ju...@kl..." <ju...@kl...>:
> On Fri, 7 Jan 2011 14:02:12 +0100, Christian Boltz
> <pos...@cb...> wrote:
>> Am Friday 07 January 2011 schrieb J4:
>>> I had postfixadmin working, and a few days I created an account
>>> in it (1234@xxxinfo). The account could login, send email & so on.
>>> Today, I added another test account, but the account would not log
>>> in.
>>
>>> I compared the entries for each account in mysql and noticed that
>>> these differed:
>>>
>>> mysql> select * from mailbox;
>>>
>>> | 12...@xx... | $1111111111111 | S.L TEST | ...
>>> | te...@xx... | $11111111111111 | test Test | xxx.info/test/
>>> ...
>>
>>> mysql> select * from virtual_users;
>>
>>> | 1 | 1 | xxxx | 12...@xx... |
>>
>>> mysql> select * from virtual_aliases;
>>
>>> | 1 | 1 | 12...@xx... | 12...@xx... |
>>> | 2 | 1 | 12...@xx... | fre...@kl... |
>>
>> Seeing your table names, I'd say you must be zed1 from IRC ;-)
>
> Hi Christian ,
> Yep. I'm still having mix-up problems.
>
>>
>> It looks like you still suffer from the mixup of
>> a) the HOWTO you found somewhere on the web (virtual_* tables)
>> b) postfixadmin's tables (mailbox, alias etc. tables)
>>
>> I'm quite sure that your dovecot still uses the "virtual_users" table
>> -
>> change it to use the "mailbox" table and it should work.
>
> Changed the dovecot file dovecot-sql.conf to read:
> driver = mysql
> connect = host=127.0.0.1 dbname=xxxx user=xxxx password=xxxxx
> default_pass_scheme = PLAIN-MD5
> password_query = SELECT email as user, password FROM mailbox WHERE
> email='%u';
> ###password_query = SELECT email as user, password FROM virtual_users
> WHERE email='%u';
>
>
> I restarted dovecot, and now no-one could log in, so I deleted all
> accounts and domains via postfixadmin, and added one again, but the IMAP
> login still failed. Luckily there was a useful error messag:e
> Jan 7 14:20:24 logout dovecot: auth-worker(default):
> sql(te...@xx...,127.0.0.1): Password query failed: Unknown column
> 'email' in 'field list'
>
> Is the above query contained in the dovecot-sql.conf correct?
>
> I shall drop the virtual* tables.
>
> J.
>
>
>>
>> You should also remove the virtual_* tables to avoid future confusion
>> (a backup never hurts, but you probably won't need it ;-)
>> Postfixadmin does not use any virtual_* tables (except if you have
>> defined custom table names or a database prefix in the config, but
>> that's something you would know.)
>>
>> If something breaks ofter removing the virtual_* tables, you most
>> probably have to fix the configuration of the breaking service.
>>
>>> These errors keep popping up in the apache error.log, and I do not
>>> know whether these are related to the problem.
>>> [Fri Jan 07 11:36:29 2011] [error] [client 11.11.11.11] PHP Notice:
>>> Undefined index: flash in
>>>
>>> /www/postfixadmin/templates_c/0d1a714f76f647ac5097fa38ac2b35080d18dd1
>>> 2.file.header.tpl.php on line 54, referer: [...]
>>
>> Those errors are unrelated and only show that our migration to smarty
>> is
>> still not perfect ;-) But that are minor things, nothing that breaks
>> functionality.
>>
>>
>> Regards,
>>
>> Christian Boltz
>> --
>> Mmh. Nachdem alle hier anscheinend Mutt verwenden habe ich mal einen
>> Blick draufgeworfen. Dafür braucht man entweder ein Studium
>> (Schwerpunkt
>> Mutt) oder viel Zeit. Mal sehen was ich zuerst habe.
>> [Christian Wunderlich in suse-linux]
>>
>>
>>
------------------------------------------------------------------------------
>> Gaining the trust of online customers is vital for the success of any
>> company
>> that requires sensitive data to be transmitted over the Web. Learn
>> how to
>> best implement a security strategy that keeps consumers' information
>> secure
>> and instills the confidence they need to proceed with transactions.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Postfixadmin-devel mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>
> --
> NEOCRON: Cyberpunk FPS MMORG http://www.neocron.com
>
>
------------------------------------------------------------------------------
> Gaining the trust of online customers is vital for the success of any
company
> that requires sensitive data to be transmitted over the Web. Learn how to
> best implement a security strategy that keeps consumers' information
secure
> and instills the confidence they need to proceed with transactions.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

Re: [Postfixadmin-devel] Email account created via postfixadmin not recognised by imap (dovecot)

[<ju...@kl...>]

 On Fri, 07 Jan 2011 14:32:50 +0100, "ju...@kl..." 
 <ju...@kl...> wrote:
> On Fri, 7 Jan 2011 14:02:12 +0100, Christian Boltz
> <pos...@cb...> wrote:
>> Am Friday 07 January 2011 schrieb J4:
>>>     I had postfixadmin working, and a few days I created an account
>>> in it (1234@xxxinfo).  The account could login, send email & so on.
>>> Today, I added another test account, but the account would not log
>>> in.
>>
>>> I compared the entries for each account in mysql and noticed that
>>> these differed:
>>>
>>> mysql> select * from mailbox;
>>>
>>> | 12...@xx...   | $1111111111111 | S.L TEST         | ...
>>> | te...@xx... | $11111111111111 | test Test     | xxx.info/test/ 
>>> ...
>>
>>> mysql> select * from virtual_users;
>>
>>> |  1 |         1 | xxxx | 12...@xx... |
>>
>>> mysql> select * from virtual_aliases;
>>
>>> |  1 |         1 | 12...@xx... | 12...@xx... |
>>> |  2 |         1 | 12...@xx... | fre...@kl...     |
>>
>> Seeing your table names, I'd say you must be zed1 from IRC ;-)
>
> Hi Christian ,
> Yep. I'm still having mix-up problems.
>
>>
>> It looks like you still suffer from the mixup of
>> a) the HOWTO you found somewhere on the web (virtual_* tables)
>> b) postfixadmin's tables (mailbox, alias etc. tables)
>>
>> I'm quite sure that your dovecot still uses the "virtual_users" 
>> table -
>> change it to use the "mailbox" table and it should work.
>
> Changed the dovecot file dovecot-sql.conf to read:
> driver = mysql
> connect = host=127.0.0.1 dbname=xxxx user=xxxx password=xxxxx
> default_pass_scheme = PLAIN-MD5
> password_query = SELECT email as user, password FROM mailbox WHERE
> email='%u';
> ###password_query = SELECT email as user, password FROM virtual_users
> WHERE email='%u';
>
>
> I restarted dovecot, and now no-one could log in, so I deleted all
> accounts and domains via postfixadmin, and added one again, but the
> IMAP login still failed.  Luckily there was a useful error messag:e
> Jan  7 14:20:24 logout dovecot: auth-worker(default):
> sql(te...@xx...,127.0.0.1): Password query failed: Unknown column
> 'email' in 'field list'
>
> Is the above query contained in the dovecot-sql.conf correct?
>
> I shall drop the virtual* tables.




 There is something wrong with the mailbox table.

 mysql> select email from mailbox;
 ERROR 1054 (42S22): Unknown column 'email' in 'field list'
 mysql> describe mailbox;
 +------------+--------------+------+-----+---------------------+-------+
 | Field      | Type         | Null | Key | Default             | Extra 
 |
 +------------+--------------+------+-----+---------------------+-------+
 | username   | varchar(255) | NO   | PRI | NULL                |       
 |
 | password   | varchar(255) | NO   |     | NULL                |       
 |
 | name       | varchar(255) | NO   |     | NULL                |       
 |
 | maildir    | varchar(255) | NO   |     | NULL                |       
 |
 | quota      | bigint(20)   | NO   |     | 0                   |       
 |
 | local_part | varchar(255) | NO   |     | NULL                |       
 |
 | domain     | varchar(255) | NO   | MUL | NULL                |       
 |
 | created    | datetime     | NO   |     | 0000-00-00 00:00:00 |       
 |
 | modified   | datetime     | NO   |     | 0000-00-00 00:00:00 |       
 |
 | active     | tinyint(1)   | NO   |     | 1                   |       
 |
 +------------+--------------+------+-----+---------------------+-------+
 10 rows in set (0.00 sec)

 I thought that maybe query should have been:

 password_query = SELECT username as user, password FROM mailbox WHERE 
 email='%u';

 mysql> select username as user,password from mailbox;
 +------------------------+------------------------------------+
 | user                   | password                           |
 +------------------------+------------------------------------+
 | te...@xx...          | $1$xxxxxxx |
 +------------------------+------------------------------------+

 ...But this did only gave the message:
 Jan  7 15:36:49 logout dovecot: auth-worker(default): 
 sql(te...@xx...,127.0.0.1): Password query failed: Unknown column 
 'email' in 'where clause'

Re: [Postfixadmin-devel] Email account created via postfixadmin not recognised by imap (dovecot)

[<ju...@kl...>]

 On Fri, 7 Jan 2011 14:02:12 +0100, Christian Boltz 
 <pos...@cb...> wrote:
> Am Friday 07 January 2011 schrieb J4:
>>     I had postfixadmin working, and a few days I created an account
>> in it (1234@xxxinfo).  The account could login, send email & so on.
>> Today, I added another test account, but the account would not log
>> in.
>
>> I compared the entries for each account in mysql and noticed that
>> these differed:
>>
>> mysql> select * from mailbox;
>>
>> | 12...@xx...   | $1111111111111 | S.L TEST         | ...
>> | te...@xx... | $11111111111111 | test Test     | xxx.info/test/ 
>> ...
>
>> mysql> select * from virtual_users;
>
>> |  1 |         1 | xxxx | 12...@xx... |
>
>> mysql> select * from virtual_aliases;
>
>> |  1 |         1 | 12...@xx... | 12...@xx... |
>> |  2 |         1 | 12...@xx... | fre...@kl...     |
>
> Seeing your table names, I'd say you must be zed1 from IRC ;-)

 Hi Christian ,
 Yep. I'm still having mix-up problems.

>
> It looks like you still suffer from the mixup of
> a) the HOWTO you found somewhere on the web (virtual_* tables)
> b) postfixadmin's tables (mailbox, alias etc. tables)
>
> I'm quite sure that your dovecot still uses the "virtual_users" table 
> -
> change it to use the "mailbox" table and it should work.

 Changed the dovecot file dovecot-sql.conf to read:
 driver = mysql
 connect = host=127.0.0.1 dbname=xxxx user=xxxx password=xxxxx
 default_pass_scheme = PLAIN-MD5
 password_query = SELECT email as user, password FROM mailbox WHERE 
 email='%u';
 ###password_query = SELECT email as user, password FROM virtual_users 
 WHERE email='%u';


 I restarted dovecot, and now no-one could log in, so I deleted all 
 accounts and domains via postfixadmin, and added one again, but the IMAP 
 login still failed.  Luckily there was a useful error messag:e
 Jan  7 14:20:24 logout dovecot: auth-worker(default): 
 sql(te...@xx...,127.0.0.1): Password query failed: Unknown column 
 'email' in 'field list'

 Is the above query contained in the dovecot-sql.conf correct?

 I shall drop the virtual* tables.

 J.


>
> You should also remove the virtual_* tables to avoid future confusion
> (a backup never hurts, but you probably won't need it ;-)
> Postfixadmin does not use any virtual_* tables (except if you have
> defined custom table names or a database prefix in the config, but
> that's something you would know.)
>
> If something breaks ofter removing the virtual_* tables, you most
> probably have to fix the configuration of the breaking service.
>
>> These errors keep popping up in the apache error.log, and I do not
>> know whether these are related to the problem.
>> [Fri Jan 07 11:36:29 2011] [error] [client 11.11.11.11] PHP Notice:
>> Undefined index: flash in
>> 
>> /www/postfixadmin/templates_c/0d1a714f76f647ac5097fa38ac2b35080d18dd1
>> 2.file.header.tpl.php on line 54, referer: [...]
>
> Those errors are unrelated and only show that our migration to smarty 
> is
> still not perfect ;-) But that are minor things, nothing that breaks
> functionality.
>
>
> Regards,
>
> Christian Boltz
> --
> Mmh. Nachdem alle hier anscheinend Mutt verwenden habe ich mal einen
> Blick draufgeworfen. Dafür braucht man entweder ein Studium 
> (Schwerpunkt
> Mutt) oder viel Zeit. Mal sehen was ich zuerst habe.
> [Christian Wunderlich in suse-linux]
>
> 
> ------------------------------------------------------------------------------
> Gaining the trust of online customers is vital for the success of any 
> company
> that requires sensitive data to be transmitted over the Web.   Learn 
> how to
> best implement a security strategy that keeps consumers' information 
> secure
> and instills the confidence they need to proceed with transactions.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

-- 
 NEOCRON:      Cyberpunk FPS MMORG http://www.neocron.com

Re: [Postfixadmin-devel] Email account created via postfixadmin not recognised by imap (dovecot)

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

Hello,

Am Friday 07 January 2011 schrieb J4:
>     I had postfixadmin working, and a few days I created an account
> in it (1234@xxxinfo).  The account could login, send email & so on.
> Today, I added another test account, but the account would not log
> in.

> I compared the entries for each account in mysql and noticed that
> these differed:
> 
> mysql> select * from mailbox;
> 
> | 12...@xx...   | $1111111111111 | S.L TEST         | ...
> | te...@xx... | $11111111111111 | test Test     | xxx.info/test/ ...

> mysql> select * from virtual_users;

> |  1 |         1 | xxxx | 12...@xx... |

> mysql> select * from virtual_aliases;

> |  1 |         1 | 12...@xx... | 12...@xx... |
> |  2 |         1 | 12...@xx... | fre...@kl...     |

Seeing your table names, I'd say you must be zed1 from IRC ;-)

It looks like you still suffer from the mixup of
a) the HOWTO you found somewhere on the web (virtual_* tables)
b) postfixadmin's tables (mailbox, alias etc. tables)

I'm quite sure that your dovecot still uses the "virtual_users" table - 
change it to use the "mailbox" table and it should work.

You should also remove the virtual_* tables to avoid future confusion 
(a backup never hurts, but you probably won't need it ;-)
Postfixadmin does not use any virtual_* tables (except if you have 
defined custom table names or a database prefix in the config, but 
that's something you would know.)

If something breaks ofter removing the virtual_* tables, you most 
probably have to fix the configuration of the breaking service.

> These errors keep popping up in the apache error.log, and I do not
> know whether these are related to the problem.
> [Fri Jan 07 11:36:29 2011] [error] [client 11.11.11.11] PHP Notice:
> Undefined index: flash in
> /www/postfixadmin/templates_c/0d1a714f76f647ac5097fa38ac2b35080d18dd1
> 2.file.header.tpl.php on line 54, referer: [...]

Those errors are unrelated and only show that our migration to smarty is 
still not perfect ;-) But that are minor things, nothing that breaks 
functionality.


Regards,

Christian Boltz
-- 
Mmh. Nachdem alle hier anscheinend Mutt verwenden habe ich mal einen
Blick draufgeworfen. Dafür braucht man entweder ein Studium (Schwerpunkt
Mutt) oder viel Zeit. Mal sehen was ich zuerst habe.
[Christian Wunderlich in suse-linux]