set-permissions fails: how to fix and/or manual set correct permissions?

2018-09-30 Thread Max Mustermann
platform: Entware (OpenWRT based = router firmware) -> minimal: no SElinux, no appArmor, readme_directory = no, etc. environment: root user name is renamed # postconf -n command_directory = /opt/sbin compatibility_level = 2 config_directory = /opt/etc/postfix daemon_directory = /opt/libexec/postf

Invalid address is accepted by postfix

2018-09-30 Thread jcdole
Hello. After reading it seems that a valid local-part address is : /The local-part of the email address may use any of these ASCII characters: *) uppercase and lowercase Latin letters A to Z and a to z; digits 0 to 9; special characters !#$%&'*+-/=?^_`{|}~; *) dot ., provid

Re: set-permissions fails: how to fix and/or manual set correct permissions?

2018-09-30 Thread Wietse Venema
Max Mustermann: > # postfix set-permissions > find: unknown user root WTF? > # ls -lah /opt/sbin/postdrop > -rwxr-xr-x1 NewRootUser root 246.8K Postfix requires a standard environment, with a user called "root" who has super-user privileges, with UID zero and GID zero. I don't expect

Re: Invalid address is accepted by postfix

2018-09-30 Thread jcdole
>From documentation : postconf.5.html#resolve_dequoted_address /resolve_dequoted_address (default: yes) Resolve a recipient address safely instead of correctly, by looking inside quotes. By default, the Postfix address resolver does not quote the address localpart as per RFC 822, so that

Re: Invalid address is accepted by postfix

2018-09-30 Thread Wietse Venema
jcdole: > >From documentation : postconf.5.html#resolve_dequoted_address > > /resolve_dequoted_address (default: yes) > > Resolve a recipient address safely instead of correctly, by looking > inside quotes. > > By default, the Postfix address resolver does not quote the address > localpa

Re: set-permissions fails: how to fix and/or manual set correct permissions?

2018-09-30 Thread Max Mustermann
How should I know that postfix requires the super-user to have "root" as name? I don't see this information in the README, neither in the (file system) requirements. Or can't I read? On 30-09-18 18:24, Wietse Venema wrote: Max Mustermann: # postfix set-permissions find: unknown user root

Re: set-permissions fails: how to fix and/or manual set correct permissions?

2018-09-30 Thread Viktor Dukhovni
> On Sep 30, 2018, at 1:26 PM, Max Mustermann wrote: > > How should I know that postfix requires the super-user to have "root" as name? > > I don't see this information in the README, neither in the (file system) > requirements. Some assumptions are inevitably so basic that they're not written

Re: set-permissions fails: how to fix and/or manual set correct permissions?

2018-09-30 Thread Max Mustermann
Usually it's a mistake to test if the user is root. POSIX does not even require a root user. source: On 30-09-18 19:36, Viktor Dukhovni wrote: Postfix documentation is not the POSIX specification. On systems that devi

Re: set-permissions fails: how to fix and/or manual set correct permissions?

2018-09-30 Thread Viktor Dukhovni
> On Sep 30, 2018, at 2:51 PM, Max Mustermann wrote: > > Usually it's a mistake to test if the user is root. > POSIX does not even require a root user. This is not a productive discussion... The Postfix deployment scripts reasonably expect to be able to chown files to "root", or check whether t

Re: any api to read logs ?

2018-09-30 Thread Илья Шипицин
вс, 30 сент. 2018 г. в 4:40, Wietse Venema : > Wietse: > > > Open a web search engine, ask for for 'logfile analysis tools'. > > ???: > > logfile analys is good for human, it is not rest api. > > I did search already > > Here is an idea: combine log analysis with a web API. End of problem