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

Re: [Postfixadmin-devel] DB schema question

[Richard H. <ri...@wa...>]

On 5/12/24 10:18, Christian Boltz wrote:
> Hello,
> 
> Am Dienstag, 3. Dezember 2024, 12:09 schrieb Richard Hector:
>> On 1/12/24 01:40, Christian Boltz wrote:
>> > Am Samstag, 30. November 2024, 06:18 schrieb Richard Hector:
> 
>> >> If they are always the same, then the example db query for
>> >> virtual_alias_domain_mailbox_maps could be significantly
>> >> simplified.
>> > 
>> > Alias domains have a few special cases and pitfalls, but
>> > nevertheless, I'm looking forward for your proposal ;-)
>> 
>> So maybe this is where I show my ignorance, but:
>> 
>> SELECT maildir from mailbox m JOIN alias_domain ad ON m.domain =
>> ad.target_domain WHERE ad.alias_domain = '%d' and m.active and
>> ad.active
> 
> This query only checks the domain (%d), but not the mailbox name (%u).
> It will give you a list of maildirs for all mailboxes on that domain,
> but not (only) the maildir for the specified mailbox. It will even give
> you a list of maildirs if you query for a non-existing mailbox.
> (Always assuming that %d is an alias domain.)
> 
>> No concatenations required. 
> 
> Only because your query doesn't specify which mailbox to look for ;-)

Aah ... I shouldn't have done that from memory, in a hurry :-)

Checking %u against m.local_part would be necessary, at least - but I'm 
again short of time, so I'll have another look later. Thank you for your 
patience :-)

> 
> The lookup needs to be done for user@targetdomain, and there's no
> variable for it (%s is user@aliasdomain - which doesn't exist because
> it's meant to be rewritten to user@targetdomain). That's why we concat
> %u (localpart) + the target domain so that the query finds the right
> mailbox.
> 
> (For the records: these variables are explained in man 5 mysql_table.)
> 
>> Get rid of the table aliases if you like.
> 
> There's nothing wrong with specifying which table you want to use ;-)
> 
>> I don't know whether those booleans work like that in mysql/maria -
>> they do in PostgreSQL.
> 
> Good question, I didn't try before.
> 
> I just tested on MariaDB 11.5.2, and it indeed handles the booleans as
> expected.
> (No idea if older MariaDB versions or MySQL also accepts this syntax.)
> 
>> Also, we don't need maildir here, right? "SELECT 1 FROM ..." would
>> work just as well, and avoid confusing people (well, me) as to what
>> it's being used for :-)
> 
> Well, it depends how you deliver mails.
> 
> If you let Postfix write the mail into the maildir, then - surprise - it
> will need to know the maildir.
> 
> If you deliver via Dovecot lmtp, then Postfix of course doesn't need to
> know the maildir.

Yes, I guess this is the right query to provide that info to Postfix. 
And you're right, I'm using dovecot (actually deliver/lda, but planning 
to switch to lmtp), so wasn't fully thinking about that.

>> Feel free to tell me I've got it wrong :-)
> 
> As requested ;-) - I hope my explanation makes it clear why the query is
> written the way it is.

Many thanks (also for your responses on IRC),
Richard

Re: [Postfixadmin-devel] DB schema question

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

Hello,

Am Dienstag, 3. Dezember 2024, 12:09 schrieb Richard Hector:
> On 1/12/24 01:40, Christian Boltz wrote:
> > Am Samstag, 30. November 2024, 06:18 schrieb Richard Hector:

> >> If they are always the same, then the example db query for
> >> virtual_alias_domain_mailbox_maps could be significantly
> >> simplified.
> > 
> > Alias domains have a few special cases and pitfalls, but
> > nevertheless, I'm looking forward for your proposal ;-)
> 
> So maybe this is where I show my ignorance, but:
> 
> SELECT maildir from mailbox m JOIN alias_domain ad ON m.domain =
> ad.target_domain WHERE ad.alias_domain = '%d' and m.active and
> ad.active

This query only checks the domain (%d), but not the mailbox name (%u).
It will give you a list of maildirs for all mailboxes on that domain, 
but not (only) the maildir for the specified mailbox. It will even give 
you a list of maildirs if you query for a non-existing mailbox.
(Always assuming that %d is an alias domain.)

> No concatenations required. 

Only because your query doesn't specify which mailbox to look for ;-)

The lookup needs to be done for user@targetdomain, and there's no 
variable for it (%s is user@aliasdomain - which doesn't exist because 
it's meant to be rewritten to user@targetdomain). That's why we concat 
%u (localpart) + the target domain so that the query finds the right 
mailbox.

(For the records: these variables are explained in man 5 mysql_table.)

> Get rid of the table aliases if you like.

There's nothing wrong with specifying which table you want to use ;-)

> I don't know whether those booleans work like that in mysql/maria -
> they do in PostgreSQL.

Good question, I didn't try before.

I just tested on MariaDB 11.5.2, and it indeed handles the booleans as 
expected.
(No idea if older MariaDB versions or MySQL also accepts this syntax.)

> Also, we don't need maildir here, right? "SELECT 1 FROM ..." would
> work just as well, and avoid confusing people (well, me) as to what
> it's being used for :-)

Well, it depends how you deliver mails.

If you let Postfix write the mail into the maildir, then - surprise - it 
will need to know the maildir.

If you deliver via Dovecot lmtp, then Postfix of course doesn't need to 
know the maildir.

> Feel free to tell me I've got it wrong :-)

As requested ;-) - I hope my explanation makes it clear why the query is 
written the way it is.


Regards,

Christian Boltz
-- 
Maybe (as it's just repackaging), it could even run on some ppc64
obs-servers that must be quite depressed and have worn down their thumbs
quite a lot from twiddling them, chronically having nothing to do ...
[David Haller in opensuse-packaging]

Re: [Postfixadmin-devel] DB schema question

[Richard H. <ri...@wa...>]

On 1/12/24 01:40, Christian Boltz wrote:
> Hello,
> 
> Am Samstag, 30. November 2024, 06:18 schrieb Richard Hector:
>> I notice that the mailbox table has username and domain columns, where
>> the username is the full email address including the domain name. Are
>> the domain names in both places guaranteed to be the same?
> 
> Nobody can stop you from doing a silly INSERT or UPDATE query directly
> in the database.
> 
> That said - as long as you only use PostfixAdmin to modify the database,
> the domain column and the domain in the mailbox name are guaranteed to
> be the same.
> 
>> If they are always the same, then the example db query for
>> virtual_alias_domain_mailbox_maps could be significantly simplified.
> 
> Alias domains have a few special cases and pitfalls, but nevertheless,
> I'm looking forward for your proposal ;-)

So maybe this is where I show my ignorance, but:

SELECT maildir from mailbox m JOIN alias_domain ad ON m.domain = 
ad.target_domain WHERE ad.alias_domain = '%d' and m.active and ad.active

No concatenations required. Get rid of the table aliases if you like.

I don't know whether those booleans work like that in mysql/maria - they 
do in PostgreSQL.

Also, we don't need maildir here, right? "SELECT 1 FROM ..." would work 
just as well, and avoid confusing people (well, me) as to what it's 
being used for :-)

Feel free to tell me I've got it wrong :-)

Cheers,
Richard

Re: [Postfixadmin-devel] DB schema question

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

Hello,

Am Samstag, 30. November 2024, 06:18 schrieb Richard Hector:
> I notice that the mailbox table has username and domain columns, where
> the username is the full email address including the domain name. Are
> the domain names in both places guaranteed to be the same?

Nobody can stop you from doing a silly INSERT or UPDATE query directly 
in the database.

That said - as long as you only use PostfixAdmin to modify the database, 
the domain column and the domain in the mailbox name are guaranteed to 
be the same.

> If they are always the same, then the example db query for
> virtual_alias_domain_mailbox_maps could be significantly simplified.

Alias domains have a few special cases and pitfalls, but nevertheless, 
I'm looking forward for your proposal ;-)


Regards,

Christian Boltz
-- 
I usually explain databases as 2TB sized global variables
with a weird access method and concurrent access.
[https://twitter.com/isotopp/status/1352618340871778308]

[Postfixadmin-devel] DB schema question

[Richard H. <ri...@wa...>]

Hi all,

I notice that the mailbox table has username and domain columns, where 
the username is the full email address including the domain name. Are 
the domain names in both places guaranteed to be the same?

If they are always the same, then the example db query for 
virtual_alias_domain_mailbox_maps could be significantly simplified.

If not - under what circumstances?

Thanks,
Richard

Re: [Postfixadmin-devel] Postfixadmin 3.1 - Fixing after upgrade from Deb 11 to 12

[Sophie <so...@kl...>]

>> Hi everybody,
>> 
>> I had a working postfixadmin v 3.1 (sqlite3,nginx) installation until 
>> I upgraded from Debian 11 to 12 and along with this php 7.4 to php 
>> 8.2.
>> 
>> Afterwards, I got a blank screen when hitting the postfixadmin 
>> login.php.
>> 
>> The error is:
>> 2023/06/12 18:51:11 [error] 3799#3799: *1 FastCGI sent in stderr: "PHP 
>> message: PHP Fatal error:  Array and string offset access syntax with 
>> curly braces is no longer supported in 
>> /var/www/mx989.example.int/functions.inc.php on line 697" while 
>> reading response header from upstream, client: 12.24.32.82, server: 
>> mx989.example.int, request: "GET /login.php HTTP/2.0", upstream: 
>> "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "mx989.example.int"
>> 
>> for ($i = 0; $i < $j; ++$i) {
>> switch ($string{$i}) {
>> case '=':
>> case '<':
>> case '>':
>> case ',':
>> case '?':
>> case '_':
>> if ($iEncStart === false) {
>> $iEncStart = $i;
>> 
>> I could just upgrade from 3.1 to 3.3.13, but I don't know if this 
>> would mend the problem. Potentially it could if brackets are out of 
>> fashion :-0
>> 
>> Thx,
>> So.
> 
> Hi,
> 
> Upgrading to 3.3.10 made no difference.
> 
> How could i troubleshoot this?

Oddly I am getting a 403 from

error.log:2023/06/18 17:03:57 [error] 105214#105214: *36 
"/var/www/a.b.uk/index.php" is forbidden (13: Permission denied)

_# cat index.html_

_<html>_
_<head>_
_    <title>Postfix Admin</title>_
_</head>_
_<body>_
_    <p>The Postfix Admin directory layout changed.</p>_
_    <p>Please update your webserver config so that the DocumentRoot or 
Alias points to the directory "public".</p>_
_</body>_
_</html>_

The nginx has:

_server {_
_   listen 443 ssl http2 default deferred;_
_   #listen [::]:443 ipv6only=off ssl;_
_   server_name    a.b.uk;_
_   root            /var/www/a.b.uk;_
_   index           index.php;_
_   charset         utf-8;_

Which used to work until I moved from php 7.4 to 8.2.

I changed this to    _root /var/www/a.b.uk/public;_ as stated in the 
PostfixAdmin index.php, but it did not work. Still got a 403.  The curly 
bracket error messages seem to have gone after the 3.3.10 upgrade.

Re: [Postfixadmin-devel] Postfixadmin 3.1 - Fixing after upgrade from Deb 11 to 12

[Sophie <so...@kl...>]

On 2023-06-12 19:58, Sophie Loewenthal wrote:

> Hi everybody,
> 
> I had a working postfixadmin v 3.1 (sqlite3,nginx) installation until I 
> upgraded from Debian 11 to 12 and along with this php 7.4 to php 8.2.
> 
> Afterwards, I got a blank screen when hitting the postfixadmin 
> login.php.
> 
> The error is:
> 2023/06/12 18:51:11 [error] 3799#3799: *1 FastCGI sent in stderr: "PHP 
> message: PHP Fatal error:  Array and string offset access syntax with 
> curly braces is no longer supported in 
> /var/www/mx989.example.int/functions.inc.php on line 697" while reading 
> response header from upstream, client: 12.24.32.82, server: 
> mx989.example.int, request: "GET /login.php HTTP/2.0", upstream: 
> "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "mx989.example.int"
> 
> for ($i = 0; $i < $j; ++$i) {
> switch ($string{$i}) {
> case '=':
> case '<':
> case '>':
> case ',':
> case '?':
> case '_':
> if ($iEncStart === false) {
> $iEncStart = $i;
> 
> I could just upgrade from 3.1 to 3.3.13, but I don't know if this would 
> mend the problem. Potentially it could if brackets are out of fashion 
> :-0
> 
> Thx,
> So.

Hi,

Upgrading to 3.3.10 made no difference.

How could i troubleshoot this?

[Postfixadmin-devel] Postfixadmin 3.1 - Fixing after upgrade from Deb 11 to 12

[Sophie L. <so...@kl...>]

Hi everybody,

I had a working postfixadmin v 3.1 (sqlite3,nginx) installation until I upgraded from Debian 11 to 12 and along with this php 7.4 to php 8.2.    

Afterwards, I got a blank screen when hitting the postfixadmin login.php.

The error is: 
2023/06/12 18:51:11 [error] 3799#3799: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Array and string offset access syntax with curly braces is no longer supported in /var/www/mx989.example.int/functions.inc.php on line 697" while reading response header from upstream, client: 12.24.32.82, server: mx989.example.int, request: "GET /login.php HTTP/2.0", upstream: "fastcgi://unix:/run/php/php8.2-fpm.sock:", host: "mx989.example.int"

   for ($i = 0; $i < $j; ++$i) {
        switch ($string{$i}) {
            case '=':
            case '<':
            case '>':
            case ',':
            case '?':
            case '_':
                if ($iEncStart === false) {
                    $iEncStart = $i;



I could just upgrade from 3.1 to 3.3.13, but I don't know if this would mend the problem. Potentially it could if brackets are out of fashion :-0

Thx,
So.

Re: [Postfixadmin-devel] Backup MX with Postfixadmin

[<pos...@fo...>]

Answering over there...

On Wed, 1 Mar 2023, Michael Neuffer wrote:

> @Janfred I assume both your mail servers are accessing the same DB backend?
> or are you replicating the information somehow  from the primary to the 
> DB on the second mail server?
>
> @Janfred @Fongaboo: would you mind moving this discussion (back) to 
> Fongaboos posting on Github
> https://github.com/postfixadmin/postfixadmin/discussions/713#discussion-4904766 
> ?
> I personally love mailing lists, but most users are found there.
>
> I believe there is a number of users interested in this topic, since 
> this is one feature that postfixadmin is still lacking.
>
> Cheers
>   Mike
>
>
> On 3/1/23 01:00, Fongaboo wrote:
>>
>> So if you had an actual POP/IMAP box on the primary, how did it 
>> manifest in Postfixadmin on the secondary?
>>
>>
>> On Mon, 27 Feb 2023, Janfred wrote:
>>
>>> Hi,
>>>
>>> (I'm not a postfixadmin maintainer, just an interested user)
>>>
>>> I had a quite similar use case, actually with the additional 
>>> requirement that my mail servers were a proxy for some domains, so we 
>>> had to forward all incoming mail for specific domains to external hosts.
>>>
>>> For this usecase I patched posfixadmin manually, I have since created 
>>> a pull request, but would need to work on that to see if it would 
>>> work with the current version, my initial patch is some years old now.
>>>
>>> The basic idea was to introduce the possibility to define a primary 
>>> mail server for each domain and only the primary would then deliver 
>>> mails to local mailboxes.
>>> The secondary mail server(s) would behave to the outside world 
>>> exactly like the primary, including resolving aliases and doing 
>>> forwards, but every mail that needs to be delivered to a local 
>>> mailbox would get forwarded to the primary.
>>>
>>> If you have input on that, please feel free to reach out to me or 
>>> review the pull request.
>>> Any feedback is appreciated.
>>>
>>> Cheers,
>>> Janfred
>>>
>>> On 27.02.23 20:24, Fongaboo wrote:
>>>>
>>>> I have my primary mail server running postfix with MySQL backend and 
>>>> PostfixAdmin front-end. Works as advertised.
>>>>
>>>> For years my backup MX has just been configured to accept all mail 
>>>> for configured domains, and store-and-forward. But we know that 
>>>> hasn't been a good practice for a long time.
>>>>
>>>> I have finally set up my backup MX with the same 
>>>> postfix/MySQL/postfixadmin stack as the primary. I see you can check 
>>>> off Backup MX as an option in Domains.
>>>>
>>>> But I want to populate the backup MX with valid users so that 
>>>> anything else gets denied. How do you do that in a Postfixadmin 
>>>> setting?
>>>>
>>>> Do aliases have to be created pointing to the same destination as is 
>>>> set on the primary?
>>>>
>>>> How are addresses that are actual POP/IMAP mailboxes on the primary 
>>>> handled? Do you have to make an actual mailbox on the secondary? Or 
>>>> can you just make a matching alias? If the latter, what to point the 
>>>> aliases to?
>>>>
>>>> Should I be planning to migrate the entire MySQL database as-is to 
>>>> the secondary server, but then have some script that sets backupmx=1?
>>>>
>>>>
>>>> TIA
>>>>
>>>>
>>>> _______________________________________________
>>>> Postfixadmin-devel mailing list
>>>> Pos...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>>>
>>>
>>> _______________________________________________
>>> Postfixadmin-devel mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>>>
>>
>>
>> _______________________________________________
>> Postfixadmin-devel mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>
>
>
>
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>

Re: [Postfixadmin-devel] Backup MX with Postfixadmin

[Michael N. <ne...@ne...>]

@Janfred I assume both your mail servers are accessing the same DB backend?
or are you replicating the information somehow  from the primary to the 
DB on the second mail server?

@Janfred @Fongaboo: would you mind moving this discussion (back) to 
Fongaboos posting on Github
https://github.com/postfixadmin/postfixadmin/discussions/713#discussion-4904766 
?
I personally love mailing lists, but most users are found there.

I believe there is a number of users interested in this topic, since 
this is one feature that postfixadmin is still lacking.

Cheers
   Mike


On 3/1/23 01:00, Fongaboo wrote:
>
> So if you had an actual POP/IMAP box on the primary, how did it 
> manifest in Postfixadmin on the secondary?
>
>
> On Mon, 27 Feb 2023, Janfred wrote:
>
>> Hi,
>>
>> (I'm not a postfixadmin maintainer, just an interested user)
>>
>> I had a quite similar use case, actually with the additional 
>> requirement that my mail servers were a proxy for some domains, so we 
>> had to forward all incoming mail for specific domains to external hosts.
>>
>> For this usecase I patched posfixadmin manually, I have since created 
>> a pull request, but would need to work on that to see if it would 
>> work with the current version, my initial patch is some years old now.
>>
>> The basic idea was to introduce the possibility to define a primary 
>> mail server for each domain and only the primary would then deliver 
>> mails to local mailboxes.
>> The secondary mail server(s) would behave to the outside world 
>> exactly like the primary, including resolving aliases and doing 
>> forwards, but every mail that needs to be delivered to a local 
>> mailbox would get forwarded to the primary.
>>
>> If you have input on that, please feel free to reach out to me or 
>> review the pull request.
>> Any feedback is appreciated.
>>
>> Cheers,
>> Janfred
>>
>> On 27.02.23 20:24, Fongaboo wrote:
>>>
>>> I have my primary mail server running postfix with MySQL backend and 
>>> PostfixAdmin front-end. Works as advertised.
>>>
>>> For years my backup MX has just been configured to accept all mail 
>>> for configured domains, and store-and-forward. But we know that 
>>> hasn't been a good practice for a long time.
>>>
>>> I have finally set up my backup MX with the same 
>>> postfix/MySQL/postfixadmin stack as the primary. I see you can check 
>>> off Backup MX as an option in Domains.
>>>
>>> But I want to populate the backup MX with valid users so that 
>>> anything else gets denied. How do you do that in a Postfixadmin 
>>> setting?
>>>
>>> Do aliases have to be created pointing to the same destination as is 
>>> set on the primary?
>>>
>>> How are addresses that are actual POP/IMAP mailboxes on the primary 
>>> handled? Do you have to make an actual mailbox on the secondary? Or 
>>> can you just make a matching alias? If the latter, what to point the 
>>> aliases to?
>>>
>>> Should I be planning to migrate the entire MySQL database as-is to 
>>> the secondary server, but then have some script that sets backupmx=1?
>>>
>>>
>>> TIA
>>>
>>>
>>> _______________________________________________
>>> Postfixadmin-devel mailing list
>>> Pos...@li...
>>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>>
>>
>> _______________________________________________
>> Postfixadmin-devel mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>>
>
>
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

Re: [Postfixadmin-devel] Backup MX with Postfixadmin

[Fongaboo <pos...@fo...>]

So if you had an actual POP/IMAP box on the primary, how did it manifest 
in Postfixadmin on the secondary?


On Mon, 27 Feb 2023, Janfred wrote:

> Hi,
>
> (I'm not a postfixadmin maintainer, just an interested user)
>
> I had a quite similar use case, actually with the additional requirement that 
> my mail servers were a proxy for some domains, so we had to forward all 
> incoming mail for specific domains to external hosts.
>
> For this usecase I patched posfixadmin manually, I have since created a pull 
> request, but would need to work on that to see if it would work with the 
> current version, my initial patch is some years old now.
>
> The basic idea was to introduce the possibility to define a primary mail 
> server for each domain and only the primary would then deliver mails to local 
> mailboxes.
> The secondary mail server(s) would behave to the outside world exactly like 
> the primary, including resolving aliases and doing forwards, but every mail 
> that needs to be delivered to a local mailbox would get forwarded to the 
> primary.
>
> If you have input on that, please feel free to reach out to me or review the 
> pull request.
> Any feedback is appreciated.
>
> Cheers,
> Janfred
>
> On 27.02.23 20:24, Fongaboo wrote:
>> 
>> I have my primary mail server running postfix with MySQL backend and 
>> PostfixAdmin front-end. Works as advertised.
>> 
>> For years my backup MX has just been configured to accept all mail for 
>> configured domains, and store-and-forward. But we know that hasn't been a 
>> good practice for a long time.
>> 
>> I have finally set up my backup MX with the same postfix/MySQL/postfixadmin 
>> stack as the primary. I see you can check off Backup MX as an option in 
>> Domains.
>> 
>> But I want to populate the backup MX with valid users so that anything else 
>> gets denied. How do you do that in a Postfixadmin setting?
>> 
>> Do aliases have to be created pointing to the same destination as is set on 
>> the primary?
>> 
>> How are addresses that are actual POP/IMAP mailboxes on the primary 
>> handled? Do you have to make an actual mailbox on the secondary? Or can you 
>> just make a matching alias? If the latter, what to point the aliases to?
>> 
>> Should I be planning to migrate the entire MySQL database as-is to the 
>> secondary server, but then have some script that sets backupmx=1?
>> 
>> 
>> TIA
>> 
>> 
>> _______________________________________________
>> Postfixadmin-devel mailing list
>> Pos...@li...
>> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>
>
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel
>

Re: [Postfixadmin-devel] Backup MX with Postfixadmin

[Janfred <pos...@ri...>]

Hi,

(I'm not a postfixadmin maintainer, just an interested user)

I had a quite similar use case, actually with the additional requirement 
that my mail servers were a proxy for some domains, so we had to forward 
all incoming mail for specific domains to external hosts.

For this usecase I patched posfixadmin manually, I have since created a 
pull request, but would need to work on that to see if it would work 
with the current version, my initial patch is some years old now.

The basic idea was to introduce the possibility to define a primary mail 
server for each domain and only the primary would then deliver mails to 
local mailboxes.
The secondary mail server(s) would behave to the outside world exactly 
like the primary, including resolving aliases and doing forwards, but 
every mail that needs to be delivered to a local mailbox would get 
forwarded to the primary.

If you have input on that, please feel free to reach out to me or review 
the pull request.
Any feedback is appreciated.

Cheers,
Janfred

On 27.02.23 20:24, Fongaboo wrote:
> 
> I have my primary mail server running postfix with MySQL backend and 
> PostfixAdmin front-end. Works as advertised.
> 
> For years my backup MX has just been configured to accept all mail for 
> configured domains, and store-and-forward. But we know that hasn't been 
> a good practice for a long time.
> 
> I have finally set up my backup MX with the same 
> postfix/MySQL/postfixadmin stack as the primary. I see you can check off 
> Backup MX as an option in Domains.
> 
> But I want to populate the backup MX with valid users so that anything 
> else gets denied. How do you do that in a Postfixadmin setting?
> 
> Do aliases have to be created pointing to the same destination as is set 
> on the primary?
> 
> How are addresses that are actual POP/IMAP mailboxes on the primary 
> handled? Do you have to make an actual mailbox on the secondary? Or can 
> you just make a matching alias? If the latter, what to point the aliases 
> to?
> 
> Should I be planning to migrate the entire MySQL database as-is to the 
> secondary server, but then have some script that sets backupmx=1?
> 
> 
> TIA
> 
> 
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

[Postfixadmin-devel] Backup MX with Postfixadmin

[Fongaboo <pos...@fo...>]

I have my primary mail server running postfix with MySQL backend and 
PostfixAdmin front-end. Works as advertised.

For years my backup MX has just been configured to accept all mail for 
configured domains, and store-and-forward. But we know that hasn't been a 
good practice for a long time.

I have finally set up my backup MX with the same 
postfix/MySQL/postfixadmin stack as the primary. I see you can check off 
Backup MX as an option in Domains.

But I want to populate the backup MX with valid users so that anything 
else gets denied. How do you do that in a Postfixadmin setting?

Do aliases have to be created pointing to the same destination as is set 
on the primary?

How are addresses that are actual POP/IMAP mailboxes on the primary 
handled? Do you have to make an actual mailbox on the secondary? Or can 
you just make a matching alias? If the latter, what to point the aliases 
to?

Should I be planning to migrate the entire MySQL database as-is to the 
secondary server, but then have some script that sets backupmx=1?


TIA

Re: [Postfixadmin-devel] Use always a password prefix

[Lefteris T. <le...@sp...>]

On 18/11/2021 20:54, Lefteris Tsintjelis via Postfixadmin-devel wrote:
> Hi, is there a way to always use a password prefix in the database?
> 
> Example: "{PLAIN}password"

$CONF['encrypt'] = 'dovecot:PASSWORD-TYPE';
$CONF['dovecotpw'] = "/path/to/doveadm pw";

Dovecot must be installed in local machine for this to work but this 
seems to be the only good solution to always have and recognize any kind 
of prefixes in the password database.

[Postfixadmin-devel] Use always a password prefix

[Lefteris T. <le...@sp...>]

Hi, is there a way to always use a password prefix in the database?

Example: "{PLAIN}password"

Re: [Postfixadmin-devel] modify dovecot user/pass_queries to deliver to local aliases via dovecot submission, with postfixadmin/sqlite3 tables?

[PGNet D. <pgn...@gm...>]

as usual, the problem's seldom where you 1st look.

*NO* need for _any_ changes to queries.

the source of the problem was my local postfix submission instance's config -- connected to, as submission_relay_host, by dovecot.

it was doing exactly what I'd told it to do ... NOT expanding alias address mappings.

ensuring that

	no_address_mappings

is removed from

	receive_override_options=

, whether in main.cf, or in the instance's config in master.cf, does the trick.

i.e., pebkac.

[Postfixadmin-devel] modify dovecot user/pass_queries to deliver to local aliases via dovecot submission, with postfixadmin/sqlite3 tables?

[PGNet D. <pgn...@gm...>]

I run dovecot + postfix with postfixadmin/sqlite3

I'm set up for all/only virtual users.

All outbound mail submits via dovecot submission port.

My current dovecot pass/user db queries are

	password_query = \
	SELECT \
	username as user, \
	password, \
	'/data/vmail/%d/%n/Maildir' as userdb_home, \
	5000 as userdb_uid, \
	5000 as userdb_gid \
	FROM mailbox WHERE username = '%u' AND active = '1'

	user_query = \
	SELECT \
	'/data/vmail/%d/%n/Maildir' as home, \
	5000 AS uid, \
	5000 AS gid, \
	('dirsize:storage=' || quota) AS quota \
	FROM mailbox WHERE username = '%u' AND active = '1'

It works perfectly for real addresses.

I've setup an alias address, e.g.

	REAL:  rea...@ex...
	ALIAS: ali...@ex...

INBOUND email to the ALIAS address -- from the 'net, delivered from postfix via LMTP to dovecot backend -- works fine.

BUT any/all mail from local users TO the ALIAS addr fail at userDB lookup

	2020-10-20 12:26:54 lmtp(ali...@ex...)<rI49JP45j19D8QAA+IOfAw>: Debug: auth-master: userdb lookup(ali...@ex...): auth USER input:
	2020-10-20 12:26:54 lmtp(ali...@ex...)<rI49JP45j19D8QAA+IOfAw>: Debug: auth-master: userdb lookup(ali...@ex...): Userdb lookup failed

What mods are required to the password_query &/or user_query in order to FIX the local->aliasuser mail lookup and delivery ... and ideally not break the rest of delivery?

Re: [Postfixadmin-devel] custom field in domainview from other table?

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

Hello,

Am Mittwoch, 13. November 2019, 13:10:21 schrieb Przemysław Orzechowski:
> I'm trying to create a custom field visible in domain pane that gets
> its  value from different table
> 
> I created custom domain hook and it works if thew field is in domains
>  table but how do i get the field from custom table ?
> 
> The table has a field name which i can
> 
> This is the struct for a field in domains table
> 
> $struct['x_password_expiry'] =  pacol(0, 1, 1, 
> 'int','x_expire','x_password_expiry',"",[],0,1);
> 
> how can i get the qerry to go to custom table?
> 
> whith name substituted for domain in the query?

You'll need some additional parameters for pacol() ;-)

See for example how DomainHandler gets the number of existing aliases 
for a domain:

           'alias_count'       => pacol(0,          0,      1,      'vnum', ''                             , ''                                 , '', array(),
               /*not_in_db*/ 0,
               /*dont_write_to_db*/ 1,
               /*select*/ 'coalesce(__alias_count,0) - coalesce(__mailbox_count,0)  as alias_count',
               /*extrafrom*/ 'left join ( select count(*) as __alias_count, domain as __alias_domain from ' . table_by_key('alias') .
                             ' group by domain) as __alias on domain = __alias_domain'),

Your case is easier:
- "select" will ideally just be your field name (coalesce to prevent 
  NULL never hurts)
- for "extrafrom", you'll need to have a "join", but probably without 
  all the magic that does the counting in the example above

BTW: the "vnum" field type is meant for a "virtual" number coming from 
joins etc. - probably exactly what you need ;-)
(the comment for initStruct() in PFAHandler has a list of field types)

pacol() supports some more parameters, see the function definition in
functions.inc.php for details.


BTW: looking at your query and field names, I wonder if you noticed 
that we support a password expiry date in the latest version.


Regards,

Christian Boltz
-- 
Kinners, die guten alten Zeiten sind schon sehr, sehr lange vorbei.
Kohl wurde durch Merkel ersetzt und zwischendrin gab es den light-Kohl
von den Sozen inklusive grünem Beiwagen. ;) [Lars Müller in opensuse-de]

[Postfixadmin-devel] custom field in domainview from other table?

[Przemysław O. <Prz...@ma...>]

Hi

I'm trying to create a custom field visible in domain pane that gets its 
value from different table

I created custom domain hook and it works if thew field is in domains 
table but how do i get the field from custom table ?

The table has a field name which i can

This is the struct for a field in domains table

$struct['x_password_expiry'] =  pacol(0, 1, 1, 
'int','x_expire','x_password_expiry',"",[],0,1);

how can i get the qerry to go to custom table?

whith name substituted for domain in the query?

[Postfixadmin-devel] apt package maintenance for PostfixAdmin

[Dave N. <da...@da...>]

Hi guys,

I don't know if someone is maintaining the apt package for PostfixAdmin, 
but I'd be willing to take on the task if desired.

However, I know zero about apt package maintenance. But I'd be happy to 
study up on the subject. I downloaded The Debian Administrator's 
Handbook and had a look at the section on deb package maintenance. I'm 
pretty sure I could get up to speed on that, although not all the info 
I'd need to learn is there, so I'd need a little bit of mentoring in the 
beginning.

I did a bit of searching on duckduckgo, but didn't find much else of 
relevance. Maybe someone would have some useful links?

As regards the PostfixAdmin package, I wanted to install it on an ubuntu 
16.04 server recently. I saw that it was going to install apache2, 
whereas I'm going to be using nginx as a requisite of something else 
I'll be installing.

Is it really necessary to make apache2 an obligatory part of the 
software installed? I know it's not really a dependency as such, because 
i have PostfixAdmin being served happily by nginx on another server 
(Ubuntu 18.04).

I thought that it might be more logical to make the PostfixAdmin package 
more "Web-server-agnostic" and maybe install the files needed for both 
apache2 and for nginx in the right places, but without actually 
installing either Web server. But whatever... Maybe there are reasons 
I'm not aware of?

Anyway, I can also write great technical documentation (I'm a technical 
translator by trade [FR > EN]). Or is there some other way I can 
contribute to the project?

About me: I'm a Linux lover for more than 10 years, but just at 
"hobbyist" level. I escaped from Windows as soon as I found I could use 
VirtualBox to run it as a guest under Linux when I need to use MS Office 
and a couple of Windows-only tools I have to use professionally.

I lease a VPS and a bare-metal server, and I use Kubuntu on my laptops. 
I used to use Gnome (which I also love), but fell totally in love with 
KDE when I tried it out recently.

On my servers, I've had a lot of fun setting up quite a variety of the 
cool Web packages out there, following instructions in the projects' 
docs and the many how-to's to be found on the Internet.

I recently started a blog at https://dalek.zone

All best wishes,
Dave

Re: [Postfixadmin-devel] How to integrate PostfixAdmin with mail server installed using iRedMail

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

Hello,

Am Dienstag, 5. November 2019, 03:15:25 CET schrieb Dave Nelson:
> First of all, thank you for your work on PostfixAdmin, and sorry for
> writing to the dev list with an end user help request.

No problem ;-)

> I use PostfixAdmin happily on one mail server I have, but decided to
> use iRedMail to set up a second mail server.
> But the free version of iRedMail-Admin does not give me all the
> features I have in PostfixAdmin, which has all the features I need
> (particularly aliases).
> Does anyone have any experience/instructions to share on getting
> PostfixAdmin integrated with a mail server á la iRedMail?

My answer doesn't cover exactly what you asked for (and I don't know the 
iRedMail database layout) but I still think it's the best I can 
recommend:

IMHO the best way would be to export the existing data (domains, 
mailboxes, aliases) from iredmail (where "export" can mean anything 
between copy&paste from the web interface to taking a database dump).

Then use postfixadmin-cli (in a shell loop) to import everything into 
PostfixAdmin.

If the database layouts are "close enough" (or if you want to write some 
adventourous SQL [1]), you could in theory also do the migration using 
SQL queries, but unless you completely understand PostfixAdmin's 
database layout, this might cause some funny[tm] effects. That's why I 
recommend postfixadmin-cli - it will handle the technical details ;-)

BTW: If the passwords are hashed in the iRedMail database, there's a 
trick: temporarily configure PostfixAdmin to use plaintext passwords, do 
the import with postfixadmin-cli (using the hashed password as 
"cleartext"), and then change the PostfixAdmin config to the hashing 
method used by iRedMail to hash your passwords.


Regards,

Christian Boltz

[1] I still remember migrating mail addresses from Plesk to PostfixAdmin
    years ago, and still remember the pain ;-)
-- 
In asynchron-verteilten Umgebungen mußt Du gegen jede einzelne Regel
Deiner Datenbankvorlesung verstoßen. [Kris Köhntopp]

Re: [Postfixadmin-devel] How to integrate PostfixAdmin with mail server installed using iRedMail

[Michael N. <ne...@ne...>]

Hi Dave

On 11/5/19 3:15 AM, Dave Nelson wrote:
> Hello,
> First of all, thank you for your work on PostfixAdmin, and sorry for 
> writing to the dev list with an end user help request.
> I use PostfixAdmin happily on one mail server I have, but decided to 
> use iRedMail to set up a second mail server.
> But the free version of iRedMail-Admin does not give me all the 
> features I have in PostfixAdmin, which has all the features I need 
> (particularly aliases).
> Does anyone have any experience/instructions to share on getting 
> PostfixAdmin integrated with a mail server á la iRedMail?
> (I have a working installation with Postfix / Dovecot / Amavis / 
> Clamav / Spamassassin, working with Mariadb, virtual users, etc)
> Many grateful thanks for any help/advice, and all the best,

iRedMail was originally based on Postfixadmin, but as it was 
commercialized more and more, the iRedMail author made it intentionally 
more and more incompatible with Postfixadmin.

For a while I privately maintained patches to make it Postfixadmin 
compatible again, but then gave up on iRedMail.

I'm using https://github.com/hardware/mailserver/ now instead.

Hope this helps.

Cheers

   Mike

Re: [Postfixadmin-devel] How to integrate PostfixAdmin with mail server installed using iRedMail

[Dave N. <da...@da...>]

Sorry, I did forget to say that I'm using Ubuntu 16.04.
Dave

On 2019-11-05 04:15, Dave Nelson wrote:
> Hello,
> First of all, thank you for your work on PostfixAdmin, and sorry for
> writing to the dev list with an end user help request.
> I use PostfixAdmin happily on one mail server I have, but decided to
> use iRedMail to set up a second mail server.
> But the free version of iRedMail-Admin does not give me all the
> features I have in PostfixAdmin, which has all the features I need
> (particularly aliases).
> Does anyone have any experience/instructions to share on getting
> PostfixAdmin integrated with a mail server á la iRedMail?
> (I have a working installation with Postfix / Dovecot / Amavis /
> Clamav / Spamassassin, working with Mariadb, virtual users, etc)
> Many grateful thanks for any help/advice, and all the best,
> Dave
> 
> _______________________________________________
> Postfixadmin-devel mailing list
> Pos...@li...
> https://lists.sourceforge.net/lists/listinfo/postfixadmin-devel

[Postfixadmin-devel] How to integrate PostfixAdmin with mail server installed using iRedMail

[Dave N. <da...@da...>]

Hello,
First of all, thank you for your work on PostfixAdmin, and sorry for 
writing to the dev list with an end user help request.
I use PostfixAdmin happily on one mail server I have, but decided to use 
iRedMail to set up a second mail server.
But the free version of iRedMail-Admin does not give me all the features 
I have in PostfixAdmin, which has all the features I need (particularly 
aliases).
Does anyone have any experience/instructions to share on getting 
PostfixAdmin integrated with a mail server á la iRedMail?
(I have a working installation with Postfix / Dovecot / Amavis / Clamav 
/ Spamassassin, working with Mariadb, virtual users, etc)
Many grateful thanks for any help/advice, and all the best,
Dave

Re: [Postfixadmin-devel] Recovering admin password from sqlite / Postfixadmin 3.1

[Sophie L. <so...@kl...>]

> On 3 Jun 2019, at 18:58, Christian Boltz <pos...@cb...> wrote:
> 
> Hello,
> 
> Am Donnerstag, 23. Mai 2019, 23:29:26 CEST schrieb Sophie Loewenthal:
>> Some how I mislaid the admin password for my postfixadmin
>> adminsatrative user. No comments please :)
>> 
>> I’m using PostfixAdmin 3.1 with Sqlite 3.1
>> 
>> How could I reset or retrive this from with in the sqlite file?
> 
> It's in the admin table, but hopefully encrypted ;-)
> 
> The best way is to use setup.php to create a new superadmin. You'll need 
> your setup password, but if you don't remember it, setup.php has a "Lost 
> password" link to generate a new setup password hash.
> 
> You can then use this new superadmin to login, and change the password 
> of your existing admin using the "edit" link.
> 

Thanks Christian.  Problem now solved.