Postgrey

I'm starting on the PKGBUILD for postgrey - already put the remaining dependency in AUR (perl-io-multiplex).  Currently, I've got everything put together and have a working PKGBUILD, but I'm looking for some feedback and some advice on how best to write the rc.d script.  I plan on looking at most of the other stuff out there, but I figured I'd put this out there as an announcement and see if anyone has any advice.
I'm well aware that the rc script DOES NOT WORK.  I haven't even started working on it - right now its just hacked together pieces (gentoo and some other arch start scripts) and is NOT CLOSE TO DONE.  However, I'm leaving for the night, so I figured I'd put everything I've done up here so if someone else decides they want to work on it, they can.
Also, since this would be my first post/interaction with the community - hi!
# Contributor: Sean Timothy Noonan <laymil>
pkgname=postgrey
pkgver=1.27
pkgrel=1
pkgdesc="a Postfix policy server implementing greylisting"
url="http://isg.ee.ethz.ch/tools/postgrey/"
options=('NOLIBTOOL')
license="GPL"
depends=('perl-net-server' 'perl>=5.6.0' 'perl-berkeleydb' 'perl-io-multiplex' 'db>=4.1' 'postfix')
makedepends=('')
source=(http://isg.ee.ethz.ch/tools/postgrey/pub/$pkgname-$pkgver.tar.gz)
md5sums=('df3a8b4a0c6ab7e8e5bb5be0de096c47')
build() {
echo $startdir
cd $startdir/pkg
mkdir -p etc/rc.d
mkdir -p etc/conf.d
mkdir -p etc/postfix
mkdir -p usr/sbin
cd $startdir/src/$pkgname-$pkgver
chown -R root:root .
install -m 0755 $startdir/postgrey.rc $startdir/pkg/etc/rc.d/postgrey
install -m 0644 $startdir/postgrey.rc.conf $startdir/pkg/etc/conf.d/postgrey
install -m 0755 postgrey contrib/postgreyreport $startdir/pkg/usr/sbin/
install -m 0644 postgrey_whitelist_recipients postgrey_whitelist_clients $startdir/pkg/etc/postfix/
# Config file for /etc/rc.d/postgrey
# LISTEN TYPE
# Set to 'inet' if you want to use a TCP socket.
# Set to 'unix' if you want to use an UNIX socket.
POSTGREY_TYPE="inet"
# HOST
# What IP should postgrey bind to?
# Leave unchanged unless you know what you are doing.
# (ignored if POSTGREY_TYPE is set to 'unix')
POSTGREY_HOST="127.0.0.1"
# PORT
# What TCP port should postgrey listen on?
# (ignored if POSTGREY_TYPE is set to 'unix')
POSTGREY_PORT="10030"
# SOCKET
# Unix socket to listen on, if POSTGREY_TYPE is set to 'unix'.
# Leave unchanged unless you know what you are doing.
# (ignored if POSTGREY_TYPE is set to 'inet')
POSTGREY_SOCKET="/var/spool/postfix/private/postgrey"
# Additional Postgrey options
# -v, --verbose increase verbosity level
# --delay=N greylist for N seconds (default: 300)
# --max-age=N delete entries older than N days since the last time
# that they have been seen (default: 30)
# --retry-window=N allow only N days for the first retrial (default: 2)
# append 'h' if you want to specify it in hours
# --greylist-action=A if greylisted, return A to Postfix (default: DEFER_IF_PERMIT)
# --greylist-text=TXT response when a mail is greylisted
# (default: Greylisted for %s seconds)
# --lookup-by-subnet strip the last 8 bits from IP addresses (default)
# --lookup-by-host do not strip the last 8 bits from IP addresses
# --whitelist-clients=FILE default: /etc/postfix/postgrey_whitelist_clients
# --whitelist-recipients=FILE default: /etc/postfix/postgrey_whitelist_recipients
# Note that the --whitelist-x options can be specified multiple times, and that
# per default /etc/postfix/postgrey_whitelist_clients.local is also read, so
# that you can put there local entries.
POSTGREY_OPTS=""
#!/bin/bash
# source application-specific settings
POSTGREY_CONF=/etc/conf.d/postgrey
[ -f $POSTGREY_CONF ] && . $POSTGREY_CONF
. /etc/rc.conf
. /etc/rc.d/functions
DAEMON_NAME="postgrey"
POSTGREY_BIN="/usr/sbin/postgrey"
POSTGREY_PID=`pidof -o %PPID /usr/sbin/postgrey`
echo $POSTGREY_TYPE
checkconfig() {
if [ -z $POSTGREY_TYPE ]
then
echo "You need to choose the server type you want"
echo "by setting the POSTGREY_TYPE variable in ${conf}."
else
if [ "$POSTGREY_TYPE" = "inet" ]
then
if [ -z "$POSTGREY_PORT" ] || [ -z "$POSTGREY_HOST" ]
then
echo "The following entries are missing in ${conf}:"
[ -z "$POSTGREY_HOST" ] && echo " - POSTGREY_HOST"
[ -z "$POSTGREY_PORT" ] && echo " - POSTGREY_PORT"
stat_fail
fi
POSTGREY_ADDR="$POSTGREY_TYPE=$POSTGREY_HOST:$POSTGREY_PORT"
else
if [ -z "$POSTGREY_SOCKET" ]
then
echo "The following entries are missing in $conf:"
[ -z "$POSTGREY_SOCKET" ] && echo " - POSTGREY_SOCKET"
stat_fail
fi
POSTGREY_ADDR="$POSTGREY_TYPE=$POSTGREY_SOCKET"
fi
fi
start() {
checkconfig || stat_fail
stat_busy "Starting Postgrey"
# HACK -- start a subshell and corrects perms on the socket...
( if [ "x${POSTGREY_TYPE}" = "xunix" ]; then
rm -f ${POSTGREY_SOCKET};
while ! test -S ${POSTGREY_SOCKET}; do sleep 1; done;
chmod a+rw,a-x ${POSTGREY_SOCKET}; fi ) &
[ -z "$PID" ] && /usr/sbin/postgrey --$POSTGREY_ADDR $POSTGREY_OPTS&> /dev/null
if [ $? -gt 0 ]; then
stat_fail
else
add_daemon postgrey
stat_done
fi
stop() {
stat_busy "Stopping Postfix"
[ ! -z "$PID" ] && kill -9 $PID &> /dev/null
if [ $? -gt 0 ]; then
stat_fail
else
rm_daemon postgrey
stat_done
fi
case "$1" in
start)
start
stop)
stop
restart)
# calling 'stop' and 'start' without the $0 fails...
$0 stop
$0 start
echo "usage: $0 {start|stop|restart}"
esac
exit 0

Now in AUR.  Some comments would be nice since this is only the second package I've done.  Should some additional info on setting up the package be added to the .install file?

Similar Messages

  • Howe to stop postgrey?

    I installed postgrey on my server on friday. And it keeps stopping mail from mail users i want mail from, they er not spammers!:(
    What can i do?

    Here is one attempt to send mail to one of the users!
    Oct 23 10:25:56 xserve postfix/smtpd[3528]: connect from marshal.ssb.no[193.160.165.61]
    Oct 23 10:25:57 xserve postfix/smtpd[3528]: NOQUEUE: reject: RCPT from marshal.ssb.no[193.160.165.61]: 450 <[email protected]>: Recipient address rejected: Greylisted, see from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<marshal.ssb.no>
    Oct 23 10:25:57 xserve postfix/smtpd[3528]: disconnect from marshal.ssb.no[193.160.165.61]
    Oct 23 10:25:59 xserve postfix/smtpd[3529]: lost connection after RCPT from unknown[218.18.138.35]
    Oct 23 10:25:59 xserve postfix/smtpd[3529]: disconnect from unknown[218.18.138.35]
    Oct 23 10:28:53 xserve postfix/smtpd[3578]: connect from marshal.ssb.no[193.160.165.61]
    Oct 23 10:28:53 xserve postfix/smtpd[3578]: NOQUEUE: reject: RCPT from marshal.ssb.no[193.160.165.61]: 450 <[email protected]>: Recipient address rejected: Greylisted, see from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<marshal.ssb.no>
    Oct 23 10:28:53 xserve postfix/smtpd[3578]: disconnect from marshal.ssb.no[193.160.165.61]
    Oct 23 10:30:42 xserve postfix/smtpd[3629]: connect from marshal.ssb.no[193.160.165.61]
    Oct 23 10:30:42 xserve postfix/smtpd[3629]: NOQUEUE: reject: RCPT from marshal.ssb.no[193.160.165.61]: 450 <[email protected]>: Recipient address rejected: Greylisted, see from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<marshal.ssb.no>
    As you see after the first try it still blocks it!

  • Postgrey is eating my emails

    I have noticed that postgrey has been rejecting emails that are perfectly valid, and I'm wondering if it is possible to recover emails that have been rejected.  I tried db_dump -ing the files in /var/spool/postfix/postgrey, but to no avail.
    Here is the relevant line in mail.log:
    postfix/smtpd[8561]: NOQUEUE: reject: RCPT from rowling.freenode.net[140.211.167.103]: 450 4.2.0 <[email protected]>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/neofish.org.html; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<rowling.osuosl.bak>
    Thoughts?

    This is the way greylisting works There is no other way to 'recover' these mails than wait for sending server to retry.

  • Postgrey PKGBUILD?

    Does anyone have a package build for Postgrey they can share?
    http://isg.ee.ethz.ch/tools/postgrey/
    This is greylisting software for postfix.  I'm about to build a package build; however I haven't done it with software with perl modules before and wanted on example.
    Thanks,
    Chris....

    Now in AUR.  Some comments would be nice since this is only the second package I've done.  Should some additional info on setting up the package be added to the .install file?

  • Postgrey plist syntax

    i followed the details in the osx.topicdesk.com doc to enable postgrey, but i'm getting "invalid argument" errors when trying to load the launchd plist. everything else is in place.
    do you see anything wrong with this plist?
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Label</key>
    <string>com.company.postgrey</string>
    <key>ProgramArguments</key>
    <array>
    <string>/usr/local/sbin/postgrey</string>
    <string>--inet=127.0.0.1:10029</string>
    <string>--dbdir=/var/postgrey</string>
    <string>--user=_amavisd</string>
    <string>--group=_amavisd</string>
    <key>ServiceIPC</key>
    <false/>
    <key>UserName</key>
    <string>root</string>
    </array>
    </dict>
    </plist>

    no, this is on a 10.6 server. there may have been some other syntax error, but the service wouldn't start until i removed that key.
    here's what's working right now:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>Label</key>
    <string>com.company.postgrey</string>
    <key>OnDemand</key>
    <false/>
    <key>ProgramArguments</key>
    <array>
    <string>/usr/local/sbin/postgrey</string>
    <string>--inet=127.0.0.1:10029</string>
    <string>--dbdir=/var/postgrey</string>
    <string>--delay</string>
    <string>60</string>
    <string>--user=_amavisd</string>
    <string>--group=_amavisd</string>
    <key>UserName</key>
    <string>root</string>
    </array>
    </dict>
    </plist>

  • Systemctl error: Failed to get D-Bus connection

    Problem migrating server to pure systemd. Unable to start stop or restart any of my enabled services.  Every command to systemctl except enable/disable results in:
    "Failed to get D-Bus connection: No connection to service manager."
    I dunno why enable/disable would work but not status, etc...
    Quick note on my environment:
    Arch installed on my remote server hosted by linode.com
    So, my only access is remote ssh.  This is purely a webserver/mailserver type box.
    Here's what I did so far:
    1) installed systemd and depys according to this guide https://wiki.archlinux.org/index.php/Systemd
    2) enabled all services from my rc.conf DAEMONS according to this guide: https://wiki.archlinux.org/index.php/Daemons_List
    systemctl enable {foo}.service
    3) removed initscripts with
    pacman -R initscripts
    and installed systemd-sysvcompat w/
    pacman -S systemd-sysvcompat
    4) rebooted
    5) I can confirm that "cat /proc/1/comm" does in fact output "systemd"
    Command " sudo ps aux | grep dbus " gives me:
    dbus 1781 0.0 0.2 3076 1352 ? Ss 12:33 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    Command "netstat antp |grep dbus" give me:
    unix 3 [ ] STREAM CONNECTED 4414 /run/dbus/system_bus_socket
    unix 3 [ ] STREAM CONNECTED 4403 /run/dbus/system_bus_socket
    unix 3 [ ] STREAM CONNECTED 4401 /run/dbus/system_bus_socket
    unix 3 [ ] STREAM CONNECTED 4370 /run/dbus/system_bus_socket
    unix 3 [ ] STREAM CONNECTED 4369 /run/dbus/system_bus_socket
    I feel I'm almost there and must be missing something stupid...
    Please help
    Here's a list of services from /etc/systemd/system/multi-user.target.wants
    NetworkManager.service
    clamd.service
    dcron.service
    dovecot.service
    fail2ban.service
    freshclamd.service
    iptables.service
    nginx.service
    ntpd.service
    postfix.service
    postgrey.service
    remote-fs.target
    spamassassin.service
    spawn-fcgi-php.service
    sshd.service
    syslog-ng.service
    DAEMONS is the only variable in my rc.conf.  Here it is:
    DAEMONS=(syslog-ng iptables network netfs crond sshd ntpd fail2ban mysqld spamd postgrey dovecot postfix nginx spawn-fcgi-php clamav)
    systemd man page that: "systemd uses control groups to effectively keep track of processes. Control group information is maintained in the kernel, and is accessible via the file system hierarchy (beneath /sys/fs/cgroup/systemd/)"  I ran the command "findmnt | grep /sys/fs/cgroup" but it returns an empty result...
    Last edited by bx (2012-11-29 22:58:06)

    Solved! Had to update kernel. Solution was in /var/log/kernel.log all along:
    Nov 27 14:43:56 xxxx kernel: systemd[1]: CONFIG_CGROUPS was not set when your kernel was compiled. Systems without control groups are not supported. We will now sleep for 10s, and then continue boot-up. Expect breakage and please do not file bugs. Instead fix your kernel and enable CONFIG_CGROUPS. Consult http://0pointer.de/blog/projects/cgroups-vs-cgroups.html for more information.
    systemd man page that: "systemd uses control groups to effectively keep track of processes. Control group information is maintained in the kernel, and is accessible via the file system hierarchy (beneath /sys/fs/cgroup/systemd/)"  I ran the command
    findmnt | grep /sys/fs/cgroup
    but it returns an empty result...
    I did not see kernel version as a requirement anywhere in docs...
    To check your kernal version use command:
    uname -r
    From the main page https://wiki.archlinux.org/index.php/Systemd
    systemd is a system and service manager for Linux that ... uses socket and D-Bus activation for starting services ... keeps track of processes using Linux control groups ...
    From wikipedia http://en.wikipedia.org/wiki/Cgroups
    cgroups (control groups) is a Linux kernel feature to that was started in 2007 ... and merged to kernel version 2.6.24 ...
    I had problems w/ kernel 2.6.39 which turned out to be a deprecated kernal on my linode. My box had like 300+ days of uptime and never had a need to reboot before the change to systemd. Lucky for me, linode made it stupid easy to update the kernel and i was back on track. systemd is cool. worth the journey. thanks!
    Last edited by bx (2012-11-29 23:14:02)

  • Greylisted in 10.4.8

    I got this message in my mail.log
    Recipient address rejected: Greylisted for 300 seconds
    Does this mean i have a greylist system in my mailserver? i hav not installed postgrey or anything like that!??

    If you haven't installed then it is the other way around. One of your users has sent an email to a mailserver that does greylisting.
    Next time please post the relevant and unmodified log entries. My psychic powers only work during solar elipses

  • Bad command startup -- throttling

    Hello guys, I need really some help.
    I have an issue with my mail (Server 2.2.1)
    The issue I have are:
    - warning: /usr/libexec/postfix/smtpd: bad command startup -- throttling
    - merlin.macwebservers.com postfix/smtpd[1144]: fatal: unsafe ownership or permissions on /private/etc/postfix/submit.cred: uid/gid/mode are 0/27/600 should be 0/0/0600
    - I have some email but not from gmail, yahho
    My postconf -n
    alias_database = hash:/etc/aliases
    alias_maps = hash:/etc/aliases
    biff = no
    command_directory = /usr/sbin
    config_directory = /etc/postfix
    daemon_directory = /usr/libexec/postfix
    data_directory = /Library/Server/Mail/Data/mta
    debug_peer_level = 2
    debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5
    default_destination_concurrency_limit = 7
    default_privs = nobody
    default_transport = smtp
    dovecot_destination_recipient_limit = 1
    enable_server_options = yes
    header_checks = regexp:/etc/postfix/header_checks
    html_directory = /usr/share/doc/postfix/html
    imap_submit_cred_file = /Library/Server/Mail/Config/postfix/submit.cred
    inet_interfaces = all
    inet_protocols = all
    mail_owner = _postfix
    mail_spool_directory = /var/spool/mail
    mailbox_command = /usr/bin/procmail
    mailbox_size_limit = 0
    mailbox_transport = dovecot
    mailq_path = /usr/bin/mailq
    manpage_directory = /usr/share/man
    message_size_limit = 10485760
    mydestination = $myhostname
    mydomain = macwebservers.com
    mydomain_fallback = localhost
    myhostname = merlin.macwebservers.com
    mynetworks = 127.0.0.0/8, [::1]/128,
    myorigin = $mydomain
    newaliases_path = /usr/bin/newaliases
    postscreen_dnsbl_sites =
    queue_directory = /Library/Server/Mail/Data/spool
    readme_directory = /usr/share/doc/postfix
    recipient_canonical_maps = hash:/etc/postfix/system_user_maps
    recipient_delimiter = +
    relay_domains = $mydestination $virtual_maps $transport_maps
    relayhost =
    sample_directory = /usr/share/doc/postfix/examples
    sendmail_path = /usr/sbin/sendmail
    setgid_group = _postdrop
    smtpd_banner = $myhostname ESMTP
    smtpd_client_restrictions = check_client_access hash:/etc/postfix/blacklist_smtp
    smtpd_enforce_tls = no
    smtpd_helo_required = yes
    smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
    smtpd_recipient_restrictions = reject_unauth_pipelining, reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, reject_unauth_destination, check_sender_access hash:/etc/postfix/sender_access, reject_rbl_client zen.spamhaus.org, reject_rbl_client bl.spamcop.net, check_policy_service unix:postgrey/socket, permit
    smtpd_tls_CAfile = /etc/certificates/Alains-Mac-mini.local.0BEEA40E61E3D14D83B7838979EAAE191AF0930 0.chain.pem
    smtpd_tls_cert_file = /etc/certificates/Alains-Mac-mini.local.0BEEA40E61E3D14D83B7838979EAAE191AF0930 0.cert.pem
    smtpd_tls_ciphers = medium
    smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL
    smtpd_tls_key_file = /etc/certificates/Alains-Mac-mini.local.0BEEA40E61E3D14D83B7838979EAAE191AF0930 0.key.pem
    smtpd_use_pw_server = yes
    smtpd_use_tls = yes
    tls_random_source = dev:/dev/urandom
    unknown_local_recipient_reject_code = 550
    use_sacl_cache = yes
    virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    virtual_alias_maps = hash:/etc/postfix/virtual

    This seem ok
    sudo postfix status:
    postfix/postfix-script: the Postfix mail system is running: PID: 15249
    But this sudo postfix -c /Library/Server/Mail/Config/postfix check give error:
    merlin:~ root# sudo postfix -c /Library/Server/Mail/Config/postfix check
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    /usr/sbin/postconf: warning: /Library/Server/Mail/Config/postfix/main.cf: unused parameter: virus_db_update_enabled=1virtual_alias_domains = $virtual_alias_maps hash:/Library/Server/Mail/Config/postfix/virtual_domains
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/custom_header_checks
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/main.cf.10.7.5
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/main.cf.10.7.5.orig
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/main.cf.default.10.8
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/main.cf.default~orig
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/makedefs.out
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/master.cf.10.7.5
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/master.cf.default
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/master.cf.default.10.8
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/master.cf.orig
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/postfix-files
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/postfix-files.prev
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/postfix-files~orig
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/rbl_whitelist
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/rbl_whitelist.db
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/sasl
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/system_user_maps
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/system_user_maps.db
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/virtual_users
    postfix/postfix-script: warning: not owned by root: /Library/Server/Mail/Config/postfix/virtual_users.db
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./aliases.desktop
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./custom_header_checks
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./main.cf.10.7.5
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./main.cf.10.7.5.orig
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./main.cf.default.10.8
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./main.cf.default~orig
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./makedefs.out
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./master.cf.10.7.5
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./master.cf.default
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./master.cf.default.10.8
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./master.cf.orig
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./postfix-files
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./postfix-files.prev
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./postfix-files~orig
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./rbl_whitelist
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./rbl_whitelist.db
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./system_user_maps
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./system_user_maps.db
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./virtual_domains
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./virtual_users
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Config/postfix/./virtual_users.db
    postfix/postfix-script: warning: not owned by _postfix: /Library/Server/Mail/Data/mta/./guid_device_maps.plist
    postfix/postfix-script: warning: group or other writable: /Library/Server/Mail/Data/mta

  • Systemd experience, or "Of Mice and Mounts"

    I cutover to systemd.  Here are my experiences, for better or for worse.  Maybe it will help someone. 
    The wiki's systemd migration page is very good!  I followed it, yet ran into a few problems outside the scope of the page.  I should add here that I want to run in a mixed initscripts/systemd environment fo ease my migration, as the wiki suggests.  My system is a home server, and for external access I run only ssh.
    Mounts -- Systemd hung trying to mount all my drives according to /etc/fstab, especially my ipod. 
    I changed most of them to "noauto" then I was ok.
    Mouse woudn't work under X windows.
    Looks like it was enumerated as /dev/input/mice not /dev/input/mouse0 as before.  Added "mice" as a section in /etc/X11/xorg.conf and then it was fine.
    Netcfg under systemd renamed my two ethernet interfaces from wan and house to wan0 and house0. 
    Ok, this wasn't a problem, but it's not what I expected.
    Cups wouldn't start. 
    I googled and found someone else on the net had this same problem; he replaced the cupsd.socket file and it worked for him.  It also worked for me.
    Postgrey wouldn't start.  It turns out that the postgrey.service file ignores the POSTGREY_ADDR variable in /etc/conf.d/postgrey, so it wasn't starting on the socket which I wanted it to, but on a hard-coded port number.  Oh well. 
    So as I had done for cups, I cloned the default postgrey.service tile in /usr/lib/systemd/system to /etc/systemd/system, and removed the hardcoded port.  Also had to "reenable" the service to make it pick up the new service file.  Now it picks up /etc/conf.d/postgrey as I think it should.
    SSH -- I have it running on a port other than the default. 
    Again, I cloned the sshd.socket file, changed the port, restarted it, and now it's ok.
    Samba is started as a legacy service.  Others are too, probably, like dhcp4.  I suppose I'll have to eventually change the legacy samba service into smbd and nmbd like the old days.
    Laptop -- Cutover to systemd on it too.  Had a few problems like these above, but that's ancient history now (last week!)  What I do like is that the power management functions work better now.  It doesn't always wake up well from sleeping, but I suppose I'll figure that out someday too.
    Last edited by jimbeam (2012-11-10 00:20:53)

    Is there a topic here?
    This seems like it should go to your blog not on the forums.

  • Greylisted address

    I am trying to send mail from my .mac address using Mail (os x 10.4.11) and get the follwoing message from the [email protected] :
    Sun, 26 Oct 2008 16:43:31 -0700 (PDT)
    [email protected]: smtp;450 <[email protected]>: Recipient address rejected: Greylisted, see http://isg.ee.ethz.ch/tools/postgrey/help/mic.gov.mz.html
    This seems to imply that either Apple or I is using a grey listing tool that won't permit sending to the intended address.
    Is there any way I can get the intended recipient off the grey list? The link indicted in the message does not tell me anything I can understand....
    thks
    jw
    Message was edited by: James Wilson

    Ask the adminstrator of the Mozambique e-mail server blocking you to unblock you.
    Make sure that:
    1. Your e-mail address is only known to people in the government agencies.
    2. You never use it for eCommerce external to the government.
    3. The people you communicate with are protecting their machines against spammer viruses.
    4. Your e-mail address is never used for sending or receiving chain letters.
    5. If you have to use eCommerce for the government, make sure that the website sneding you information regarding your purchases has your "notify me of further offers" and similar options unchecked.

  • BerkeleyDB & Incompatible versions of libdb & db.h

    Hi all
    I've been using the Postgrey[*1] package on a mailserver for about 12 months now without any trouble.  Did my semi-regular system upgrade over the w/e and since have been unable to get it to start.
    Additionally, the amavisd-new [*2] AUR package has also stopped working with the same error, although I've managed to find a work around for the moment.
    # /etc/rc.d/postgrey start
    :: Starting Postgrey [BUSY]
    BerkeleyDB needs compatible versions of libdb & db.h
    you have db.h version 5.2.28 and libdb version 5.2.36
    Compilation failed in require at /usr/sbin/postgrey line 16.
    BEGIN failed--compilation aborted at /usr/sbin/postgrey line 16.
    [FAIL]
    I get an identical error message when starting amavisd-new, but there's a flag to disable the db, which I has set so at least that's able to run. 
    I've tried updating both the per-berkeleydb packages and the postgrey packages but I still receive the same error.  I've also installed them via the ABS, but as I didn't make any changes it didn't yield any results.
    Is anyone using postgrey with an up-to-date system?
    Any help would be greatly appreciated. 
    ETA : I'm currently building core/db via the ABS to see if that helps.  If not I thought I might roll back to 5.2.28-1 as core/db has defiantly been updated in my last update.
    [*1] - http://www.archlinux.org/packages/commu … /postgrey/
    [*2] - http://aur.archlinux.org/packages.php?ID=573
    [*3] - http://projects.archlinux.org/svntogit/ … ackages/db
    Last edited by hokapoka (2011-10-25 15:15:22)

    stephane : I did try to rebuild postgrey too, albeit just a perl script. 
    Got if fixed, by rolling back the following packages :
    core/db => 5.2.28-1
    community/perl-berkeleydb => 0.43-6
    community/postgrey => 1.34-2
    I used the packages that were in /var/cache/pacman/pkg Of course I had to remove all postgrey, amavid-new & perl-berkeleydb before I downgraded core/db to 5.2.28-1.  Once I had done that reinstalled all of the other packages both amavisd-new and postfix started without the BerkeleyDB & Incompatible versions of libdb & db.h error.
    I guess I need to file a bug now.

  • [Solved] urlplot + db.h + libdb

    urlplot is an irssi script that catches posted url links in IRC channels in irssi and puts them in an html file. After db upgrade and the db_upgrade advice from here (which I don't think should have made any difference), I get this error when I try to load the script.
    20:22 -!- Irssi: Error in script urlplot:
    20:22
    20:22 DB_File needs compatible versions of libdb & db.h
    20:22 you have db.h version 4.6.19 and libdb version 4.6.21
    20:22 Compilation failed in require at (eval 18) line 230.
    20:22 BEGIN failed--compilation aborted at (eval 18) line 230.
    My db.h:
    * Berkeley DB version information.
    #define DB_VERSION_MAJOR 4
    #define DB_VERSION_MINOR 6
    #define DB_VERSION_PATCH 21
    #define DB_VERSION_STRING "Berkeley DB 4.6.21: (September 27, 2007)"
    I've tried renaming the /usr/include/db.h and /usr/lib/libdb.a but it still gives me that error. I'm guessing it has something to do with DB_File pointing somewhere else, but I don't know perl . If you guys could help me out, I'd really appreciate it.
    Edit: Nevermind. Upgrade to the latest perl 5.8.8-8 fixed the problem.
    'upgpkg: don't remove empty dirs, it breaks installation of perl. added coreutils as depend because of ln usage in .install file'
    Last edited by gentoofu (2007-10-24 04:04:38)

    stephane : I did try to rebuild postgrey too, albeit just a perl script. 
    Got if fixed, by rolling back the following packages :
    core/db => 5.2.28-1
    community/perl-berkeleydb => 0.43-6
    community/postgrey => 1.34-2
    I used the packages that were in /var/cache/pacman/pkg Of course I had to remove all postgrey, amavid-new & perl-berkeleydb before I downgraded core/db to 5.2.28-1.  Once I had done that reinstalled all of the other packages both amavisd-new and postfix started without the BerkeleyDB & Incompatible versions of libdb & db.h error.
    I guess I need to file a bug now.

  • Problèmes avec Amavisd

    Bonsoir, (ou bonjour),
    Quelqu'un d'entre vous a t-il déja eu ce problème :
    Suite à une mise à jour d'un module PERL, Amavisd est tombé : des erreurs de types relay=127.0.0.1[127.0.0.1], delay=6, status=deferred (host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to end of DATA command)).
    des posts de la liste de discussion d'apple m'ont orienté vers une mise à jour d'amavisd, selon un tuto que j'ai trouvé sur osx.topicdesk.com.
    J'ai bien suivi le tuto et je n'ai eu qu'une erreur sur la mise à jour d'un module perl (MIME::Parser).
    Suite à la mise à jour, amavisd se relance bien, mais :
    - le scan antispam ne se fait plus
    - des mails restent bloqués suite à une erreur de type Mime :
    host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=04124-15, mime_decode-1 FAILED: Can't locate object method "binmode" via package "IO::File" at /Library/Perl/5.8.6/MIME/Body.pm line 437. (in reply to end of DATA commandv)
    j'ai testé le package IO::File mais il ne présente pas de problèmes.
    Si je teste le module Maim::SpamAssassin, la j'ai une dizaine d'erreur et il prévient qu'il manque une paire de modules.
    Bon, résultat des courses :
    - mon serveur est une passoire à spams
    - certains mails légitimes ne passent plus
    et je n'ai bien sur pas fait de sauvegarde (on ne m'y reprendra plus).
    Bon j'aurais mieux fait de rester coucher ce matin (ou hier matin), me direz-vous.
    Quoiqu'il en soit, si vous avez une idée pour me sortir de là, je vous en serai redevable.
    Jean-Luc

    Hi pterobyte,
    ok, I'll try to translate.
    I have restored my mailserver with an old image of my server and it works.
    the update was really not fonctionnal with my server.
    but to resume, I updated the IO::file but it didn't work, even in forcing to install with CPAN. there were too much dependencies working out.
    whatever, i'll try another day.
    i was just trying to get my server to filter better than it does.
    the spammassassin' learning junk mail is not so efficient and in installing Postgrey, I met those problems.
    I'm going to work differently. i'll make an backup image (with the excellent deploystudio, i profite to make pub for french software) and I'll try a new update.
    Thanks Pterobyte,
    Jean-Luc

  • Production Mail Servers on Arch

    Just wondering if anyone on this board built / manages a production (or personal) email server running on Arch Linux. I am curious what you used as the MTA and some details about your build. If you have any feedback - please post it here as I am planning on doing so on my system soon.
    Thanks!

    I am going to build a production mail server for about 100+ users on my domain and was only considering Postfix since I have used it before and love it. It's so straight forward and rock solid over anything else I have seen or used. My question is when I search the Wiki or other guides for building a Postfix mail server on Arch, I get a tutorial that explains how to do this with MySQL support. I have never done any kind of mail server with a database engine. Normally I would simply just dump all the users email into their home directory via Maildir method. My question is how difficult is it to build Postfix and have it working with MySQL over just doing a vanilla Maildir style installation. Are their benefits to using MySQL over the simplistic way I am use to doing it? I am assuming the setup and configuration process is a bit more complex but I decided I would ask here for your input / suggestions.
    - Postfix
    - MySQL
    - Dovecot
    - Roundcube (Webmail)
    - Cyrus SASL (SMTP Auth)
    - Clamav
    - Spamassassin
    - Postgrey
    - Amavisd-new (very strange that this is only in AUR)

  • Greylisting in 10.5 server?

    In 10.4 Server, I have used the guide on the link below to install greylisting on 10.4 Server. Have not found any info on how to accomplish this in 10.5. Since niutil dont exist nowadays it must be done in some other way. Any ideas?
    Guide: http://www.afp548.com/article.php?story=20051127235810230

    hi,
    can you give me the new commands? The -commands are not compatible
    Here is the niutil code:
    niutil -create . /groups/postgrey
    niutil -createprop . /groups/postgrey gid 25
    niutil -create . /users/postgrey
    niutil -createprop . /users/postgrey uid 25
    niutil -createprop . /users/postgrey gid 25
    niutil -createprop . /users/postgrey shell /bin/tcsh
    niutil -createprop . /users/postgrey home /tmp
    niutil -createprop . /users/postgrey passwd "*"

Maybe you are looking for

  • Up and Down Internet Connection

    Recently my MacBook is having up and down internet connection. I'm using the new Aiport Extreme base station which is connected to my cable modem. By up and down I mean, the connection seems to go in and out. My Airport signal status is full bars, so

  • Filtering problem in IE 7

    Can someone tell me what I'm doing wrong? The filtering works in FireFox but not IE. http://www.victorcorey.com/spry/wh_unobtrusivegrid.htm [code] <select onchange="filterRegion(this.options[this.selectedIndex].value);"> <option>All Regions</option>

  • Photoshop Elements 11 Crashing

    My Photoshop Elements 11 is brand new and continues to crash repeatedly, losing my data.

  • Tomorrows date

    I have a select option for date range , the lower one should default to system data which is sy-datum , the higher one shoule default to tomorrows date, whats the syntax to put tomorrows date  in the higher select option

  • Why icloud doesn't ask your id and password to stop the service??

    I don't understand why any people who take the iphone can stop the service "find my iphone" without Id and password.  If someone steal ur iphone and stop the service u cannot find ur iphone so I think it would be better to ask for apple id to be able