Skip to main content

Configure "mutt" to send mail over SMTP using Google Apps



dot.muttrc Download this file
My Colleague was working on having auto scripts to send mail through "mutt" with backup attachment.
But he was not able get it up, so though of looking into this.
Wondering what "mutt" is go here then :)
Here is what I did to get it working.
  1. If you need to configure anything for mutt first look for .muttrc in your home directory ~/.muttrc
  2. If its not there you can create one.
  3. I have attached my .muttrc file you can use to configure your mutt. (change the email and password)
  4. Just download the dot.muttrc and save it as .muttrc in your home directory (/home/ahmed).
  5. Also create directory in the  path below
  • mkdir -p ~/.mutt/cache/headers
  • mkdir -p ~/.mutt/cache/bodies
  • mkdir -p ~/.mutt/certificates
Before you can start using the script to send your mails -
you need to send the first mail from the "mutt client" so that it takes the certificate from the server.

use
$ mutt
This will bring up the mutt interface - send your test mail from here.
Once that is done. You are all set to use the script.
To test - run the below command in your command prompt.
$ mutt --help
$ mutt -s "Hello Test from the shell Script :)" zubair.ahmed@emailid.com < /dev/null -a <attach a File here>

NOTE for .muttrc
# Non Google App users can just enter the username without the domain name like below.
#set smtp_url = "smtp://zubair.ahmed@smtp.gmail.com:587/"
# To use google apps make sure your email account is transitioned - check with our Google Email Administrator
set smtp_url = "smtp://zubair.ahmed@domainName.com@smtp.gmail.com:587/"
set smtp_pass = "yourDomainPassword"
Labels:

Comments

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n
2 comments
Read more

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa
Post a Comment
Read more