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

Re: [Postfixadmin-devel] Virtual vacation-related

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

Oh moment, i git it wrong.

So you mean in the alias table if vaction is turned on, the sender get a 
vacation mail but the sent mail is not in the maildir of your user?

Lets see. I think that are 2 or 3 lines in the php code.

the same thing, i upload it to trunk.

Rudi
Am 13.07.2011 09:47, schrieb Ian R. Justman:
> Hi, all.
>
> Is it normal to see the alias only point to
> "emailaddress#vir...@va..." when one sets a
> vacation message using the virtual vacation subsystem?  If so, then I
> have a problem.  I had one of my clients inform me that he wasn't
> getting e-mails despite the fact the autoresponder was working as it
> should.  Is it configurable so that it will add the actual e-mail for
> the vacationing recipient to the alias so he can get his mail (i.e. the
> "address" column has "ema...@vi..." and the "goto"
> column has
> "ema...@vi...,emailaddress#vir...@va..."
> in the "alias" table)?  Or is this a case of either hand-editiong the
> database or coding it myself?  I can do the former (in fact, that's what
> I did), but while it's relatively easy to do, it's very inconvenient.
> If I knew enough PHP, I would consider the latter.
>
> Thanks.
>
> --Ian.
>

Re: [Postfixadmin-devel] Virtual vacation-related

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

Hello Ian,

the vacation script is written in Perl. So you have to be able to chang 
some lines in this perl script.

I try if i can build it like your wishes and upload it to trunk. chris 
or ginger have to test if it works with 2.3.3 and if so, we can serve it 
with 2.3.4.



Greetz Rudi

Am 13.07.2011 09:47, schrieb Ian R. Justman:
> Hi, all.
>
> Is it normal to see the alias only point to
> "emailaddress#vir...@va..." when one sets a
> vacation message using the virtual vacation subsystem?  If so, then I
> have a problem.  I had one of my clients inform me that he wasn't
> getting e-mails despite the fact the autoresponder was working as it
> should.  Is it configurable so that it will add the actual e-mail for
> the vacationing recipient to the alias so he can get his mail (i.e. the
> "address" column has "ema...@vi..." and the "goto"
> column has
> "ema...@vi...,emailaddress#vir...@va..."
> in the "alias" table)?  Or is this a case of either hand-editiong the
> database or coding it myself?  I can do the former (in fact, that's what
> I did), but while it's relatively easy to do, it's very inconvenient.
> If I knew enough PHP, I would consider the latter.
>
> Thanks.
>
> --Ian.
>

[Postfixadmin-devel] Virtual vacation-related

[Ian R. J. <ia...@ia...>]

Hi, all.

Is it normal to see the alias only point to 
"emailaddress#vir...@va..." when one sets a 
vacation message using the virtual vacation subsystem?  If so, then I 
have a problem.  I had one of my clients inform me that he wasn't 
getting e-mails despite the fact the autoresponder was working as it 
should.  Is it configurable so that it will add the actual e-mail for 
the vacationing recipient to the alias so he can get his mail (i.e. the 
"address" column has "ema...@vi..." and the "goto" 
column has 
"ema...@vi...,emailaddress#vir...@va..." 
in the "alias" table)?  Or is this a case of either hand-editiong the 
database or coding it myself?  I can do the former (in fact, that's what 
I did), but while it's relatively easy to do, it's very inconvenient. 
If I knew enough PHP, I would consider the latter.

Thanks.

--Ian.

-- 
Ian R. Justman
UNIX hacker.  Anime fan.  Any questions?
ianj (at) ian-justman.com

[Postfixadmin-devel] Per mailbox transport

[Andre g. <and...@gm...>]

Hi.
I'm designing a large mail structure and I'll postfixadmin to manage the sql
database of emails.
We'll have separated mailbox servers, and that's why I'll need transport per
mailbox instead of just domains.

I think I already achieved this.
- Few changes on 4 files: edit-mailbox and create-mailbox (both them and
their template files).
- Extra 'transport' column on mailbox table
- Some tweaks on the recommended mysql_*.cf files, created some new ones and
reconfigured main.cf as well.
With just these changes I got what I need. And I don't feel it would cause
any problems with who only needs transports by entire domain.


Is there plans to postfixadmin support this ?
I ask that because I'm sure you would do it much better than how I did, and
I'm not a php master like you, so I'll need care with upgrades.

Thank you for this great software.

Re: [Postfixadmin-devel] Setup error

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

On 6 May 2011, at 15:33, Geoff Shang wrote:

> On Fri, 6 May 2011, David Goodwin wrote:
> 
>> Either install phppgadmin or nuke the database from orbit and restart 
>> the installation - fixing the plpgsql problem first ;-)
> 
> ah yes.  I should have thought of this.  This should work.
> 
> I uninstalled the package so that dbconfig would get rid of the database. 
> I didn't notice this the first time I installed, but when I reinstalled 
> the package this time, I got the following errors:
> 
> sh: getcwd() failed: No such file or directory
> shell-init: error retrieving current directory: getcwd: cannot access 
> parent directories: No such file or directory
> dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf
> shell-init: error retrieving current directory: getcwd: cannot access 
> parent directories: No such file or directory
> shell-init: error retrieving current directory: getcwd: cannot access 
> parent directories: No such file or directory
> sh: getcwd() failed: No such file or directory
> shell-init: error retrieving current directory: getcwd: cannot access 
> parent directories: No such file or directory
> shell-init: error retrieving current directory: getcwd: cannot access 
> parent directories: No such file or directory
> sh: getcwd() failed: No such file or directory
> creating postgres user postfixadmin:  already exists.
> resetting password:  success.
> sh: getcwd() failed: No such file or directory
> creating database postfixadmin: already exists.
> dbconfig-common: flushing administrative password


I'd guess your shell was 'in' /etc/postfixadmin or something similar which was removed when you nuked the package from orbit.

> 
> It looks like it did all it should do, but the errors are a bit 
> concerning.  There's nothing about these in /var/log/dpkg.log.
> 
> postgres@patronus:~$ psql postfixadmin
> psql (8.4.7)
> Type "help" for help.
> 
> postfixadmin=# CREATE LANGUAGE plpgsql;
> ERROR:  language "plpgsql" already exists
> 


Yes, 'create language' is a database wide change... hence it just needs doing once.

> Guess it already remembered that from before.
> 
> hmm.  Same error, guess i actually need to purge, not just uninstall.
> 
> OK, didn't get the shell errors this time.
> 

You'd probably changed directory!

> hmm, still remembered the database.  Will have to try removing postgresql 
> *as well*.
> 
> OK, this time I purged postfixadmin, postgresql-8.4 and dbconfig-common. 
> I should add that each time I've removed the dump that the uninstall wrote 
> to /var/tmp.
> 

I suspect that's a dbcommon thing.

> This time, the PFA install didn't seem to give comments about he database 
> already existing, despite the uninstall saying that it was gone.
> 

As expected, /var/lib/postgresql had been nuked.

> postgres@patronus:~$ psql postfixadmin
> psql (8.4.7)
> Type "help" for help.
> 
> postfixadmin=# CREATE LANGUAGE plpgsql;
> CREATE LANGUAGE
> 
> OK, everything worked this time.  Obviously this will need to get sorted. 
> Fortunately I'd only just installed the database so nothing was lost, but 
> this won't always be the case.
> 
>> I'm sure you can fix permissions on postgresql objects, but I can't 
>> remember the syntax off the top of my head.
> 
> I know almost nothing about PG.  I'm more familiar with MySQL, but made 
> the switch for philosophical reason.  I decided the only way to learn it 
> was to use it, but I've not made the time to actually learn it yet.
> 
>> Sorry, I'm not overly helpful.
> 
> You were very helpful.  Thanks.



np.

David

Re: [Postfixadmin-devel] Setup error

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

On Fri, 6 May 2011, David Goodwin wrote:

> Either install phppgadmin or nuke the database from orbit and restart 
> the installation - fixing the plpgsql problem first ;-)

ah yes.  I should have thought of this.  This should work.

I uninstalled the package so that dbconfig would get rid of the database. 
I didn't notice this the first time I installed, but when I reinstalled 
the package this time, I got the following errors:

sh: getcwd() failed: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access 
parent directories: No such file or directory
dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf
shell-init: error retrieving current directory: getcwd: cannot access 
parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access 
parent directories: No such file or directory
sh: getcwd() failed: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access 
parent directories: No such file or directory
shell-init: error retrieving current directory: getcwd: cannot access 
parent directories: No such file or directory
sh: getcwd() failed: No such file or directory
creating postgres user postfixadmin:  already exists.
resetting password:  success.
sh: getcwd() failed: No such file or directory
creating database postfixadmin: already exists.
dbconfig-common: flushing administrative password

It looks like it did all it should do, but the errors are a bit 
concerning.  There's nothing about these in /var/log/dpkg.log.

postgres@patronus:~$ psql postfixadmin
psql (8.4.7)
Type "help" for help.

postfixadmin=# CREATE LANGUAGE plpgsql;
ERROR:  language "plpgsql" already exists

Guess it already remembered that from before.

hmm.  Same error, guess i actually need to purge, not just uninstall.

OK, didn't get the shell errors this time.

hmm, still remembered the database.  Will have to try removing postgresql 
*as well*.

OK, this time I purged postfixadmin, postgresql-8.4 and dbconfig-common. 
I should add that each time I've removed the dump that the uninstall wrote 
to /var/tmp.

This time, the PFA install didn't seem to give comments about he database 
already existing, despite the uninstall saying that it was gone.

postgres@patronus:~$ psql postfixadmin
psql (8.4.7)
Type "help" for help.

postfixadmin=# CREATE LANGUAGE plpgsql;
CREATE LANGUAGE

OK, everything worked this time.  Obviously this will need to get sorted. 
Fortunately I'd only just installed the database so nothing was lost, but 
this won't always be the case.

> I'm sure you can fix permissions on postgresql objects, but I can't 
> remember the syntax off the top of my head.

I know almost nothing about PG.  I'm more familiar with MySQL, but made 
the switch for philosophical reason.  I decided the only way to learn it 
was to use it, but I've not made the time to actually learn it yet.

> Sorry, I'm not overly helpful.

You were very helpful.  Thanks.

Geoff.

Re: [Postfixadmin-devel] Setup error

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

> 
> 
> Ergh.  Looks like I should have only run the "create language plpgsql" 
> statement as user postgres and run the second query via the setup script.
> 
> I'm guessing I can undo what I did as postgres, but as I'm not very 
> familiar with postgresql, I'm not sure what I should do next.

Either install phppgadmin or nuke the database from orbit and restart the installation - fixing the plpgsql problem first ;-)

I'm sure you can fix permissions on postgresql objects, but I can't remember the syntax off the top of my head.

Sorry, I'm not overly helpful.

Thanks
David.

Re: [Postfixadmin-devel] Setup error

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

On Thu, 5 May 2011, David Goodwin wrote:

> See below.

Thanks for getting back to me.

>>    updating to version 730 (PgSQL)...
>>
>>    CREATE LANGUAGE plpgsql
>>
>>    DEBUG INFORMATION:
>>    Invalid query: ERROR: must be owner of database postfixadmin
>>
>>    CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER AS
>>    $merge_quota$ BEGIN UPDATE quota SET current = NEW.current + current
>>    WHERE username = NEW.username AND path = NEW.path; IF found THEN RETURN
>>    NULL; ELSE RETURN NEW; END IF; END; $merge_quota$ LANGUAGE plpgsql;
>>
>
>
> sudo -s (or otherwise become root)
>
> su - postgres
>
> psql postfix    (assuming db name is postfix; "psql -l" will list all databases)

postgres@patronus:~$ psql postfix
psql: FATAL:  database "postfix" does not exist
postgres@patronus:~$ psql -l
                                    List of databases
      Name     |  Owner   | Encoding |  Collation  |    Ctype    |   Access 
privileges
--------------+----------+----------+-------------+-------------+-----------------------
  postfixadmin | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
  postgres     | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
  template0    | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
=c/postgres
                                                                 : 
postgres=CTc/postgres
  template1    | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | 
=c/postgres
                                                                 : 
postgres=CTc/postgres
(4 rows)

postgres@patronus:~$ psql postfixadmin
psql (8.4.7)
Type "help" for help.

> Copy and paste the above in.... if that fails, try the 'create language plpgsql' then paste the above in.

  postfixadmin=# CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER 
AS $merge_quota$ BEGIN UPDATE quota SET current = NEW.current + current 
WHERE username = NEW.username AND path = NEW.path; IF found THEN RETURN 
NULL; ELSE RETURN NEW; END IF; END; $merge_quota$ LANGUAGE plpgsql;
ERROR:  language "plpgsql" does not exist
HINT:  Use CREATE LANGUAGE to load the language into the database.
postfixadmin=# create language plpgsql;
CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER AS $merge_quota$ 
BEGIN
UPDATE quota SET current = NEW.current + current WHERE username = 
NEW.username AND path = NEW.path; IF found THEN RETURN NULL; ELSE RETURN 
NEW; END IF; END; $merge_quota$ LANGUAGE plpgsql;
CREATE LANGUAGE
CREATE FUNCTION

Looks like that worked.

    updating to version 730 (PgSQL)...

    CREATE LANGUAGE plpgsql

    DEBUG INFORMATION:
    Invalid query: ERROR: language "plpgsql" already exists

    CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER AS
    $merge_quota$ BEGIN UPDATE quota SET current = NEW.current + current
    WHERE username = NEW.username AND path = NEW.path; IF found THEN RETURN
    NULL; ELSE RETURN NEW; END IF; END; $merge_quota$ LANGUAGE plpgsql;

    DEBUG INFORMATION:
    Invalid query: ERROR: must be owner of function merge_quota

Ergh.  Looks like I should have only run the "create language plpgsql" 
statement as user postgres and run the second query via the setup script.

I'm guessing I can undo what I did as postgres, but as I'm not very 
familiar with postgresql, I'm not sure what I should do next.

> I'm wondering if it's a case of some default setting changing....

Is there more information I can give you?

Geoff.

Re: [Postfixadmin-devel] Setup error

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

On Thu, 5 May 2011, David Goodwin wrote:

>> FYI, I edited config.inc.php with my customisations, and then took its
>> suggestion of saving it as config.local.php to proof it against upgrades.
>> But when I ran setup.php, both with and without debug, I got the
>> following in the error log:
>>
>
> You /might/ have a circular reference there.

Oh of *course* I do.  Duh!!!!

<mutters something about PHP warning about including a file in itself>

I did wonder how I managed to fill up 134 MB of RAM.  Oops.

It's getting late.

Geoff.

Re: [Postfixadmin-devel] Setup error

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

On 5 May 2011, at 22:26, Geoff Shang wrote:

> On Thu, 5 May 2011, Christian Boltz wrote:
> 
>> Please run setup.php?debug=1 to get a more useful error message.
> 
> FYI, I edited config.inc.php with my customisations, and then took its 
> suggestion of saving it as config.local.php to proof it against upgrades. 
> But when I ran setup.php, both with and without debug, I got the 
> following in the error log:
> 

You /might/ have a circular reference there. 

config.local.php should only contain the variables / settings you wish to override, e.g. 


orange:~ $ cat src/postfixadmin/trunk/config.local.php 


<?php
$CONF['configured'] = true;
$CONF['setup_password'] = 'changeme';

$CONF['postfix_admin_url'] = '/david/postfixadmin/';

// shouldn't need changing.
$CONF['postfix_admin_path'] = dirname(__FILE__);

// Language config
// Language files are located in './languages', change as required..
$CONF['default_language'] = 'en';

// Database Config
// mysql = MySQL 3.23 and 4.0, 4.1 or 5
// mysqli = MySQL 4.1+ 
// pgsql = PostgreSQL
$CONF['database_type'] = 'pgsql';
$CONF['database_host'] = 'pgsqlserver';
$CONF['database_user'] = 'dg';
$CONF['database_password'] = 'whatever';
$CONF['database_name'] = 'postfix';
$CONF['database_prefix'] = '';

$CONF['vacation'] = 'YES';

// end file.

thanks
David.




> [Thu May 05 22:40:35 2011] [error] [client ::1] PHP Fatal error:  Allowed 
> memory size of 134217728 bytes exhausted (tried to allocate 30720 bytes) 
> in /etc/postfixadmin/config.local.php on line 137
> 
> If I used the original config.inc.php *or* my modified one as that 
> filename (i.e. not being loaded as config.local.php), it ran just fine.
> 
> Geoff.
> 
> 
> ------------------------------------------------------------------------------
> WhatsUp Gold - Download Free Network Management Software
> The most intuitive, comprehensive, and cost-effective network 
> management toolset available today.  Delivers lowest initial 
> acquisition cost and overall TCO of any competing solution.
> http://p.sf.net/sfu/whatsupgold-sd
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

Re: [Postfixadmin-devel] Setup error

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

See below.

>> 
>> The interesting thing is that the function to update to version 730
>> first runs a 'CREATE LANGUAGE plpgsql' query. Looks like this fails on
>> your system for some reason.
>> 
>> Please run setup.php?debug=1 to get a more useful error message.
> 
>    Updating database:
> 
>    - old version: 729; target version: 740
> 
>    updating to version 730 (PgSQL)...
> 
>    CREATE LANGUAGE plpgsql
> 
>    DEBUG INFORMATION:
>    Invalid query: ERROR: must be owner of database postfixadmin
> 
>    CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER AS
>    $merge_quota$ BEGIN UPDATE quota SET current = NEW.current + current
>    WHERE username = NEW.username AND path = NEW.path; IF found THEN RETURN
>    NULL; ELSE RETURN NEW; END IF; END; $merge_quota$ LANGUAGE plpgsql;
> 


sudo -s (or otherwise become root)

su - postgres

psql postfix    (assuming db name is postfix; "psql -l" will list all databases)

Copy and paste the above in.... if that fails, try the 'create language plpgsql' then paste the above in.

I'm wondering if it's a case of some default setting changing....

thanks
David.

Re: [Postfixadmin-devel] Setup error

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

On Thu, 5 May 2011, Christian Boltz wrote:

> Please run setup.php?debug=1 to get a more useful error message.

FYI, I edited config.inc.php with my customisations, and then took its 
suggestion of saving it as config.local.php to proof it against upgrades. 
But when I ran setup.php, both with and without debug, I got the 
following in the error log:

[Thu May 05 22:40:35 2011] [error] [client ::1] PHP Fatal error:  Allowed 
memory size of 134217728 bytes exhausted (tried to allocate 30720 bytes) 
in /etc/postfixadmin/config.local.php on line 137

If I used the original config.inc.php *or* my modified one as that 
filename (i.e. not being loaded as config.local.php), it ran just fine.

Geoff.

Re: [Postfixadmin-devel] Setup error

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

Hi,

Thanks for the reply.

On Thu, 5 May 2011, Christian Boltz wrote:

>> then ran "lynx http://localhost/postfixadmin/setup.php".
>>
>>     updating to version 730 (PgSQL)...
>>
>>     DEBUG INFORMATION:
>>     Invalid query: ERROR: language "plpgsql" does not exist HINT: Use
>>     CREATE LANGUAGE to load the language into the database.
>
> The interesting thing is that the function to update to version 730
> first runs a 'CREATE LANGUAGE plpgsql' query. Looks like this fails on
> your system for some reason.
>
> Please run setup.php?debug=1 to get a more useful error message.

    Updating database:

    - old version: 729; target version: 740

    updating to version 730 (PgSQL)...

    CREATE LANGUAGE plpgsql

    DEBUG INFORMATION:
    Invalid query: ERROR: must be owner of database postfixadmin

    CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER AS
    $merge_quota$ BEGIN UPDATE quota SET current = NEW.current + current
    WHERE username = NEW.username AND path = NEW.path; IF found THEN RETURN
    NULL; ELSE RETURN NEW; END IF; END; $merge_quota$ LANGUAGE plpgsql;

    DEBUG INFORMATION:
    Invalid query: ERROR: language "plpgsql" does not exist HINT: Use
    CREATE LANGUAGE to load the language into the database.

> Or login to PostgreSQL directly and run the following query:
>    CREATE LANGUAGE plpgsql

Not sure exactly what I need to do that.  I've only just installed this on 
a clean VPS and don't know what account I should use to ogin.  I'll need 
to go look at Debian docs I guess.

Thanks,
Geoff.

Re: [Postfixadmin-devel] Setup error

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

Hello,

Am Donnerstag, 5. Mai 2011 schrieb Geoff Shang:
> Apologies if this is the wrong place.

You are perfectly right - it's just the mailinglist name that might be 
misleading ;-)  (in other words: we don't have enough questions for a 
separate -users mailinglist.)

> then ran "lynx http://localhost/postfixadmin/setup.php".
> 
>     updating to version 730 (PgSQL)...
> 
>     DEBUG INFORMATION:
>     Invalid query: ERROR: language "plpgsql" does not exist HINT: Use
>     CREATE LANGUAGE to load the language into the database.

The interesting thing is that the function to update to version 730 
first runs a 'CREATE LANGUAGE plpgsql' query. Looks like this fails on 
your system for some reason.

Please run setup.php?debug=1 to get a more useful error message.
Or login to PostgreSQL directly and run the following query:
    CREATE LANGUAGE plpgsql

If you can't get it working, post the detailed PostgreSQL error message. 
David can then probably help you (I can't because I'm using MySQL ;-)


Regards,

Christian Boltz
-- 
> ganz im Gegensatz zu dir süffisanten Personal-Firewall-/-Knallkopp.
cool ... du bist ja putzig.
> Geh mal einen Psychologen aufsuchen.
ich dachte ich bin der Psychologe. soll ich mich also selber
aufsuchen, ja? [> Timo Nentwig und Michael Meyer in suse-linux]

[Postfixadmin-devel] Setup error

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

Hi,

Apologies if this is the wrong place.

I'm seting up a VPS running Debian Squeeze and I want to use PostfixAdmin.

I managed to find the Debian package (I was surprised there isn't an 
official Debian package yet), installed it, manually linked the 
apache.conf file to the write place so that it would actually work then 
ran "lynx http://localhost/postfixadmin/setup.php".

It all seemed to be going well until:

    updating to version 730 (PgSQL)...

    DEBUG INFORMATION:
    Invalid query: ERROR: language "plpgsql" does not exist HINT: Use
    CREATE LANGUAGE to load the language into the database.

This is the first database to be used and I've not yet done any other 
Postfix configuration.

I don't know enough about this to debug it, and figured someone else would 
know.

Any thoughts?

Geoff.

Re: [Postfixadmin-devel] domian-wide sender_bcc_maps and recipient_bcc_maps admin patch

[Max G. <ma...@ne...>]

On Tue, May 03, 2011 at 08:31:25AM -0400, Tanstaafl wrote:
> Very nice, and definitely should be considered for addition to the core
> code, but I wonder if it is possible to adjust this so that it adds a
> plus delimeter with the original users local address part?
> 
> Ie, instead of aliasing to 'everything@', alias to 'everything+user@'...
> where 'user' is the original recipients local address part?
Yes, definetely possible, once i get to it : )
Should be pretty trivial, just need to make sure when the setting is changed/added or when a user is added, a new entry is made in that table.
Postfix will automatically create the maildir on delivery for whatever is in the bcc column.

On other hand, once you have access to that inbox, you could filter by the To/From within a MUA, but yes, that would be less desirable.

> To expand on this... could it be made to differentiate between outbound
> and inbound?
Well, right now there are 2 tabeles - bcc_senders and bcc_recipients, so different mailboxes can be used for incoming vs outgoing mail, although it will not be per user.

> I know, I like to complicate things.
Hehe, features are awesome!

Re: [Postfixadmin-devel] domian-wide sender_bcc_maps and recipient_bcc_maps admin patch

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

On 2011-04-29 3:44 PM, Max Gribov wrote:
> Hi all,
> i developed a simple/small patch against trunk which allows enabling domain-wide (NOT per user) BCC setting (http://www.postfix.org/ADDRESS_REWRITING_README.html#auto_bcc)
> 
> The patch adds "BCC Recipient" and "BCC Sender" columns to the domain list, and adds 2 text inputs for the functionality in domain edit screens.
> 
> When either field is set, an apropriate wildcard BCC entry is created in bcc_recipients/bcc_senders tables
> 
> Here's an example db entry to forward all incoming email for example.com to eve...@ex...
> mysql> select * from bcc_senders;
> +--------------+------------------------+-------------+---------------------+---------------------+--------+
> | user         | bcc                    | domain      | created             | modified            | active |
> +--------------+------------------------+-------------+---------------------+---------------------+--------+
> | @example.com | eve...@ex... | example.com | 2011-04-29 12:02:11 | 2011-04-29 18:48:41 |      1 |
> +--------------+------------------------+-------------+---------------------+---------------------+--------+
> 
> Is there interest in this kind of functionality? The patch is attached, as im not sure how to go about submitting it?..
> 
> Also, i've never seen PA code before today, so of course the patch may not comply with PA coding standards, but i will happily change whatever is needed.

Very nice, and definitely should be considered for addition to the core
code, but I wonder if it is possible to adjust this so that it adds a
plus delimeter with the original users local address part?

Ie, instead of aliasing to 'everything@', alias to 'everything+user@'...
where 'user' is the original recipients local address part?

This would make it easy to file these in folders, rather than dumping
everyone's messages in a single folder.

To expand on this... could it be made to differentiate between outbound
and inbound?

Ie, everything-in+user@, and everything-out+user@ ?

I know, I like to complicate things.

Re: [Postfixadmin-devel] 1 to 1 alias domains

[Ron G. <ro...@vn...>]

Christian Boltz wrote:
> Hello,
>
> Am Sonntag, 1. Mai 2011 schrieb Ron Guerin:
>   
>> Christian Boltz wrote:
>>     
>>> Am Sonntag, 1. Mai 2011 schrieb Ron Guerin:
>>> It is no problem to have several domains (on the "from" side of the
>>> alias) pointing to the same target domain, for example
>>>
>>>     foo.com -> example.com
>>>     bar.com -> example.com
>>>       
>
>   
>> Does not work in my version (2.3.3) .  You cannot alias both foo.com
>> and bar.com to example.com.  
>>     
>
> Just tested with 2.3.3 - result: works.
> Do you see any error messages?
>   

Interesting.  I'll have to look into this further.  Thanks for checking.

- Ron

Re: [Postfixadmin-devel] 1 to 1 alias domains

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

Hello,

Am Sonntag, 1. Mai 2011 schrieb Ron Guerin:
> Christian Boltz wrote:
> > Am Sonntag, 1. Mai 2011 schrieb Ron Guerin:
> > It is no problem to have several domains (on the "from" side of the
> > alias) pointing to the same target domain, for example
> > 
> >     foo.com -> example.com
> >     bar.com -> example.com

> Does not work in my version (2.3.3) .  You cannot alias both foo.com
> and bar.com to example.com.  

Just tested with 2.3.3 - result: works.
Do you see any error messages?

> Is this a bug that got fixed?

No, I don't remember a bug in that area.


Regards,

Christian Boltz
-- 
Du solltest mal deine sHIFT-taSTE und die ordogravieh in Ordnung
bringen. Das hilft in jedem Falle dabei, hier qualifizierte Antworten
zu bekommen. [Axel Heinrici in suse-linux]

Re: [Postfixadmin-devel] 1 to 1 alias domains

[Ron G. <ro...@vn...>]

Christian Boltz wrote:
> Hello,
>
> Am Sonntag, 1. Mai 2011 schrieb Ron Guerin:
>   
>> Was it a deliberate decision to only allow a one to one relationship
>> between domains for aliasing purposes?  I have one domain and 4
>> aliased to it (I added the MySQL records by hand) and if it's not
>> over my head I might try sending a patch in if the idea is
>> acceptable.  Otherwise I'm probably not going to bother changing the
>> code for myself either.
>>     
>
> I'm afraid I don't really understand your problem :-(
> Therefore I'll give a short explanation about what is allowed for alias 
> domains.
>
> It is no problem to have several domains (on the "from" side of the 
> alias) pointing to the same target domain, for example
>     foo.com -> example.com
>     bar.com -> example.com
>
> However, a domain that is already used on the "to" side can't be used on 
> the "from" side of another alias domain. For example, if you have the 
> two alias domains listed above, you can't do
>     example.com -> foobar.com   # not allowed
> This is a restriction we intentionally included because it is the 
> easiest way to avoid loops.
>   

Does not work in my version (2.3.3) .  You cannot alias both foo.com and
bar.com to example.com.  Is this a bug that got fixed?

- Ron

Re: [Postfixadmin-devel] 1 to 1 alias domains

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

Hello,

Am Sonntag, 1. Mai 2011 schrieb Ron Guerin:
> Was it a deliberate decision to only allow a one to one relationship
> between domains for aliasing purposes?  I have one domain and 4
> aliased to it (I added the MySQL records by hand) and if it's not
> over my head I might try sending a patch in if the idea is
> acceptable.  Otherwise I'm probably not going to bother changing the
> code for myself either.

I'm afraid I don't really understand your problem :-(
Therefore I'll give a short explanation about what is allowed for alias 
domains.

It is no problem to have several domains (on the "from" side of the 
alias) pointing to the same target domain, for example
    foo.com -> example.com
    bar.com -> example.com

However, a domain that is already used on the "to" side can't be used on 
the "from" side of another alias domain. For example, if you have the 
two alias domains listed above, you can't do
    example.com -> foobar.com   # not allowed
This is a restriction we intentionally included because it is the 
easiest way to avoid loops.

If this does not answer your question, please send an example what you 
manually had to add to the database so that I can understand your 
problem.


Regards,

Christian Boltz
-- 
> Ich komme z.Zt. kaum noch mit dem Lesen der Listenmails nach.
> (Freundin ist schuld.)
Oh, hast du noch "Freundin 1.3"? Ab 2.0 beherrscht zumindest die
OS-Version Suspend-to-Disco und Suspend-to-MOM, teste die doch mal
an :-) Klappt hier ganz prima. 
[> Ralph Müller und  Michael Behrens in suse-linux]

Re: [Postfixadmin-devel] domian-wide sender_bcc_maps and recipient_bcc_maps admin patch

[Ron G. <ro...@vn...>]

From: Max Gribov <max@ne...> -    2011-04-29 19:42

> i developed a simple/small patch against trunk which allows enabling
domain-wide (NOT per user) BCC setting

> Is there interest in this kind of functionality?

This isn't a proper reply since I wasn't on the list when you sent the
message, but yes, I'm interested in this.  I've got two domains that
presently use that functionality in Postfix and expect that's going to
be something I get asked about a lot because of compliance issues.

- Ron

[Postfixadmin-devel] 1 to 1 alias domains

[Ron G. <ro...@vn...>]

Was it a deliberate decision to only allow a one to one relationship
between domains for aliasing purposes?  I have one domain and 4 aliased
to it (I added the MySQL records by hand) and if it's not over my head I
might try sending a patch in if the idea is acceptable.  Otherwise I'm
probably not going to bother changing the code for myself either.

- Ron

[Postfixadmin-devel] domian-wide sender_bcc_maps and recipient_bcc_maps admin patch

[Max G. <ma...@ne...>]

Hi all,
i developed a simple/small patch against trunk which allows enabling domain-wide (NOT per user) BCC setting (http://www.postfix.org/ADDRESS_REWRITING_README.html#auto_bcc)

The patch adds "BCC Recipient" and "BCC Sender" columns to the domain list, and adds 2 text inputs for the functionality in domain edit screens.

When either field is set, an apropriate wildcard BCC entry is created in bcc_recipients/bcc_senders tables

Here's an example db entry to forward all incoming email for example.com to eve...@ex...
mysql> select * from bcc_senders;
+--------------+------------------------+-------------+---------------------+---------------------+--------+
| user         | bcc                    | domain      | created             | modified            | active |
+--------------+------------------------+-------------+---------------------+---------------------+--------+
| @example.com | eve...@ex... | example.com | 2011-04-29 12:02:11 | 2011-04-29 18:48:41 |      1 |
+--------------+------------------------+-------------+---------------------+---------------------+--------+

Is there interest in this kind of functionality? The patch is attached, as im not sure how to go about submitting it?..

Also, i've never seen PA code before today, so of course the patch may not comply with PA coding standards, but i will happily change whatever is needed.


Postfix configs:
main.cf:
recipient_bcc_maps = proxy:mysql:/etc/postfix/mysql/mysql_virtual_bcc_recipients_maps.cf
sender_bcc_maps = proxy:mysql:/etc/postfix/mysql/mysql_virtual_bcc_senders_maps.cf

mysql_virtual_bcc_recipients_maps.cf:
hosts = 127.0.0.1
user = postfix
password = password
dbname = email
query = select bcc from bcc_recipients where user = '%s' and active=1;

mysql_virtual_bcc_senders_maps.cf:
hosts = 127.0.0.1
user = postfix
password = password
dbname = email
query = select bcc from bcc_senders where user = '%s' and active=1;


DB tables:
CREATE TABLE `bcc_recipients` (
  `user` varchar(255) NOT NULL,
  `bcc` varchar(255) NOT NULL,
  `domain` varchar(255) NOT NULL,
  `created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `active` tinyint(1) NOT NULL DEFAULT '1'
);

CREATE TABLE `bcc_senders` (
  `user` varchar(255) NOT NULL,
  `bcc` varchar(255) NOT NULL,
  `domain` varchar(255) NOT NULL,
  `created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `modified` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `active` tinyint(1) NOT NULL DEFAULT '1'
);

[Postfixadmin-devel] PostfixAdmin @LinuxTag

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

Hello,

LinuxTag (www.linuxtag.org) in Berlin is coming soon (May 11-14).

They have introduced a new concept called "Project Meeting Point", which 
is basically a part-time booth for small projects that don't have enough 
people for a "normal" (full-time) booth.

To make the story short: I'll present PostfixAdmin at LinuxTag :-)

The current planning [1] is that I'll be at the Project Meeting Point on
- Thursday 13:00-14:00
- Saturday 11:00-12:00

If someone is visiting LinuxTag, make sure to come around ;-)
If you can't make it at the times listed above, just send me a mail. I'm 
there Thursday till Saturday, and we'll probably find another time for a 
meeting.

I can probably offer some free tickets for LinuxTag - just send me a 
mail if you are interested.

And finally I can recommend my talk "wine is not only an emulator" 
(Saturday 17:00). Let me just say that the subtitle is "it is also 
something to drink" ;-)


Regards,

Christian Boltz

[1] The latest schedule is available on
    http://wiki.linuxtag.org/w/fp:ProjectMeetingPoints

-- 
Auch wenn da nix sein KANN und Du lieber neue Parameter einbaust. Tust
Du MIR bitte mal den Gefallen und liest Du wenigstens EINMAL Deine
main.cf auf komische Umbrüche und Einträge hin durch? Nur mir zuliebe,
bitte. Ich weiß, ist natürlich Unsinn. Machst Du es trotzdem?
[Peer Heinlein in postfixbuch-users]