For a general overview of feeding email data to the IzyCloud AI cloud and artifical intelligence engine see email-pipeline-with-izycloud.
Notice that this article does not address setting up a the Reception, Storage and Browse (which IMAP and POP3 are part of), Indexing and Machine Learning Services the the pipeline. Also notice that the data encryption happens in the storage service and layer.
0 mx.izyware.com
10 mx10.izyware.comsendmail.mc
which will be built below:
yum install sendmail-cf;
which perl
/etc/smrsh/
, otherwise you would get 'Service unavailable'.ln -s /your_path/maildump.pl /etc/smrsh/maildump.pl
ln -s /usr/bin/perl /etc/smrsh/perl/etc/aliases
and inform the system that mail that gets delivered to the user needs to get piped to your lambda function, i.e.:yourlocaluseralias: "| perl /your_path/maildump.pl"
You can also dump the mail to another user:
yourlocaluseralias: root
/etc/aliases
:cd /etc/mail/;chmod 644 /etc/aliases; newaliases;
m4 sendmail.mc > sendmail.cf;
chmod 755 /etc/mail;/etc/mail/local-host-names
is the file that will define aliases for your machine, so add the domain to the file.
/etc/mail/virtusertable
will define the username the the incoming email to the domain will be mapped to, so add a line for your domain, and reference the yourlocaluseralias that was added to the aliases file i.e.:
@mydomain.com yourlocaluseralias
You should then build the virtusertable.db database by:
makemap hash virtusertable.db < virtusertable;
/sbin/service sendmail restart; > /var/log/maillog; echo OK;tail /var/log/maillog
email-pipeline-with-izycloud: https://izyware.com/blog/article/how-to-build-an-customized-and-automated-email-pipeline-with-izycloud