9 More Discussions You Might Find Interesting
1. HP-UX
Hi,
I have reports that are generated in one server (10.61.1.108), hostname l28bi01. These reports are supposedly sent to a group of email addresses hourly via an email relay server. However, this is not happening.
In sendmail.cf in bi01, the DS Smart Relay Host ip address is:
... (3 Replies)
Discussion started by: anaigini45
3 Replies
2. UNIX for Dummies Questions & Answers
First, please forgive me for my 2nd attempt to post in a Forum!
And btw, the Code Tags tutorial has the fonts and the sizes,
but when I am editing my post none of those fonts and sizes
are not there!
SCO OpenServer(TM) Release 5 (worf.xxx.com)
Worf is our proxy & POP Server, and it... (7 Replies)
Discussion started by: Nancy L
7 Replies
3. Post Here to Contact Site Administrators and Moderators
SCO OpenServer(TM) Release 5 (worf.xxx.com)
Worf is my proxy Server, and it runs my Lan with windows PCs, wk2s & XPs. There are only two users who POP the mailbox from the Server to client, elena and me nancy! elena can POP her email mailbox is just fine.
We use Eudora and for years we... (1 Reply)
Discussion started by: Nancy L
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,I know, that this is very common issue, but I can't find where is the problem... I have Solaris 10 installed.I want to send mail to external SMTP server, like:echo "letter body"| mailx -s "subject" test@test.comBut I donno what kind of changes I have to do in /etc/hosts and sendmail.cf or... (5 Replies)
Discussion started by: nypreH
5 Replies
5. UNIX for Advanced & Expert Users
Hi folks
OS- Debian Etch
Xen
postfix
courier
perdition
perdition-mysql
MySQL
Single public IP
Dom0 - Debian Etch workstation
Server-1, domU1 for routing with perdition and perdition-mysql
installed
Server-2, domU2, mail server for domain-A
Server-3, domU3, mail server for... (2 Replies)
Discussion started by: satimis
2 Replies
6. UNIX for Dummies Questions & Answers
How do I delete all my mails in the mailbox on Solaris?
$mail
? d *
Illegal numeric
?
d * does not work. Also I want to retain the mailbox.
Thanks,
Rahul. (3 Replies)
Discussion started by: rahulrathod
3 Replies
7. What is on Your Mind?
Hi folks,
Some companies, including mine, disable the cookies on browser (I suppose) making their staffs unable to send/receive online mails other than their own. I even can't read webmails on my own server. I tried going through other proxy servers but without result. Is there anyway to... (3 Replies)
Discussion started by: satimis
3 Replies
8. Solaris
Hi, Can anyone pls. tell me how to access Active directory from solaris. I am looking at solution by which I can send mail notification from the logs generated by scripts, to the users on Exchange server. I am trying for a Perl-LDAP module , but don't realy know how to go for it (5 Replies)
Discussion started by: ganeshh
5 Replies
9. UNIX for Dummies Questions & Answers
Both A and B people has mail client to mail client interaction happily.
1) mails from A company unix server 'uuu' are being received by
A company people onto their mail client. So A company people are happy.
2) mails from A company unix server 'uuu' are not being received by B
... (4 Replies)
Discussion started by: vkandati
4 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)