tux12 | i don't think so ham5urg because that file also exists on debian systems. | 00:03 |
---|---|---|
ham5urg | tux12, yeah, looks like a higher level managing instance of ifupdown. | 00:04 |
tux12 | # Configuration for networking init script being run during the boot sequence // says the first comment in the file | 00:05 |
Guest31 | hi im new to Devuan . i couldnt find Devuan Chimera's default system init. What is it? | 07:09 |
Guest31 | is it sysvinit | 07:09 |
onefang | Correct. | 07:10 |
Guest31 | ty | 07:10 |
Wonka | Setting up polkitd (121+compat0.1-6devuan1) ... | 17:06 |
Wonka | Failed to open 'polkitd.conf', ignoring: No such file or directory | 17:06 |
Wonka | debian's polkitd_121+compat0.1-6_amd64.deb contains /usr/lib/sysusers.d/polkitd.conf, polkitd_121+compat0.1-6devuan1_amd64.deb doesn't. | 17:07 |
u-amarsh04 | I had this problem Wonka | 17:07 |
Wonka | I have systemd-standalone-sysusers installed, that's why it fails | 17:07 |
Wonka | it's a dependency of stunnel4... | 17:07 |
u-amarsh04 | yes, I found the same thing | 17:07 |
Wonka | without systemd-standalone-sysusers it would work | 17:08 |
u-amarsh04 | for the same reason because I had stunnel installed | 17:08 |
Wonka | likely fix: don't throw that file out | 17:08 |
u-amarsh04 | https://bugs.devuan.org/cgi/bugreport.cgi?bug=717 | 17:08 |
Wonka | ah, nice. | 17:10 |
Wonka | I extracted the polkitd.conf from polkitd_121+compat0.1-6_amd64.deb, ran 'dpkg --configure -a', and it worked. | 17:10 |
u-amarsh04 | I was a bit mystified why systemd-standalone-sysusers was not mentioned in the dependencies of polkitd even as a suggests/enhanced by | 17:12 |
Wonka | I have no idea if changing the postinst script to unconditionally act as if systemd-sysusers was absent wouldn't be a good fix too... | 17:16 |
Wonka | but using it while not providing the necessary config file is certainly wrong :) | 17:16 |
u-amarsh04 | it also struck me that the code path in the postinstallation script which used the program from systemd-standalone-sysusers actually worked | 17:19 |
u-amarsh04 | I have several bugs opened against exim4 in Debian for not properly documenting /etc/mailname | 17:20 |
u-amarsh04 | I figured by documenting the issue in the bug reports at least other people would find my solution | 17:21 |
u-amarsh04 | "localhost" without the quotes is a valid /etc/mailname entry | 17:21 |
u-amarsh04 | correction, the code path in the installation script used if systemd-sysusers was found wasn't properly tested | 17:25 |
Wonka | yep | 17:27 |
fatalerrors | hi everyone | 21:40 |
fatalerrors | i need help on something i thought was a common practice and can't find anything using search engines, even evil one | 21:42 |
fatalerrors | i need to create a postfix configuration for local network only to send all mails received by local network server *@*.domain.net to a public mail server with address system@domain.net | 21:44 |
amesser | fatalerrors, so relay only? | 22:15 |
fatalerrors | amesser: yes | 22:17 |
amesser | you could setup a transport_map to do this is. in your main.cf add something like "transport_maps = hash:/ets/postfix/transport" | 22:17 |
fatalerrors | the relay can only receive system mail from local network | 22:17 |
amesser | then create /etc/postfix/transport with content: | 22:17 |
amesser | .domain.net smtp:[<my-mail-server-address-here>] | 22:18 |
amesser | run postmap /etc/postfix/transport | 22:18 |
amesser | that should be enough. postfix will consult this file to choose a transport for destination address. ah, i see you'll need rewrite also. | 22:19 |
amesser | hmm. | 22:19 |
fatalerrors | rewrite? | 22:23 |
fatalerrors | i don't know that | 22:23 |
fatalerrors | is it like rewriting the sender address? | 22:23 |
amesser | not sure what your public mail server will accept. At least the envelope of the mails must be changed to "system@domain.net" | 22:24 |
amesser | I think you can resolf thie by having another hash map for postfix option "virtual_alias_maps" | 22:25 |
fatalerrors | yes the public mail server will not accept anything else for security/spam reason, this is what caused my trouble on the first place | 22:25 |
fatalerrors | cause the previous mail server was not secure enough | 22:26 |
fatalerrors | so my home made servers was rejected, but i could influence to adopt mailcow:dockerized insted of gmail or microsoft | 22:28 |
fatalerrors | it was hard fight | 22:28 |
amesser | So then you need two steps. First your mail envelope and headers need to be rewritten such that "To" becomes "system@domain.net" | 22:28 |
fatalerrors | yes exactly | 22:28 |
fatalerrors | but i don't know how to do | 22:29 |
amesser | I think this could be achieved using "recipient_canonical_maps" in postfix | 22:29 |
fatalerrors | ok i'll look forward | 22:29 |
amesser | Just create a hashmap for this like above. See https://www.postfix.org/canonical.5.html for the map format most likely one line. | 22:33 |
amesser | Another thing to do this could also be: https://www.postfix.org/ADDRESS_REWRITING_README.html#generic | 22:33 |
fatalerrors | thanks i read a lot of usefull things thanks to you amesser | 22:38 |
amesser | happy to help | 22:39 |
fatalerrors | thank you that's exactly what i missed | 22:39 |
fatalerrors | search engines sucks ;) | 22:40 |
amesser | yes, i tend to crawl through "man postconf" by hand. A lot of possibilities, however. | 22:41 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!