Sponsored Content
Special Forums UNIX and Linux Applications Mutt Configuration for Yahoo! (Working sol -) Post 303015240 by puneet_bapna on Saturday 31st of March 2018 08:07:36 AM
Old 03-31-2018
Unfortunately sending did not work with the above,
here are the changes you have to make

Change

Code:
set smtp_url = "smtp://$imap_user:$imap_pass@smtp.mail.yahoo.com:587"

Add

set ssl_starttls = yes
This User Gave Thanks to puneet_bapna For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

how to install yahoo messenger

plz help me how to install yahoo messenger... I dont know the version of solaris i m using ... in system config OS is shown as SunOS version 5.8 also specify where to get the installer of messenger... thanks (1 Reply)
Discussion started by: coolguyshail
1 Replies

2. Solaris

Chinese characters on Sol 2.7

Hi there, I need to get a Chinese disclaimer attached to an email on a Solaris 2.7 box. The disclaimer we use is in English and stored as a text file although I've been asked to see if we can add the Chinsese one? Is it simply just a matter of adding the Chinese locale to the OS or is there... (1 Reply)
Discussion started by: Hayez
1 Replies

3. UNIX for Advanced & Expert Users

Sol 10 Sendmail issue

We have a Spark Solaris 10 box running behind a Pix 501 firewall, we are running NAT and I have mapped access to it from the outside world. Anyway, we can receive mail no problem just can't send. I receive this message bounce: The original message was received at Thu, 10 Jan 2008 17:04:29 -0600... (1 Reply)
Discussion started by: varlania
1 Replies

4. UNIX for Advanced & Expert Users

luupgrade: Sol 8 -> Sol 10 u7 (5/09)

Greetings Forumers! I ran into an issue after running luupgrade on v880 running Solaris 8. I want to upgrade to Solaris 10. When I rebooted the system I noticed the file systems listed as such: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t1d0s0 ... (2 Replies)
Discussion started by: bluescreen
2 Replies

5. Solaris

GCC for X86 on SOL 10

Need help with GCC package. I did downloaded the same from sunfreeware.com for i86, however after doing the unzip I am unable to add the same with pkgadd as I am unable to get the sun standard format as SUNWgcc on my system. Thanks (4 Replies)
Discussion started by: kumarmani
4 Replies

6. UNIX and Linux Applications

Mutt for yahoo and Gmail?

Hi Installed MUTT and configured it for Gmail and got successful and then tried to configure for Yahoo but i am not getting any success in doing that. Can anybody advice what preferences are to be set in .muttrc file for configuring yahoo and moreover How to configure multiple Gmail clients in... (1 Reply)
Discussion started by: nixhead
1 Replies

7. Solaris

JASS - upgrading from Sol 9 to Sol 10

Do I need to reinstall/rerun JASS after upgrading from Sol9 to Sol10? Just wondered if the upgrade procedure overwrote any of the settings etc? (0 Replies)
Discussion started by: psychocandy
0 Replies

8. UNIX for Dummies Questions & Answers

Crontab not working with the hour configuration

Hi, When I set the crontab to run every minute, every hour, it works fine. * * * * * env > /tmp/env.output However I want to run it every day at 8:00 AM and it does not run. * 8 * * * env > /tmp/env.output I ran the 'date' command which says it's 8AM PST and also the 'TZ'... (5 Replies)
Discussion started by: samantha13
5 Replies

9. UNIX for Beginners Questions & Answers

Mutt configuration for yahoo

I have searched high and low for any solid answer on how to configure mutt for yahoo mail. I don't know how to even get the information that I need to do it, everything that I find is for gmail. It's quite frustrating and I need help. (3 Replies)
Discussion started by: Huitzilopochtli
3 Replies
STG-MAIL(1)							   StGit Manual 						       STG-MAIL(1)

NAME
stg-mail - Send a patch or series of patches by e-mail SYNOPSIS
stg mail [options] [<patch1>] [<patch2>] [<patch3>..<patch4>] DESCRIPTION
Send a patch or a range of patches by e-mail using the SMTP server specified by the stgit.smtpserver configuration option, or the --smtp-server command line option. This option can also be an absolute path to sendmail followed by command line arguments. The From address and the e-mail format are generated from the template file passed as argument to --template (defaulting to .git/patchmail.tmpl or ~/.stgit/templates/patchmail.tmpl or /usr/share/stgit/templates/patchmail.tmpl). A patch can be sent as attachment using the --attach option in which case the mailattch.tmpl template will be used instead of patchmail.tmpl. The To/Cc/Bcc addresses can either be added to the template file or passed via the corresponding command line options. They can be e-mail addresses or aliases which are automatically expanded to the values stored in the [mail "alias"] section of GIT configuration files. A preamble e-mail can be sent using the --cover and/or --edit-cover options. The first allows the user to specify a file to be used as a template. The latter option will invoke the editor on the specified file (defaulting to .git/covermail.tmpl or ~/.stgit/templates/covermail.tmpl or /usr/share/stgit/templates/covermail.tmpl). All the subsequent e-mails appear as replies to the first e-mail sent (either the preamble or the first patch). E-mails can be seen as replies to a different e-mail by using the --refid option. SMTP authentication is also possible with --smtp-user and --smtp-password options, also available as configuration settings: smtpuser and smtppassword. TLS encryption can be enabled by --smtp-tls option and smtptls setting. The following variables are accepted by both the preamble and the patch e-mail templates: %(diffstat)s - diff statistics %(number)s - empty if only one patch is sent or ' patchnr/totalnr' %(patchnr)s - patch number %(sender)s - 'sender' or 'authname <authemail>' as per the config file %(totalnr)s - total number of patches to be sent %(version)s - ' version' string passed on the command line (or empty) In addition to the common variables, the preamble e-mail template accepts the following: %(shortlog)s - first line of each patch description, listed by author In addition to the common variables, the patch e-mail template accepts the following: %(authdate)s - patch creation date %(authemail)s - author's email %(authname)s - author's name %(commemail)s - committer's e-mail %(commname)s - committer's name %(diff)s - unified diff of the patch %(fromauth)s - 'From: author ' if different from sender %(longdescr)s - the rest of the patch description, after the first line %(patch)s - patch name %(prefix)s - 'prefix ' string passed on the command line %(shortdescr)s - the first line of the patch description OPTIONS
-a, --all E-mail all the applied patches. --to TO Add TO to the To: list. --cc CC Add CC to the Cc: list. --bcc BCC Add BCC to the Bcc: list. --auto Automatically cc the patch signers. --noreply Do not send subsequent messages as replies. --unrelated Send patches without sequence numbering. --attach Send a patch as attachment. -v VERSION, --version VERSION Add VERSION to the [PATCH ...] prefix. --prefix PREFIX Add PREFIX to the [... PATCH ...] prefix. -t FILE, --template FILE Use FILE as the message template. -c FILE, --cover FILE Send FILE as the cover message. -e, --edit-cover Edit the cover message before sending. -E, --edit-patches Edit each patch before sending. -s SECONDS, --sleep SECONDS Sleep for SECONDS between e-mails sending. --refid REFID Use REFID as the reference id. --smtp-server HOST[:PORT] or "/path/to/sendmail -t -i" SMTP server or command to use for sending mail. -u USER, --smtp-user USER Username for SMTP authentication. -p PASSWORD, --smtp-password PASSWORD Password for SMTP authentication. -T, --smtp-tls Use SMTP with TLS encryption. -b BRANCH, --branch BRANCH Use BRANCH instead of the default branch. -m, --mbox Generate an mbox file instead of sending. -O OPTIONS, --diff-opts OPTIONS Extra options to pass to "git diff". STGIT
Part of the StGit suite - see linkman:stg[1] StGit 03/13/2012 STG-MAIL(1)
All times are GMT -4. The time now is 11:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy