Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - eworbit

Pages: [1]
Dovecot / Need Domain specific sieve script instead of system global
« on: December 18, 2020, 08:46:58 PM »
Let me ask this a better way.  Reading this file:

 # The default Sieve script when the user has none. This is a path to a global
 # sieve script file, which gets executed ONLY if user's private Sieve script
 # doesn't exist. Be sure to pre-compile this script manually using the sievec
 # command line tool.
 # --> See sieve_before fore executing scripts before the user's personal
 #     script.
 #sieve_default = /var/lib/dovecot/sieve/default.sieve

It sounds like there's no way for a mail server to have a virtual domains specific sieve script.   It's either each virtual user has to have their own sieve script OR ELSE the global /var/lib/dovecot/sieve/default.sieve takes over.  This isn't very useful when you are running multiple email domains.   

I'm trying to come from a procmail environment where I can do user, domain and system-wide rules however I want.  Any ideas?

Postfix / Can CWP host latest dovecot/pigeonhole packages in its repo?
« on: October 05, 2018, 08:46:46 PM »
It's a sad state of affairs.

Procmail is AWESOME but dead:

The newest way to filter email at the lda local delivery phase is to use a dovecot plugin called pigeonhole. 

As a leach, I've been capturing dovecot mail list emails for years and I scanned over them reading about bugs.   Dovecot developers say that Centos7 needs to have more up-to-date dovecot/pigeonhole packages to solve some common issues.

Centos seems to only have 2013 dovecot packages.

CWP unfortunately doesn't maintain a recent version of dovecot or pigeonhole (# yum list dovecot-pigeonhole dovecot*).

So.... I.... am..... humbled.   procmail *is* installed and I could use that - which I'm WELL familiar with but I got to thinking about how invested CPW is in Centos yet they have old packages.

PS. gosh procmail rules are SO compact, powerful and fast.  This new pigeonhole (seive) syntax stuff is... <sign> ok I guess.

CentOS-WebPanel Bugs / incorrectly shows FAIL on reverse dns check
« on: October 02, 2018, 02:57:12 PM »
In the Postfix Mail Server Manager screen, it shows a FAILED message for my server (

rDNS/PTR = 7.0/ [FAILED]

It's as if it is concatenating "" with 7.0/ and then trying to resolve that.

nslookup does confirm my server forward and reverse resolves correctly so must be a simple CWP bug.

My Current Version:

CentOS-WebPanel Bugs / Re: Why SSH port doesnot change?
« on: October 02, 2018, 12:21:54 PM »
There's some kind of bug.  When I change the ssh port in Services Config -> SSH Configuration, you would expect this part of the

/etc/csf/csf.conf to change accordingly:

# This list is replaced, if present, by "Port" definitions in
# /etc/ssh/sshd_config
PORTS_sshd = "2221"

But it doesn't.   For me,  I had to change this setting and manually open the port in firewall settings.   So this PORTS_sshd does nothing.   Definitely glitchy.

Postfix / Enhancing the Email Auto Responders
« on: September 28, 2018, 07:42:39 PM »
Along with the standard vacation table, I plan to add a vacation_correspondent table.   This will record which recipients have already received the current vacation message per email address. 

The main question I have is that since port 2082 lets the domain's admin log in to administer the email accounts, how can an individual  email users change their own vacation message?   If there's no way in CWP, I guess I'll can write an external control screen in php.

Just asking first.

Postfix / Re: system not sending vacation message
« on: September 27, 2018, 09:33:07 PM »
The rebuild fixed the to the correct permissions:
-rw-r-----  1 vacation mail   203 Sep 27 17:21

But, I didn't like how it lost my custom transport, mynetworks and settings.    Good thing I had them documented.

Postfix / Re: system not sending vacation message
« on: September 26, 2018, 08:39:47 PM »
Getting closer to answering my own question:

At the top of the script, the shell_exec must be restricted and therefore can't fetch the mysql password.
$postfix_password = shell_exec("grep '^password' /etc/postfix/| awk {'print $3'}");

I hardcoded the mysql password in the script and it autoresponder worked.   The script is running as the "nobody".

Postfix / system not sending vacation message
« on: September 26, 2018, 02:46:22 PM »
The system is not sending a vacation message back.  All I seen in /var/log/maillog is where the incomming mail is getting "piped" to the vacation mechanism:
Sep 25 15:04:12 mail postfix/pipe[23896]: 050E720B1A3B: to=<>, relay=vacation, delay=0.08, delays=0.02/0.02/0/0.04, dsn=2.0.0, status=sent (delivered via vacation service)

As a test, I copied the /etc/postfix/vacation.php script over to a junk.php and manual ran it and it did send back a vacation message.  I'm just wondering why the sender is not getting a vacation message through the postfix delivery process.

Any ideas?

Pages: [1]