IndiMail

By now I have got exhausted answering folks 'Why IndiMail does not have a shared addressbook'IndiMail is a pure messaging platform. It does not attempt to do things which can be done better by other software like openLDAP etc.However, things can get ... [More] bit tricky setting up an address book using openLDAP. This tutorial should make it easy for you to install your own shared address book. The commands below have worked for me on my linux laptop which is proudly powered by Fedora 12. The commands / configuration may slightly vary for your Linux distro / openLDAP version.Install openldap% sudo yum install openldap openldap-servers openldap-clientsConfigure openldapYou need to start slapd to implement openldap. slapd uses configurionfile /etc/openldap/slapd.confThe following slapd.conf file contains the basic configurations required to establish a shared address book on a secure network, however there are no access controls yet defined; security is covered later on. The encrypted root password (rootpw) should be substituted where necessary. You can use slappasswd to generate the password% slappasswd -s secret{SSHA}gDPX3cS87+B31mAF5zHCGtEJBYSuqrN/## See slapd.conf(5) for details on configuration options.# This file should NOT be world readable.#include /etc/openldap/schema/corba.schemainclude /etc/openldap/schema/core.schemainclude /etc/openldap/schema/cosine.schemainclude /etc/openldap/schema/duaconf.schemainclude /etc/openldap/schema/dyngroup.schemainclude /etc/openldap/schema/inetorgperson.schemainclude /etc/openldap/schema/java.schemainclude /etc/openldap/schema/misc.schemainclude /etc/openldap/schema/nis.schemainclude /etc/openldap/schema/openldap.schemainclude /etc/openldap/schema/ppolicy.schemainclude /etc/openldap/schema/collective.schema######################################################################## ldbm and/or bdb database definitions#######################################################################database bdbsuffix "dc=indimail,dc=org"checkpoint 1024 15rootdn "cn=Manager,dc=indimail,dc=org"rootpw {SSHA}gDPX3cS87+B31mAF5zHCGtEJBYSuqrN/# The database directory MUST exist prior to running slapd AND# should only be accessible by the slapd and slap tools.# Mode 700 recommended.directory /var/lib/ldap# Sample access control policy:# Root DSE: allow anyone to read it# Subschema (sub)entry DSE: allow anyone to read it# Other DSEs:# Allow self write access# Allow authenticated users read access# Allow anonymous users to authenticate# Directives needed to implement policy:# access to dn.base="" by * read# access to dn.base="cn=Subschema" by * read# access to *# by self write# by users read# by anonymous auth## if no access controls are present, the default policy# allows anyone and everyone to read anything but restricts# updates to rootdn. (e.g., "access to * by * read")## rootdn can always read and write EVERYTHING!access to dn.subtree="ou=addressbook,dc=indimail,dc=org" by anonymous auth by self write by users readaccess to * by anonymous auth by self read by users read# Indices to maintain for this databaseindex objectClass eq,pres#index ou,cn,mail,surname,givenname eq,pres,sub#index uidNumber,gidNumber,loginShell eq,pres#index uid,memberUid eq,pres,sub#index nisMapName,nisMapEntry eq,pres,subMake user that /etc/openldap/slapd.conf is owned by ldap and has write permissions for ldap user.As of now I prefer openldap using slapd.conf and not slapd.d for configuration.% sudo /bin/rm -r /etc/openldap/slapd.dslapd StartupMy favourite method happens to be using djb's supervise and hence is one of the core compoment of the IndiMail package% cat > /tmp/run1#!/bin/shexec /usr/sbin/slapd -u ldap -f /etc/openldap/slapd.conf -d 0 2>&1cntrl-d% cat > /tmp/run2#!/bin/shexec /var/indimail/bin/setuidgid qmaill \/var/indimail/bin/multilog t /var/log/indimail/slapd.389cntrl-d# create /service/.slapd.389 so that svscan does not discover this new service yet% sudo mkdir -p /service/.slapd.389/log% sudo mv /tmp/run2 /service/.slapd.389/log/run% sudo mv /tmp/run1 /service/.slapd.389/run% sudo chmod +x /service/.slapd.389/run /service/.slapd.389/log/run# rename .slapd.389 to slapd.389 for svscan to discover and start slapd% sudo mv /service/.slapd.389 /service/slapd.389% svstat /service/slapd.389/service/slapd.389/: up (pid 4069) 4 seconds http://www.brennan.id.au/20-Shared_Address_Book_LDAP.html http://www.wains.be/mirrors/feldt.com/ http://linsec.ca/Using_OpenLDAP_as_an_Address_Book [Less]

IndiMail 1.7.3 comes with option in svctool to install QMQP service. IndiMail 1.7.5 will come with RPM package indimail-mini which will allow you to install a mini indimail installation. A mini indimail installation comes up with a bare minimum list ... [More] of programs to enable you to send out mails. A indimail-mini installation doesn't have a mail queue. Instead it gives each new message to a central server through QMQP.Many of my friends run web servers which need to send out emails. If you already have an installation of IndiMail messaging server on your network, you can quickly setup a mini indimail installation on your web server, without impacting the performance by using QMQP. To use QMQP service, you need to have QMQP service running on your IndiMail messaging server. All other servers (including your webservers) can have a indimail-mini installation.How do I set up a QMQP service?You need to have at least one host on your network offering QMQP service to your clients. IndiMail includes a QMQP server, qmail-qmqpd. Here's how to set up QMQP service to authorized client hosts on your IndiMail messaging server.first create /var/indimail/etc/qmqp.tcp in tcprules format to allow queueing from the authorized hosts. make sure to deny connections from unauthorized hosts. for example, if queueing is allowed from 1.2.3.*:1.2.3.:allow:denyThen create /var/indimail/etc/qmqp.cdb:% sudo /var/indimail/bin/tcprules /var/indimail/etc/qmqp.cdb \ /var/indimail/etc/qmqp.tmp < /var/indimail/etc/qmqp.tcpYou can change /var/indimail/etc/qmqp.tcp and run tcprules again at any time. Finally qmail-qmqpd to be run under supervise:% sudo /var/indimail/sbin/svctool --qmqp=628 --servicedir=/service \ --qbase=/var/indimail/queue --qcount=5 --qstart=1 \ --cntrldir=control --localip=0 \ --maxdaemons=75 --maxperip=25 --fsync --syncdir \ --memory=104857600 --min-free=52428800628 is the TCP port for QMQP.How do I install indimail-mini?A indimail-mini installation is just like a indimail installation, except that it's much easier to set up:* You don't need MySQL* You don't need /var/indimail/alias. A indimail-mini installation doesn't do any local delivery.* You don't need indimail entries in /etc/group or /etc/passwd. indimail-mini runs with the same privileges as the user sending mail; it doesn't have any of its own files.* You don't need to start anything from your boot scripts. indimail-mini doesn't have a queue, so it doesn't need a long-running queue manager.* You don't need to add anything to inetd.conf. A null client doesn't receive incoming mail.Here's what you do need:* qmail-qmqpc, forward, qmail-inject, sendmail, predate, datemail, mailsubj, qmail-showctl, maildirmake, maildir2mbox, maildirwatch, qail, elq, and pinq in /var/indimail/bin;* a symbolic link to qmail-qmqpc from /var/indimail/bin/qmail-queue;* symbolic links to /var/indimail/bin/sendmail from /usr/sbin/sendmail and /usr/lib/sendmail (for Fedora see the topic on /usr/sbin/alternatives below)* all the manual pages in /var/indimail/man;You can install all the above my manually copying the binaries and man pages from a host having standard IndiMail installation or you can using the indimail-mini RPM% sudo rpm -ivh indimail-mini-1.7.5-1.1.i386.rpmApart from the binaries, you need to do the following* a list of IP addresses of QMQP servers, one per line, in /var/indimail/control/qmqpservers;* a copy of /var/indimail/control/me, /var/indimail/control/defaultdomain, and /var/indimail/control/plusdomain from your central server, so that qmail-inject uses appropriate host names in outgoing mail; and* this host's name in /var/indimail/control/idhost, so that qmail-inject generates Message-ID without any risk of collision.Everything can be shared across hosts except for /var/indimail/control/idhost.Remember that users won't be able to send mail if all the QMQP servers are down. Most sites have two or three independent QMQP servers.Note that users can still use all the qmail-inject environment variables to control the appearance of their outgoing messages.Fedora - Using /usr/sbin/alternativesSometimes two or more Fedora package exist that serve the same purpose. The alternatives system provides a mechanism for selecting an active default application from several valid alternatives. You can use the alternatives system to configure as an alternative MTA for your system. Using alternatives, you don't have to create the links to /var/indimail/bin/sendmail manually as instructed above.% sudo /usr/sbin/alternatives --install \ /usr/sbin/sendmail mta /var/indimail/bin/sendmail 120 \ --slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman \ /var/indimail/man/man8/qmail-inject.8.gz \ --slave /usr/lib/sendmail mta-sendmail \ /var/indimail/bin/sendmail /usr/sbin/alternatives --set mta /var/indimail/bin/sendmailYou can download IndiMail athttp://sourceforge.net/projects/indimail/The RPM can be downloaded fromhttp://download.opensuse.org/repositories/home:/indimail/NOTE: This document is based on 'Installing min-qmail' by djb [Less]

IndiMail 1.7.3 comes with option in svctool to install QMQP service. IndiMail 1.7.5 will come with RPM package indimail-mini which will allow you to install a mini indimail installation. A mini indimail installation comes up with a bare minimum list ... [More] of programs to enable you to send out mails. A indimail-mini installation doesn't have a mail queue. Instead it gives each new message to a central server through QMQP.Many of my friends run web servers which need to send out emails. If you already have an installation of IndiMail messaging server on your network, you can quickly setup a mini indimail installation on your web server, without impacting the performance by using QMQP. To use QMQP service, you need to have QMQP service running on your IndiMail messaging server. All other servers (including your webservers) can have a indimail-mini installation.How do I set up a QMQP service?You need to have at least one host on your network offering QMQP service to your clients. IndiMail includes a QMQP server, qmail-qmqpd. Here's how to set up QMQP service to authorized client hosts on your IndiMail messaging server.first create /var/indimail/etc/tcp.qmqp in tcprules format to allow queueing from the authorized hosts. make sure to deny connections from unauthorized hosts. for example, if queueing is allowed from 1.2.3.*:1.2.3.:allow:denyThen create /var/indimail/etc/tcp.qmqp.cdb:% sudo /var/indimail/bin/tcprules /var/indimail/etc/tcp.qmqp.cdb \/var/indimail/etc/qmqp.tmp < /var/indimail/etc/tcp.qmqpYou can change /var/indimail/etc/tcp.qmqp and run tcprules again at any time. Finally qmail-qmqpd to be run under supervise:% sudo /var/indimail/sbin/svctool --qmqp=628 --servicedir=/service \--qbase=/var/indimail/queue --qcount=5 --qstart=1 \--cntrldir=control --localip=0 \--maxdaemons=75 --maxperip=25 --fsync --syncdir \--memory=104857600 --min-free=52428800628 is the TCP port for QMQP.How do I install indimail-mini?A indimail-mini installation is just like a indimail installation, except that it's much easier to set up:* You don't need MySQL* You don't need /var/indimail/alias. A indimail-mini installation doesn't do any local delivery.* You don't need indimail entries in /etc/group or /etc/passwd. indimail-mini runs with the same privileges as the user sending mail; it doesn't have any of its own files.* You don't need to start anything from your boot scripts. indimail-mini doesn't have a queue, so it doesn't need a long-running queue manager.* You don't need to add anything to inetd.conf. A null client doesn't receive incoming mail.Here's what you do need:* qmail-qmqpc, forward, qmail-inject, sendmail, predate, datemail, mailsubj, qmail-showctl, maildirmake, maildir2mbox, maildirwatch, qail, elq, and pinq in /var/indimail/bin;* a symbolic link to qmail-qmqpc from /var/indimail/bin/qmail-queue;* symbolic links to /var/indimail/bin/sendmail from /usr/sbin/sendmail and /usr/lib/sendmail (for Fedora see the topic on /usr/sbin/alternatives below)* all the manual pages in /var/indimail/man;You can install all the above by manually copying the binaries and man pages from a host having standard IndiMail installation or you can using the indimail-mini RPM% sudo rpm -ivh indimail-mini-1.7.5-1.1.i386.rpmApart from the binaries, you need to do the following* a list of IP addresses of QMQP servers, one per line, in /var/indimail/control/qmqpservers;* a copy of /var/indimail/control/me, /var/indimail/control/defaultdomain, and /var/indimail/control/plusdomain from your central server, so that qmail-inject uses appropriate host names in outgoing mail; and* this host's name in /var/indimail/control/idhost, so that qmail-inject generates Message-ID without any risk of collision.Everything can be shared across hosts except for /var/indimail/control/idhost.Remember that users won't be able to send mail if all the QMQP servers are down. Most sites have two or three independent QMQP servers.Note that users can still use all the qmail-inject environment variables to control the appearance of their outgoing messages.Fedora - Using /usr/sbin/alternativesSometimes two or more Fedora package exist that serve the same purpose. The alternatives system provides a mechanism for selecting an active default application from several valid alternatives. You can use the alternatives system to configure as an alternative MTA for your system. Using alternatives, you don't have to create the links to /var/indimail/bin/sendmail manually as instructed above.% sudo /usr/sbin/alternatives --install \/usr/sbin/sendmail mta /var/indimail/bin/sendmail 120 \--slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman \/var/indimail/man/man8/qmail-inject.8.gz \--slave /usr/lib/sendmail mta-sendmail \/var/indimail/bin/sendmail/usr/sbin/alternatives --set mta /var/indimail/bin/sendmailYou can download IndiMail athttp://sourceforge.net/projects/indimail/The RPM can be downloaded fromhttp://download.opensuse.org/repositories/home:/indimail/NOTE: This document is based on 'Installing min-qmail' by djb [Less]

IndiMail 1.7.3 comes with option in svctool to install QMQP service. IndiMail 1.7.5 will come with RPM package indimail-mini which will allow you to install a mini indimail installation. A mini indimail installation comes up with a bare minimum list ... [More] of programs to enable you to send out mails. A indimail-mini installation doesn't have a mail queue. Instead it gives each new message to a central server through QMQP.Many of my friends run web servers which need to send out emails. If you already have an installation of IndiMail messaging server on your network, you can quickly setup a mini indimail installation on your web server, without impacting the performance by using QMQP. To use QMQP service, you need to have QMQP service running on your IndiMail messaging server. All other servers (including your webservers) can have a indimail-mini installation.How do I set up a QMQP service?You need to have at least one host on your network offering QMQP service to your clients. IndiMail includes a QMQP server, qmail-qmqpd. Here's how to set up QMQP service to authorized client hosts on your IndiMail messaging server.first create /var/indimail/etc/tcp.qmqp in tcprules format to allow queueing from the authorized hosts. make sure to deny connections from unauthorized hosts. for example, if queueing is allowed from 1.2.3.*:1.2.3.:allow:denyThen create /var/indimail/etc/tcp.qmqp.cdb:% sudo /var/indimail/bin/tcprules /var/indimail/etc/tcp.qmqp.cdb \/var/indimail/etc/qmqp.tmp < /var/indimail/etc/tcp.qmqpYou can change /var/indimail/etc/tcp.qmqp and run tcprules again at any time. Finally qmail-qmqpd to be run under supervise:% sudo /var/indimail/sbin/svctool --qmqp=628 --servicedir=/service \--qbase=/var/indimail/queue --qcount=5 --qstart=1 \--cntrldir=control --localip=0 \--maxdaemons=75 --maxperip=25 --fsync --syncdir \--memory=104857600 --min-free=52428800628 is the TCP port for QMQP.How do I install indimail-mini?A indimail-mini installation is just like a indimail installation, except that it's much easier to set up:* You don't need MySQL* You don't need /var/indimail/alias. A indimail-mini installation doesn't do any local delivery.* You don't need indimail entries in /etc/group or /etc/passwd. indimail-mini runs with the same privileges as the user sending mail; it doesn't have any of its own files.* You don't need to start anything from your boot scripts. indimail-mini doesn't have a queue, so it doesn't need a long-running queue manager.* You don't need to add anything to inetd.conf. A null client doesn't receive incoming mail.Here's what you do need:* qmail-qmqpc, forward, qmail-inject, sendmail, predate, datemail, mailsubj, qmail-showctl, maildirmake, maildir2mbox, maildirwatch, qail, elq, and pinq in /var/indimail/bin;* a symbolic link to qmail-qmqpc from /var/indimail/bin/qmail-queue;* symbolic links to /var/indimail/bin/sendmail from /usr/sbin/sendmail and /usr/lib/sendmail (for Fedora see the topic on /usr/sbin/alternatives below)* all the manual pages in /var/indimail/man;You can install all the above by manually copying the binaries and man pages from a host having standard IndiMail installation or you can using the indimail-mini RPM% sudo rpm -ivh indimail-mini-1.7.5-1.1.i386.rpmApart from the binaries, you need to do the following* a list of IP addresses of QMQP servers, one per line, in /var/indimail/control/qmqpservers;* a copy of /var/indimail/control/me, /var/indimail/control/defaultdomain, and /var/indimail/control/plusdomain from your central server, so that qmail-inject uses appropriate host names in outgoing mail; and* this host's name in /var/indimail/control/idhost, so that qmail-inject generates Message-ID without any risk of collision.Everything can be shared across hosts except for /var/indimail/control/idhost.Remember that users won't be able to send mail if all the QMQP servers are down. Most sites have two or three independent QMQP servers.Note that users can still use all the qmail-inject environment variables to control the appearance of their outgoing messages.Fedora - Using /usr/sbin/alternativesSometimes two or more Fedora package exist that serve the same purpose. The alternatives system provides a mechanism for selecting an active default application from several valid alternatives. You can use the alternatives system to configure as an alternative MTA for your system. Using alternatives, you don't have to create the links to /var/indimail/bin/sendmail manually as instructed above.% sudo /usr/sbin/alternatives --install \/usr/sbin/sendmail mta /var/indimail/bin/sendmail 120 \--slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman \/var/indimail/man/man8/qmail-inject.8.gz \--slave /usr/lib/sendmail mta-sendmail \/var/indimail/bin/sendmail/usr/sbin/alternatives --set mta /var/indimail/bin/sendmailYou can download IndiMail athttp://sourceforge.net/projects/indimail/The RPM can be downloaded fromhttp://download.opensuse.org/repositories/home:/indimail/NOTE: This document is based on 'Installing min-qmail' by djb [Less]

IndiMail 1.7.3 comes with option in svctool to install QMQP service. IndiMail 1.7.5 will come with RPM package indimail-mini which will allow you to install a mini indimail installation. A mini indimail installation comes up with a bare minimum list ... [More] of programs to enable you to send out mails. A indimail-mini installation doesn't have a mail queue. Instead it gives each new message to a central server through QMQP.Many of my friends run web servers which need to send out emails. If you already have an installation of IndiMail messaging server on your network, you can quickly setup a mini indimail installation on your web server, without impacting the performance by using QMQP. To use QMQP service, you need to have QMQP service running on your IndiMail messaging server. All other servers (including your webservers) can have a indimail-mini installation.How do I set up a QMQP service?You need to have at least one host on your network offering QMQP service to your clients. IndiMail includes a QMQP server, qmail-qmqpd. Here's how to set up QMQP service to authorized client hosts on your IndiMail messaging server.first create /var/indimail/etc/tcp.qmqp in tcprules format to allow queueing from the authorized hosts. make sure to deny connections from unauthorized hosts. for example, if queueing is allowed from 1.2.3.*:1.2.3.:allow:denyThen create /var/indimail/etc/tcp.qmqp.cdb:% sudo /var/indimail/bin/tcprules /var/indimail/etc/tcp.qmqp.cdb \/var/indimail/etc/qmqp.tmp < /var/indimail/etc/tcp.qmqpYou can change /var/indimail/etc/tcp.qmqp and run tcprules again at any time. Finally qmail-qmqpd to be run under supervise:% sudo /var/indimail/sbin/svctool --qmqp=628 --servicedir=/service \--qbase=/var/indimail/queue --qcount=5 --qstart=1 \--cntrldir=control --localip=0 \--maxdaemons=75 --maxperip=25 --fsync --syncdir \--memory=104857600 --min-free=52428800628 is the TCP port for QMQP.How do I install indimail-mini?A indimail-mini installation is just like a indimail installation, except that it's much easier to set up:* You don't need MySQL* You don't need /var/indimail/alias. A indimail-mini installation doesn't do any local delivery.* You don't need indimail entries in /etc/group or /etc/passwd. indimail-mini runs with the same privileges as the user sending mail; it doesn't have any of its own files.* You don't need to start anything from your boot scripts. indimail-mini doesn't have a queue, so it doesn't need a long-running queue manager.* You don't need to add anything to inetd.conf. A null client doesn't receive incoming mail.Here's what you do need:* qmail-qmqpc, forward, qmail-inject, sendmail, predate, datemail, mailsubj, qmail-showctl, maildirmake, maildir2mbox, maildirwatch, qail, elq, and pinq in /var/indimail/bin;* a symbolic link to qmail-qmqpc from /var/indimail/bin/qmail-queue;* symbolic links to /var/indimail/bin/sendmail from /usr/sbin/sendmail and /usr/lib/sendmail (for Fedora see the topic on /usr/sbin/alternatives below)* all the manual pages in /var/indimail/man;You can install all the above by manually copying the binaries and man pages from a host having standard IndiMail installation or you can using the indimail-mini RPM% sudo rpm -ivh indimail-mini-1.7.5-1.1.i386.rpmApart from the binaries, you need to do the following* a list of IP addresses of QMQP servers, one per line, in /var/indimail/control/qmqpservers;* a copy of /var/indimail/control/me, /var/indimail/control/defaultdomain, and /var/indimail/control/plusdomain from your central server, so that qmail-inject uses appropriate host names in outgoing mail; and* this host's name in /var/indimail/control/idhost, so that qmail-inject generates Message-ID without any risk of collision.Everything can be shared across hosts except for /var/indimail/control/idhost.Remember that users won't be able to send mail if all the QMQP servers are down. Most sites have two or three independent QMQP servers.Note that users can still use all the qmail-inject environment variables to control the appearance of their outgoing messages.Fedora - Using /usr/sbin/alternativesSometimes two or more Fedora package exist that serve the same purpose. The alternatives system provides a mechanism for selecting an active default application from several valid alternatives. You can use the alternatives system to configure as an alternative MTA for your system. Using alternatives, you don't have to create the links to /var/indimail/bin/sendmail manually as instructed above.% sudo /usr/sbin/alternatives --install \/usr/sbin/sendmail mta /var/indimail/bin/sendmail 120 \--slave /usr/share/man/man8/sendmail.8.gz mta-sendmailman \/var/indimail/man/man8/qmail-inject.8.gz \--slave /usr/lib/sendmail mta-sendmail \/var/indimail/bin/sendmail/usr/sbin/alternatives --set mta /var/indimail/bin/sendmailYou can download IndiMail athttp://sourceforge.net/projects/indimail/The RPM can be downloaded fromhttp://download.opensuse.org/repositories/home:/indimail/NOTE: This document is based on 'Installing min-qmail' by djb [Less]

IndiMail has a program called vbulletin using which you can instantly email all your subscribers in a domain that has been created using vadddomain. Whenever an authentication requests comes to IndiMail through POP3, IMAP or authenticated SMTP, a ... [More] hook called Login_Tasks gets called. One of the job that Login_Tasks does is to look for a file, in RFC822 format, with ",all" in the end of the filename. If such a file is found, it is copied to the user's Maildir. By using the timestamp of the original file, Login_Tasks also ensures that the file is copied once only.The good thing about using bulletins is that the email is available instantly to all users. No queues, no delays and a huge saving of system resources.You can manually copy the file to /var/indimail/control/domain_name/bulk_mail directory or use the vbulletin command% vbulletin -f /tmp/new_offers.eml -a example.comvbulletin is especially useful when you want to target a subsection of your users or when you have large number of mail delivery hosts in an IndiMail cluster.Read the man page vbulletin(1) for more details [Less]

IndiMail has a program called vbulletin using which you can instantly email all your subscribers in a domain that has been created using vadddomain. Whenever an authentication requests comes to IndiMail through POP3, IMAP or authenticated SMTP, a ... [More] hook called Login_Tasks gets called. One of the job that Login_Tasks does is to look for a file, in RFC822 format, with ",all" in the end of the filename. If such a file is found, it is copied to the user's Maildir. By using the timestamp of the original file, Login_Tasks also ensures that the file is copied once only.The good thing about using bulletins is that the email is available instantly to all users. No queues, no delays and a huge saving of system resources.You can manually copy the file to /var/indimail/control/domain_name/bulk_mail directory or use the vbulletin command% vbulletin -f /tmp/new_offers.eml -a example.comvbulletin is especially useful when you want to target a subsection of your users or when you have large number of mail delivery hosts in an IndiMail cluster.Read the man page vbulletin(1) for more details [Less]

IndiMail has a program called vbulletin using which you can instantly email all your subscribers in a domain that has been created using vadddomain. Whenever an authentication requests comes to IndiMail through POP3, IMAP or authenticated SMTP, a ... [More] hook called Login_Tasks gets called. One of the job that Login_Tasks does is to look for a file, in RFC822 format, with ",all" in the end of the filename. If such a file is found, it is copied to the user's Maildir. By using the timestamp of the original file, Login_Tasks also ensures that the file is copied once only.The good thing about using bulletins is that the email is available instantly to all users. No queues, no delays and a huge saving of system resources.You can manually copy the file to /var/indimail/control/domain_name/bulk_mail directory or use the vbulletin command% vbulletin -f /tmp/new_offers.eml -a example.comvbulletin is especially useful when you want to target a subsection of your users or when you have large number of mail delivery hosts in an IndiMail cluster.Read the man page vbulletin(1) for more details [Less]

IndiMail has a program called vbulletin using which you can instantly email all your subscribers in a domain that has been created using vadddomain. Whenever an authentication requests comes to IndiMail through POP3, IMAP or authenticated SMTP, a ... [More] hook called Login_Tasks gets called. One of the job that Login_Tasks does is to look for a file, in RFC822 format, with ",all" in the end of the filename. If such a file is found, it is copied to the user's Maildir. By using the timestamp of the original file, Login_Tasks also ensures that the file is copied once only.The good thing about using bulletins is that the email is available instantly to all users. No queues, no delays and a huge saving of system resources.You can manually copy the file to /var/indimail/control/domain_name/bulk_mail directory or use the vbulletin command% vbulletin -f /tmp/new_offers.eml -a example.comvbulletin is especially useful when you want to target a subsection of your users or when you have large number of mail delivery hosts in an IndiMail cluster.Read the man page vbulletin(1) for more details [Less]

IndiMail has many methods to help deal with spam. For detecting spam, IndiMail uses bogofilter a fast bayesian spam filter. IndiMail's qmail-smtpd which provides SMTP protocol is neatly integrated with bogofilter. When bogofilter detects spam ... [More] , qmail-smtpd prints the X-Bogosity header as part of SMTP transaction log% grep "X-Bogosity, Yes" /var/log/indimail/smtpd.25/current@400000004bc8183f01fcbc54 qmail-smtpd: pid 16158 from ::ffff:88.191.35.203 HELO MAIL from xxxx RCPT yyyy AUTH Size: 4871 X-Bogosity: Yes, spamicity=0.999616, cutoff=9.90e-01, ham_cutoff=0.00e+00, queueID=6cs66604wfk,The value "Yes" in X-Bogosity indicates spam. You can tell qmail-smtpd to reject such mails at SMTP just by doing# echo 1 > /service/qmail-smtpd.25/variables/REJECTSPAM# svc -u /service/qmail-smtpd.25# svc -d /service/qmail-smtpd.25SMTP clients which tries to send a spam mail will get the following error at the end of the SMTP transaction554 SPAM or junk mail threshold exceeded (#5.7.1)The mail will get bounced. In some cases you would want to issue temporary error to such clients. In the above SMTP transaction log, the IP address of the client was 88.191.35.203. To put such client's into IndiMail's SPAM blacklist, you just need to put the IP address in the control file /var/indimail/control/badip# echo 88.191.35.203 >> /var/indimail/control/badipFor turning on the BADIP functionality, you need to set the BADIPCHECK or the BADIP environment variable. i.e.# echo badip > /service/qmail-smtpd.25/variables/BADIP# svc -d /service/qmail-smtpd.25# svc -u /service/qmail-smtpd.25Clients whose IP match an entry in badip will be greeted as below421 indimail.org sorry, your IP (::ffff:88.191.35.203) is temporarily denied (#4.7.1)Also the client will not be able to carry out any SMTP transactions like ehlo, MAIL FROM, RCPT TO, etcA large ISP can run the following command every day once in crongrep "X-Bogosity, Yes" /var/log/indimail/qmail.smtpd.25/current > /var/indimail/control/badipIf your badip files becomes very large, you can also take advantage of IndiMail's ability to use cdb (or you could use MySQL too)% sudo /var/indimail/bin/qmail-cdb badip [Less]