Recent content by das1996

Using the lxc.mount.entry method in unpriveldged containers, do you still need to do the gui/uid remapping? Here's a snippet of my container.conf. IIRC, i needed to pass gui/uid of 864 and 865 to get permissions to work correctly. mp0: /mnt/pve/nas1-scratch,mp=/mnt/scratch mp1...

^^Ran into this myself ( finger print change). To deal with the fqdn instead of the pbe ip, create a dns entry in your dns resolver. ie. pbe.domain.com > {internal ip of pbe server} pbe.domain.com > 192.168.1.250 Lets encrypt should continue to work as it's likely using dns validation with...

Sorry, no option to edit the op available.

This was eventually fixed in one of the PPB updates. Currently running PPBE 4.8.0 and no disconnect issues. However, I do periodically see communications restored in the ppb event log. I'd surmise to say either the software or ups is buggy. Using similar ups on a windows box with same...

@ukro Did you ever figure out how to get the source ip forwarded to the mail server behind PMG?

SUCCESS! I understand now (more or less). I didn't realize that white/black list was tied to spam checking rules. I don't recall seeing it in the documentation either. In testing, the messages are indeed blocked, but not rejected/bounced at smtp level. Can that be implemented? Similar to how...

Start with the last. Everything under mail filter/rules (at the top) is all turned off. I see something in there about default-accept, but mentioned, all rules are disabled. Only the admin/user blacklist is defined. Which brings back the original question; under what circumstances is the...

I must be doing something wrong then as its still letting messages through. user1@domain.com is a mailbox on the local server sitting behind PMG. *@aol.com is what should be blocked. Test message from an aol account gets accepted and delivered.

Sorry, still unclear. Define internal recipient. IE, PMG is configured to relay messages to an internal email server handling mail for "mydomain.com". I configure user1@mydomain.com as a black list entry in PMG under this context (administration user blacklist). Send an email from outside...

Can you expand on use cases for the user white/black list (4.4.3. User White-/Blacklist) under administration user white/blacklist? What specific users is this referring to? Assuming its referring to PMG users, I tried adding an email to the root account then setting up a blacklist to block to...

I got nowhere trying to set the mapping with main.cf.in. One post I found made reference to just setting up another transport. That works for specific domains when transport defined configuration/mail proxy/relaying/smarthost is used as primary. Similar to the OP, I want it to send directly...

Bump. This would be a great feature. As a self hosted residential user with a semi static ip (changes ~5 yrs), I've had good results sending to most destinations, however do run into some targets that outright refuse because th rdns lookup doesn't match pmg fqdn. It would be nice to have a...

^^^ FIXED Apparently I wasn't reading the openssl output properly. Turns out script used to update the mailcow LE certs was only acting on the nginx container and not on postfix/dovecot. Getting that fixed involved figuring out what paths were used in the script vs where postfix/dovecot was...

Just wanted to confirm the above. Setting up an actual forwarding rule rather than using the forward option appears to have solved the issue. Both are forwarding target email addr. I suspect the "bad" is doing (or not doing) something to the headers. Good Bad

@thomas-hn I'm doing something similar to this with mailcow dockerized (email server) and getmail (also runs under docker). Effectively, mailcow has an option to poll for email from external accounts. It does this using imap but at fixed intervals. This works well for initially syncing up an...