Displaying 5 results from an estimated 5 matches for "mailalia".
Did you mean:
mailalias
2009 Feb 04
3
mailalias ... not doing anything???
G''day
my module''s init.pp:
class mailaliases
{
if ($skip_mailaliases != "true")
{
mailalias
{ "root":
# ensure => absent,
ensure => present,
target => "/etc/aliases",...
2009 Sep 23
2
mailalias type: automatic rebuild of aliases.db?
HI,
All our unix boxes under puppet are configured with the ''mailalias'' resource
type as in :
mailalias { "root":
recipient => "linuxroot@fqdn",
ensure => present
}
The majority of those boxes however don''t have /etc/aliases served out by
puppet, rather, they simply have the installed default /et...
2010 Jun 26
2
dovecot ldap search result ordering?
...t of dovecot-ldap.conf:
pass_attrs = mail=user, uid=userdb_home=/home/xadmin/%d/%$,userPassword=password
pass_filter = (&(objectClass=posixAccount)(uid=%u))
default_pass_scheme = SSHA
user_attrs = mail=user, uid=home=/home/xadmin/%d/%$
user_filter = (&(objectClass=posixAccount)(|(mail=%u)(mailAlias=%u)))
It works fine, but some account failed to get their domain in pass_attrs.
I check the log.
when it success, the result order is "mail, uid, userPassword"
when it failed, the order is "userPassword, uid, mail"
we just use a username to login. I think dovecot cant get the...
2012 Mar 06
2
Long config retrieval on nodes
...he config retrieval level:
(This is on our monitoring server)
Time:
Attachedstorage: 2.00
Class: 0.00
Collectd conf: 0.01
Config retrieval: 85.91
Cron: 0.00
Exec: 34.11
File: 35.56
Filebucket: 0.00
Group: 0.26
Mailalias: 0.17
Mount: 3.48
Nagios command: 0.02
Nagios contact: 0.00
Nagios contactgroup: 0.00
Nagios host: 0.02
Nagios service: 0.12
Nagios servicegroup: 0.00
Package: 3.12
Resources: 0.00
Schedule: 0.01
This agent run has been done with storeco...
2011 Sep 23
21
Official puppetlabs position on cron vs puppet as a service?
Over the years many shops have come to start running puppet via cron to
address memory leaks in earlier versions of Ruby, but the official position
was that puppet was meant to be run as a continually running service.
I am wondering if the official position has changed. On one hand many if not
all of the early Ruby issues have been fixed, on the other, the addition of
mcollective into the mix as