postfixadmin-devel Mailing List for PostfixAdmin
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
postfixadmin-devel — Postfix Admin development talk - users are also welcome
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(39) |
Nov
(29) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(5) |
Feb
|
Mar
(8) |
Apr
(8) |
May
|
Jun
(11) |
Jul
(21) |
Aug
(4) |
Sep
(9) |
Oct
(5) |
Nov
(25) |
Dec
(11) |
| 2009 |
Jan
(40) |
Feb
(16) |
Mar
(1) |
Apr
(46) |
May
(3) |
Jun
|
Jul
(1) |
Aug
(9) |
Sep
(9) |
Oct
(27) |
Nov
(35) |
Dec
(20) |
| 2010 |
Jan
(3) |
Feb
(2) |
Mar
(8) |
Apr
(1) |
May
(9) |
Jun
(8) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
(2) |
Nov
(12) |
Dec
(7) |
| 2011 |
Jan
(45) |
Feb
(11) |
Mar
(18) |
Apr
(15) |
May
(20) |
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
(8) |
Nov
|
Dec
(14) |
| 2012 |
Jan
(30) |
Feb
(36) |
Mar
(6) |
Apr
(32) |
May
(20) |
Jun
(5) |
Jul
(2) |
Aug
|
Sep
(4) |
Oct
|
Nov
(22) |
Dec
(1) |
| 2013 |
Jan
(13) |
Feb
(4) |
Mar
(70) |
Apr
(10) |
May
(6) |
Jun
(11) |
Jul
(1) |
Aug
(3) |
Sep
(2) |
Oct
(15) |
Nov
(4) |
Dec
(4) |
| 2014 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(2) |
| 2015 |
Jan
(1) |
Feb
(9) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(4) |
Feb
|
Mar
(10) |
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(13) |
| 2017 |
Jan
(1) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(3) |
| 2018 |
Jan
(2) |
Feb
|
Mar
(2) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
(10) |
Apr
|
May
(1) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(7) |
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2023 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sophie <so...@kl...> - 2023-06-18 17:13:37
|
>> 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. |
|
From: Sophie <so...@kl...> - 2023-06-18 16:51:10
|
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? |
|
From: Sophie L. <so...@kl...> - 2023-06-12 19:18:35
|
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.
|
|
From: <pos...@fo...> - 2023-03-01 15:37:55
|
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 > |
|
From: Michael N. <ne...@ne...> - 2023-03-01 08:23:29
|
@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 |
|
From: Fongaboo <pos...@fo...> - 2023-03-01 00:00:51
|
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 > |
|
From: Janfred <pos...@ri...> - 2023-02-27 20:36:29
|
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 |
|
From: Fongaboo <pos...@fo...> - 2023-02-27 19:42:40
|
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 |
|
From: Lefteris T. <le...@sp...> - 2021-11-19 06:16:29
|
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.
|
|
From: Lefteris T. <le...@sp...> - 2021-11-18 19:10:27
|
Hi, is there a way to always use a password prefix in the database?
Example: "{PLAIN}password"
|
|
From: PGNet D. <pgn...@gm...> - 2020-10-21 01:58:30
|
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. |
|
From: PGNet D. <pgn...@gm...> - 2020-10-20 19:36:25
|
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?
|
|
From: Christian B. <pos...@cb...> - 2019-11-24 21:07:17
|
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]
|
|
From: Przemysław O. <Prz...@ma...> - 2019-11-13 15:44:37
|
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? |
|
From: Dave N. <da...@da...> - 2019-11-06 23:29:23
|
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 |
|
From: Christian B. <pos...@cb...> - 2019-11-06 21:59:02
|
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]
|
|
From: Michael N. <ne...@ne...> - 2019-11-05 06:22:19
|
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 |
|
From: Dave N. <da...@da...> - 2019-11-05 02:35:37
|
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 |
|
From: Dave N. <da...@da...> - 2019-11-05 02:32:00
|
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 |
|
From: Sophie L. <so...@kl...> - 2019-06-03 19:00:00
|
> 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. |
|
From: Christian B. <pos...@cb...> - 2019-06-03 17:16:35
|
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. Regards, Christian Boltz -- > > My calendar shows May 12th to be a Friday, not a Thursday? > I meant 11th ;-(. With all the delays, perhaps mentioning the year would also be a good idea. ;-) [> Andreas Jaeger and houghi in opensuse] |
|
From: Sophie L. <so...@kl...> - 2019-05-23 21:45:20
|
Hi, 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? Best, So. |
|
From: Danny H. <dho...@gm...> - 2019-03-28 23:49:27
|
Hello,
Not a problem, I fully understand, and i am gratefull you are helping
me :)
It is a real headscratcher. And i am in for some crazy ideas :)
On Wed, 2019-03-27 at 22:52 +0100, Christian Boltz wrote:
> Hello,
>
> sorry for the late reply, but I'm running out of ideas...
>
> That said, maybe we should switch to the crazy ideas ;-)
>
> Am Dienstag, 12. März 2019, 00:23:54 CET schrieb Danny Houtworm:
> > On Mon, 2019-03-11 at 23:10 +0100, Christian Boltz wrote:
> > > This indicates that require_once() can read config.inc.php.
> > >
> > > To confirm that, please introduce a syntax error in
> > > config.inc.php,
> > > and
> > > then run setup.php on the commandline again. You should see a
> > > message
> > > about that syntax error.
> >
> > I added some gibberish to the config.inc.php file and i indeed get
> > a
> > Syntax errors :)
> >
> > [houtworm@server ~]$ sudo -u http php
> > /usr/share/webapps/postfixAdmin/public/setup.php
> > PHP Parse error: syntax error, unexpected 'ik' (T_STRING) in
> > /usr/share/webapps/postfixAdmin/config.inc.php on line 17
> > [houtworm@server ~]$
>
> OK, so config.inc.php is readable and gets included, and "only" the
> check fails for some strange reason.
>
> Repeat that test with config.local.php to ensure it also gets used.
>
I repeated it twice, It gives an error at the first following setting,
Maybe this is a problem somehow Line 32 and 39 where these 2 lines at
that moment. with the non local config file it gave a syntax error for
the line i typed the gibberish, This does not match up, maybe something
is wrong here.
32 global $CONF;
39 $CONF['configured'] = true;
But i think those are alright. Not sure why it gives a syntax error
[houtworm@server ~]$ sudo nano
/usr/share/webapps/postfixAdmin/config.inc.php
[houtworm@server ~]$ sudo -u http php
/usr/share/webapps/postfixAdmin/public/setup.php
PHP Parse error: syntax error, unexpected 'global' (T_GLOBAL) in
/usr/share/webapps/postfixAdmin/config.inc.php on line 32
[houtworm@server ~]$ sudo nano
/usr/share/webapps/postfixAdmin/config.inc.php
[houtworm@server ~]$ sudo -u http php
/usr/share/webapps/postfixAdmin/public/setup.php
PHP Parse error: syntax error, unexpected '$CONF' (T_VARIABLE) in
/usr/share/webapps/postfixAdmin/config.inc.php on line 39
[houtworm@server ~]$
> > > One idea I have is the way how setup.php checks for
> > > config.local.php:
> > > $file_config = file_exists(realpath("./../config.inc.php"));
> > >
> > > $file_local_config =
> > >
> > > file_exists(realpath("./../config.local.php"));
> > >
> > > Note the realpath() call, which means resolving all symlinks.
> > > Does the path /usr/share/webapps/postfixAdmin/public/ include any
> > > symlinked part?
> >
> > In /postfixAdmin only .htaccess is symlinked
> >
> > in /public only password-change.php and password-recover.php are
> > symlinked
> >
> > The config files where both symlinked because i copied local from
> > inc,
> > i removed both and made new files for them to ensure they are not
> > symlinked. I did this before but it did not help, Maybe the inc
> > file
> > needs to be symlinked?
>
> There's no requirement that config.*.php has to be a symlink (but
> having
> them as symlink can be useful so that you can have the actual files
> in
> /etc/postfixadmin/ - that's nice for distro packaging and being FHS
> compliant)
>
> > > If in doubt, add
> > >
> > > echo "\n\n file_config: $file_config local
> > > $file_local_config
> > > \n\n"
> > > to setup.php (directly under the lines quoted above) and check
> > > the
> > > result.
> >
> > I edited it like this
> > /usr/share/webapps/postfixAdmin/public/setup.php
> >
> > 56 $file_config = file_exists(realpath("./../config.inc.php"));
> > 57 $file_local_config =
> > file_exists(realpath("./../config.local.php")); 58 echo "\n\n
> > file_config: $file_config local $file_local_config 59 > \n\n";
> > 60 $error = 0;
> >
> > terminal output
> >
> > [houtworm@server ~]$ sudo -u http php
> > /usr/share/webapps/postfixAdmin/public/setup.php
> ...
> > file_config: local
>
> So both variables are False/empty which means that file_exists()
> thinks
> the files don't exist.
>
> Let's try some more debugging code (add it at the same place):
>
> echo "\n realpath of config files:\n";
> echo realpath("./../config.inc.php");
> echo "\n";
> echo realpath("./../config.local.php");
>
> > Then finding that file is the only thing that matters, Very strange
> > it
> > does not see it.
>
> Well, the fact that introducing a syntax error triggers an error
> means
> that the code finds the config files, but the checks in setup.php
> don't.
>
> There might be a crazy "fix": adjust setup.php and change
>
> $file_config = file_exists(realpath("./../config.inc.php"));
> $file_local_config = file_exists(realpath("./../config.local.php"));
>
> to
>
> # fake test results
> $file_config = True;
> $file_local_config = True;
>
> This will obviously avoid the test failure, but since we know that
> the
> config files get included successfully, it's worth a try ;-)
I think this fixed it :)
[houtworm@server ~]$ sudo -u http php
/usr/share/webapps/postfixAdmin/public/setup.php
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" type="text/css" href="css/default.css" />
<title>Postfix Admin - PHP Notice: Undefined index: HTTP_HOST in
/usr/share/webapps/postfixAdmin/templates/header.php on line 22
</title>
</head>
<body>
<div id="login_header">
<img id="login_header_logo" src="images/logo-default.png" />
</div>
<div class='setup'>
<h2>Postfix Admin Setup Checker</h2>
<p>Running software:
<ul>
realpath of config files:
<li>PHP version 7.3.3</li>
</ul><p>Checking for dependencies:
<ul>
<li>Magic Quotes: Disabled - OK</li>
<li>Depends on: presence config.inc.php - OK</li>
<li>Checking $CONF['configured'] - OK
<li>Depends on: presence config.local.php - OK</li>
<li>Depends on: MySQL 4.1 - OK
</li><li>Depends on: PostgreSQL - OK
<br>(change the database_type to 'pgsql' in config.local.php if you
want to use PostgreSQL)
</li><li>Testing database connection (using mysqli) -
OK</li><li>Depends on: session - OK</li>
<li>Depends on: pcre - OK</li>
<li>Depends on: multibyte string - OK</li>
<li>Depends on: IMAP functions - OK</li>
</ul><p>Everything seems fine... attempting to create/update database
structure</p>
<p>Database is up to date: 1840/0 </p>
<div class="standout"></div>
<div id="edit_form">
<form name="setuppw" method="post" action="setup.php">
<input type="hidden" name="form" value="setuppw" />
<table>
<tr>
<td colspan="3"><h3>Change setup password</h3></td>
</tr>
<tr>
<td><label for="setup_password">Setup password</label></td>
<td><input class="flat" type="password" name="setup_password"
value="" /></td>
<td></td>
</tr>
<tr>
<td><label for="setup_password2">Setup password
(again)</label></td>
<td><input class="flat" type="password" name="setup_password2"
value="" /></td>
<td></td>
</tr>
<tr>
<td colspan="3" class="hlp_center"><input class="button"
type="submit" name="submit" value="Generate password hash" /></td>
</tr>
</table>
</form>
</div>
<b>Since version 2.3 there is no requirement to delete
setup.php!</b><br />
<b>Check the config.inc.php file for any other settings that you
might need to change!<br />
</div>
</body>
</html>
[houtworm@server ~]$
So that looks great :)
But i still get a white page So i guess the PHP error was not the only
problem Are there more vital PHP pages that need to be able to get
loaded?
Maybe it lies in the Nginx config now, Maybe even in the postfix or
dovecot settings, i had some updates, Maybe i should try to run the
tutorial again just in case?
Anyway, we have some progress :)
Greets
Danny
>
>
> Regards,
>
> Christian Boltz
|
|
From: Christian B. <pos...@cb...> - 2019-03-27 21:52:50
|
Hello,
sorry for the late reply, but I'm running out of ideas...
That said, maybe we should switch to the crazy ideas ;-)
Am Dienstag, 12. März 2019, 00:23:54 CET schrieb Danny Houtworm:
> On Mon, 2019-03-11 at 23:10 +0100, Christian Boltz wrote:
> > This indicates that require_once() can read config.inc.php.
> >
> > To confirm that, please introduce a syntax error in config.inc.php,
> > and
> > then run setup.php on the commandline again. You should see a
> > message
> > about that syntax error.
>
> I added some gibberish to the config.inc.php file and i indeed get a
> Syntax errors :)
>
> [houtworm@server ~]$ sudo -u http php
> /usr/share/webapps/postfixAdmin/public/setup.php
> PHP Parse error: syntax error, unexpected 'ik' (T_STRING) in
> /usr/share/webapps/postfixAdmin/config.inc.php on line 17
> [houtworm@server ~]$
OK, so config.inc.php is readable and gets included, and "only" the
check fails for some strange reason.
Repeat that test with config.local.php to ensure it also gets used.
> > One idea I have is the way how setup.php checks for
> > config.local.php:
> > $file_config = file_exists(realpath("./../config.inc.php"));
> >
> > $file_local_config =
> >
> > file_exists(realpath("./../config.local.php"));
> >
> > Note the realpath() call, which means resolving all symlinks.
> > Does the path /usr/share/webapps/postfixAdmin/public/ include any
> > symlinked part?
>
> In /postfixAdmin only .htaccess is symlinked
>
> in /public only password-change.php and password-recover.php are
> symlinked
>
> The config files where both symlinked because i copied local from inc,
> i removed both and made new files for them to ensure they are not
> symlinked. I did this before but it did not help, Maybe the inc file
> needs to be symlinked?
There's no requirement that config.*.php has to be a symlink (but having
them as symlink can be useful so that you can have the actual files in
/etc/postfixadmin/ - that's nice for distro packaging and being FHS
compliant)
> > If in doubt, add
> >
> > echo "\n\n file_config: $file_config local $file_local_config
> > \n\n"
> > to setup.php (directly under the lines quoted above) and check the
> > result.
>
> I edited it like this /usr/share/webapps/postfixAdmin/public/setup.php
>
> 56 $file_config = file_exists(realpath("./../config.inc.php"));
> 57 $file_local_config =
> file_exists(realpath("./../config.local.php")); 58 echo "\n\n
> file_config: $file_config local $file_local_config 59 > \n\n";
> 60 $error = 0;
>
> terminal output
>
> [houtworm@server ~]$ sudo -u http php
> /usr/share/webapps/postfixAdmin/public/setup.php
...
> file_config: local
So both variables are False/empty which means that file_exists() thinks
the files don't exist.
Let's try some more debugging code (add it at the same place):
echo "\n realpath of config files:\n";
echo realpath("./../config.inc.php");
echo "\n";
echo realpath("./../config.local.php");
> Then finding that file is the only thing that matters, Very strange it
> does not see it.
Well, the fact that introducing a syntax error triggers an error means
that the code finds the config files, but the checks in setup.php don't.
There might be a crazy "fix": adjust setup.php and change
$file_config = file_exists(realpath("./../config.inc.php"));
$file_local_config = file_exists(realpath("./../config.local.php"));
to
# fake test results
$file_config = True;
$file_local_config = True;
This will obviously avoid the test failure, but since we know that the
config files get included successfully, it's worth a try ;-)
Regards,
Christian Boltz
--
For patterns and products, this is - as we now learned - wrong and
confusing. (We will probably have more such learning effects in the
future ... ;-})
[Klaus Kaempf in https://bugzilla.novell.com/show_bug.cgi?id=198379]
|
|
From: Danny H. <dho...@gm...> - 2019-03-11 23:24:05
|
Hello again
On Mon, 2019-03-11 at 23:10 +0100, Christian Boltz wrote:
>
> > <li><b>Error: Depends on: presence config.inc.php - NOT FOUND
>
> That's... interesting[tm].
>
> It's especially interesting because setup.php starts with
> require_once(dirname(__FILE__).'/common.php');
> which has
> require_once(dirname(__FILE__) . '/../common.php');
> and that one has
> $incpath = dirname(__FILE__);
> if (!is_file("$incpath/config.inc.php")) {
> die("config.inc.php is missing!");
> }
> require_once("$incpath/config.inc.php");
>
> so setup.php should fail _before_ printing the header, and before
> printing the failure about finding config.inc.php.
>
> This indicates that require_once() can read config.inc.php.
>
> To confirm that, please introduce a syntax error in config.inc.php,
> and
> then run setup.php on the commandline again. You should see a
> message
> about that syntax error.
I added some gibberish to the config.inc.php file and i indeed get a
Syntax errors :)
[houtworm@server ~]$ sudo -u http php
/usr/share/webapps/postfixAdmin/public/setup.php
PHP Parse error: syntax error, unexpected 'ik' (T_STRING) in
/usr/share/webapps/postfixAdmin/config.inc.php on line 17
[houtworm@server ~]$
> > The location in setup.php is set to /../config.local.php also the
> > inc
> > one
> > The files are there 100% they are owned by http:http and the
> > permissions are 644
> >
> > [houtworm@server ~]$ cd /usr/share/webapps/postfixAdmin/
> > [houtworm@server postfixAdmin]$ ls
> > common.php config.local.php languages public template
> > s_c
> > composer.json configs lib README.md
> > composer.lock functions.inc.php model scripts
> > config.inc.php index.php phpunit.xml templates
> > [houtworm@server postfixAdmin]$
>
> Looks good.
Great :)
>
> One idea I have is the way how setup.php checks for config.local.php:
>
> $file_config = file_exists(realpath("./../config.inc.php"));
>
> $file_local_config =
> file_exists(realpath("./../config.local.php"));
>
> Note the realpath() call, which means resolving all symlinks.
> Does the path /usr/share/webapps/postfixAdmin/public/ include any
> symlinked part?
In /postfixAdmin only .htaccess is symlinked
in /public only password-change.php and password-recover.php are
symlinked
The config files where both symlinked because i copied local from inc,
i removed both and made new files for them to ensure they are not
symlinked. I did this before but it did not help, Maybe the inc file
needs to be symlinked?
> If in doubt, add
> echo "\n\n file_config: $file_config local $file_local_config
> \n\n"
> to setup.php (directly under the lines quoted above) and check the
> result.
I edited it like this /usr/share/webapps/postfixAdmin/public/setup.php
56 $file_config = file_exists(realpath("./../config.inc.php"));
57 $file_local_config = file_exists(realpath("./../config.local.php"));
58 echo "\n\n file_config: $file_config local $file_local_config
59 > \n\n";
60 $error = 0;
terminal output
[houtworm@server ~]$ sudo -u http php
/usr/share/webapps/postfixAdmin/public/setup.php
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" type="text/css" href="css/default.css" />
<title>Postfix Admin - PHP Notice: Undefined index: HTTP_HOST in
/usr/share/webapps/postfixAdmin/templates/header.php on line 22
</title>
</head>
<body>
<div id="login_header">
<img id="login_header_logo" src="images/logo-default.png" />
</div>
<div class='setup'>
<h2>Postfix Admin Setup Checker</h2>
<p>Running software:
<ul>
file_config: local
>
<li>PHP version 7.3.3</li>
</ul><p>Checking for dependencies:
<ul>
<li>Magic Quotes: Disabled - OK</li>
<li><b>Error: Depends on: presence config.inc.php - NOT FOUND</b><br
/></li>
Create the file, and edit as appropriate (e.g. select database type
etc)<br />For example:<br />
<code><pre>cp config.inc.php.sample config.inc.php</pre></code>
<li><b>Warning: config.local.php - NOT FOUND</b><br /></li>
It's Recommended to store your own settings in config.local.php instead
of editing config.inc.php<br />Create the file, and edit as appropriate
(e.g. select database type etc)<br /><li>Depends on: MySQL 4.1 - OK
<br>(change the database_type to 'mysqli' in config.local.php if you
want to use MySQL)
</li><li>Depends on: PostgreSQL - OK
<br>(change the database_type to 'pgsql' in config.local.php if you
want to use PostgreSQL)
</li><li>Depends on: session - OK</li>
<li>Depends on: pcre - OK</li>
<li>Depends on: multibyte string - OK</li>
<li>Depends on: IMAP functions - OK</li>
</ul><p><b>Please fix the errors listed above.</b></p></div>
</body>
</html>
[houtworm@server ~]$
> Also note that there's a fallback check for config.local.php:
>
> // Fall back to looking in /etc/postfixadmin for
> config.local.php
> // (Debian etc)
> if (!$file_local_config && is_dir('/etc/postfixadmin')) {
> $file_local_config = file_exists(
> '/etc/postfixadmin/config.local.php');
> }
>
> which can mean
> a) try to create a /etc/postfixadmin/config.local.php and check if
> setup.php finds it
> b) make sure your PHP open_basedir allows access to
> /etc/postfixadmin/
I made the /etc/postfixadmin/ directory and copied config.local.php
into it but the output is still the same
[houtworm@server ~]$ sudo -u http php
/usr/share/webapps/postfixAdmin/public/setup.php
[sudo] password for houtworm:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<link rel="stylesheet" type="text/css" href="css/default.css" />
<title>Postfix Admin - PHP Notice: Undefined index: HTTP_HOST in
/usr/share/webapps/postfixAdmin/templates/header.php on line 22
</title>
</head>
<body>
<div id="login_header">
<img id="login_header_logo" src="images/logo-default.png" />
</div>
<div class='setup'>
<h2>Postfix Admin Setup Checker</h2>
<p>Running software:
<ul>
file_config: local
>
<li>PHP version 7.3.3</li>
</ul><p>Checking for dependencies:
<ul>
<li>Magic Quotes: Disabled - OK</li>
<li><b>Error: Depends on: presence config.inc.php - NOT FOUND</b><br
/></li>
Create the file, and edit as appropriate (e.g. select database type
etc)<br />For example:<br />
<code><pre>cp config.inc.php.sample config.inc.php</pre></code>
<li><b>Warning: config.local.php - NOT FOUND</b><br /></li>
It's Recommended to store your own settings in config.local.php instead
of editing config.inc.php<br />Create the file, and edit as appropriate
(e.g. select database type etc)<br /><li>Depends on: MySQL 4.1 - OK
<br>(change the database_type to 'mysqli' in config.local.php if you
want to use MySQL)
</li><li>Depends on: PostgreSQL - OK
<br>(change the database_type to 'pgsql' in config.local.php if you
want to use PostgreSQL)
</li><li>Depends on: session - OK</li>
<li>Depends on: pcre - OK</li>
<li>Depends on: multibyte string - OK</li>
<li>Depends on: IMAP functions - OK</li>
</ul><p><b>Please fix the errors listed above.</b></p></div>
</body>
</html>
[houtworm@server ~]$
> > My Database is
> ... irrelevant, at least until the problems with config.inc.php and
> config.local.php are solved ;-)
Good to know, i won't look into that untill this is fixed :)
> > Nginx Setup: https://paste.ee/p/IE2na
> > Local and Inc config: https://paste.ee/p/VcMUQ
> >
> > I hope there is an obvious mistake here somewhere
>
> I checked them, and didn't see an obvious error.
> That's not surprising because the syntax check already confirmed
> that
> your config.*.php is ok, at least the first half of setup.php
> worked,
> and the nginx config is irrelevant when running php on the command
> line.
Then finding that file is the only thing that matters, Very strange it
does not see it.
If i can provide any more information please let me know,
Thanks,
Danny
> Regards,
>
> Christian Boltz
|
15 messages has been excluded from this view by a project administrator.