9 More Discussions You Might Find Interesting
1. Solaris
Hi Gurus;
I had 2 interface.
eth1 : 10.x.x.x
eth2 : 30.x.x.x
My default out is 10.x.x.x
Now, I need to connect to public SFTP Server
If I use sftp user@public IP.
I can not connect.
because my out is 10.x.x.x
But I telnet it:
telnet -z 30.x.x.x <public IP - sftp server>... (5 Replies)
Discussion started by: Mujakol
5 Replies
2. UNIX for Advanced & Expert Users
Hello, I'm configuring sendmail on an AIX 7.1 server (bos.net.tcp.client 7.1.1.15).
I've gotten sendmail to send mail through our Novell GroupWise server, so that mail from a user on the server appears to come from their GroupWise account, and replies to the email would go to their GroupWise... (0 Replies)
Discussion started by: eyebeam
0 Replies
3. Linux
hi experts
2012-01-30 10:30:01:812 "y" "NA" "30/01/2012 10:30:01:154 AM"
2012-01-30 10:33:46:342 "y" "NA" "30/01/2012 10:33:45:752 AM"
2012-01-30 10:41:11:148 "n" "200" "30/01/2012 10:41:10:558 AM"
2012-01-30 10:44:48:049 "y" "NA" ... (7 Replies)
Discussion started by: nith_anandan
7 Replies
4. Solaris
Hello,
ENVIRONMENT:
OS: Solaris 10
Sendmail: 8.13.8+Sun
BACKGROUND:
We had a user account that was compromised and was used as a relay. She sent out (or would have if we didn't kill sendmail) ~10K emails alerting people they just won $75K.
The target for this spam was everyone internal... (1 Reply)
Discussion started by: avikb
1 Replies
5. AIX
We have had an issue where the mail file filled up. Is there a setting in sendmail.cf to automatically remove old emails? Say after 14 days. If not is there any way automatically to delete older mail files?? (1 Reply)
Discussion started by: daveisme
1 Replies
6. UNIX for Dummies Questions & Answers
I have a Solaris 2.6 server running sendmail (Version 8.9.3p2). It actually receives email and runs the sendmail process. I need to configure it so that it continues to receive email, but disable its ability to send email out. My initial ideas was to just rename the mail and mailx binaries. But... (0 Replies)
Discussion started by: Rosko
0 Replies
7. Solaris
Hi All,
I have solaris 8 on sparc machine, i need to know how i can let my system send to my e-mail any impacts or troubles.... how i can do that?! :confused:
thx, (1 Reply)
Discussion started by: ahmad_one
1 Replies
8. UNIX for Dummies Questions & Answers
G'day,
I've a solaris 9 box that I want to configure so that users can send out mails to internet. How can I do it? Can someone pls list me the steps or direct me to a detailed website.
Thanks in advance. (1 Reply)
Discussion started by: Albert J.
1 Replies
9. UNIX for Dummies Questions & Answers
Hi.
I need to set up sendmail so that it can send mail to a mail relay.
I have never touched sendmail before so I am not sure how to do this. All incoming mail is directed to a different server - this is just to enable me to get mail out.
Running Solaris 8 on Sparc.
Many thanks,
... (6 Replies)
Discussion started by: warrend
6 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)