• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

procmail with plesk 9.0.1

T

Trampelpfad

Guest
Hello,

after upgrading to Plesk 9.0.1 from 8.6 my procmail filtering did not work any more. I used to have a .procmailrc file which processed all incoming mail from a certain sender through "munpack" to save the attachments in a certain directory on the server.

Is there any way to get procmail back into action on Plesk 9 or is there any other way (maybe horde's ingo) to get incoming mails filtered and attachments decoded and stored in a certain directory?

Thanks for any ideas.
 
No, it seems procmail is completely ignored. (No entries at all in the procmail log)
 
qmail doesn't set UFLINE, DTLINE, RPLINE and other variables -> preline doesn't work -> procmail is ignored
procmail can work without preline, but:
- you can't use variables (eg. $HOME)
- procmailrc have to be in .

so:
.qmail:

| true
| /usr/bin/procmail -m -o ./.procmailrc

my .procmailrc:

:0:
* ^X-Spam-Status: Yes
./Maildir/.Spam/

:0
*
./Maildir/
 
On a Plesk 9.3 system apparently using qmail (according to the message headers) for some reason I cannot see anything below /var/qmail/mailnames/my.dom according to ls -artl there - are the accounts and forwarders set up for each domain saved elsewhere in some configurations, or just hidden from httpd & family through access rights?

Regrettably my "shell" is limited to what I can indirectly invoke through Perl on that LAMP system (as in most shared domain hosting scenarios) - but maybe even there a way could be found to configure eMail accounts and forwarding targets from a list, rather than one by one (of hundreds) through the web interface?
 
Back
Top