10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi guys,
I am trying to send a mail with below command which is working fine. $FilePath_mail have To,From and other information along with mail body which is in HTML format. I want to have image(logo) in the body. So just wanted to send it as an an attachment.
/usr/sbin/sendmail -t <... (1 Reply)
Discussion started by: balakrishnaps
1 Replies
2. UNIX and Linux Applications
Dear Concern,
As per below article, we have configured qmail in our system.
THE LINUX STUFF: qmail Installation Steps on Linux
But when we try to send any mail in own domain, got below error message. Please advise.
Apr 17 17:01:20 BLAUDITSCPTEST sendmail: alias database /etc/aliases... (0 Replies)
Discussion started by: makauser
0 Replies
3. UNIX for Advanced & Expert Users
I am attempting to send multipart formatted email using sendmail -t with attachments. The attachments always arrive as empty if sent from linux. They are intact if sent from AIX.
Does qmail not support attachments for multipart formatted email?
I have a legacy application which runs... (4 Replies)
Discussion started by: charles_n_may
4 Replies
4. Shell Programming and Scripting
Hi,
Can anyone point out some examples on how to use sendmail to send mails with attachments. We have a requirement to change from address and so we are not able to use uuencode along with mailx for sending emails. All your reponses are highly appreciated.
Thanks,
Manick. (3 Replies)
Discussion started by: manickaraja
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have a problem which rely on the fact that I can't to connect from my Linux to any mail server (I have tried for example poczta.o2.pl 587 and poczta.onet.pl 587). It something strange because it works finely on Windows. Have you suggestions what can be source of troubles? I have tried to... (5 Replies)
Discussion started by: DavidMax
5 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have email that is being routed from one server to another server it seems.
The sending server has postfix running and the receiving server has sendmail running. The sendmail status is receiving connection. The sending server cannot seem to reach the receiving server. Error logs state... (0 Replies)
Discussion started by: mojoman
0 Replies
7. Red Hat
Hi ,
I am a complete newbie to linux, I have been given a job to install a mail solution (postfix if possible) I would like to know how should I go about installing..)
Can any one provide me some steps to go about it..
i have read about postfix and the installation steps, it seems there are... (1 Reply)
Discussion started by: anilhk
1 Replies
8. IP Networking
hi all.
Am using smtpd_recipient_restrictions & check_recipient_access in postfix.
The hash file looks like this:
emailaddress1 HOLD
emailaddress2 HOLD
The aim is to place email from these recipients in the hold directory,check them then reinject them back in postfix on some... (0 Replies)
Discussion started by: coolatt
0 Replies
9. Linux
Hi every body.
I have istalled qmail on Red Hat Linux on Local Machine.
I have sent mails.I noticed that these mails have been queued but not delivered.
Can you please help me? So I can send email locally.
I have used following cammands:
# qmailctl stat
/service/qmail-send: up (pid... (0 Replies)
Discussion started by: mosiur
0 Replies
10. Linux
Migrating from sendmail on SUN Solaris to POSTFIX on Linux.
I have been asked to migrate our sendmail to postfix on Linux and would appreciate and information. Hints and tips on the process involved.
Perhaps any links to useful site or documentation that you may know about.
Many Thanks (2 Replies)
Discussion started by: Andrek
2 Replies
OBNAM-BENCHMARK(1) General Commands Manual OBNAM-BENCHMARK(1)
NAME
obnam-benchmark - benchmark obnam
SYNOPSIS
obnam-benchmark [--config=FILE] [--description=DESCRIPTION] [--drop-caches] [--dump-config] [--dump-memory-profile=METHOD]
[--dump-setting-names] [--file-size=SIZE] [--generate-manpage=TEMPLATE] [--generations=N] [-h] [--help] [--larch-branch=DIR]
[--list-config-files] [--log=FILE] [--log-keep=N] [--log-level=LEVEL] [--log-max=SIZE] [--log-mode=MODE] [--no-default-configs]
[--obnam-branch=DIR] [--output=FILE] [--profile-name=PROFILE-NAME] [--results=DIR] [--seivot-branch=DIR] [--seivot-log=SEIVOT-LOG]
[--sftp-delay=SFTP-DELAY] [--size=PAIR] [--use-sftp-repository] [--use-sftp-root] [--verify] [--version] [--with-encryption] [FILE]...
DESCRIPTION
obnam-benchmark benchmarks the obnam(1) backup application, by measuring how much time it takes to do a backup, restore, etc, in various
scenarios. obnam-benchmark uses the seivot(1) tool for actually running the benchmarks, but makes some helpful assumptions about things,
to make it simpler to run than running seivot directly.
Benchmarks are run using two different usage profiles: mailspool (all files are small), and mediaserver (all files are big). For each pro-
file, test data of the desired total size is generated, backed up, and then several incremental generations are backed up, each adding some
more generated test data. Then other operations are run against the backup repository: restoring, listing the contents of, and removing
each generation.
The result of the benchmark is a .seivot file per profile, plus a Python profiler file for each run of obnam. These are stored in
../benchmarks. A set of .seivot files can be summarized for comparison with seivots-summary(1). The profiling files can be viewed with
the usual Python tools: see the pstats module.
The benchmarks are run against a version of obnam checked out from version control. It is not (currently) possible to run the benchmark
against an installed version of obnam. Also the larch Python library, which obnam needs, needs to be checked out from version control.
The --obnam-branch and --larch-branch options set the locations, if the defaults are not correct.
OPTIONS
--config=FILE
add FILE to config files
--description=DESCRIPTION
describe benchmark
--drop-caches
drop kernel buffer caches
--dump-config
write out the entire current configuration
--dump-memory-profile=METHOD
make memory profiling dumps using METHOD, which is one of: none, simple, meliae, or heapy (default: simple)
--dump-setting-names
write out all names of settings and quit
--file-size=SIZE
how big should files be?
--generate-manpage=TEMPLATE
fill in manual page TEMPLATE
--generations=N
benchmark N generations (default: 5)
-h, --help
show this help message and exit
--larch-branch=DIR
use DIR as the larch branch (default: /sbuild-nonexistent/larch/trunk)
--list-config-files
list all possible config files
--log=FILE
write log entries to FILE (default is to not write log files at all); use "syslog" to log to system log, or "none" to disable log-
ging
--log-keep=N
keep last N logs (10)
--log-level=LEVEL
log at LEVEL, one of debug, info, warning, error, critical, fatal (default: debug)
--log-max=SIZE
rotate logs larger than SIZE, zero for never (default: 0)
--log-mode=MODE
set permissions of new log files to MODE (octal; default 0600)
--no-default-configs
clear list of configuration files to read
--obnam-branch=DIR
use DIR as the obnam branch to benchmark (default: .)
--output=FILE
write output to FILE, instead of standard output
--profile-name=PROFILE-NAME
short name for benchmark scenario
--results=DIR
put results under DIR (../benchmarks)
--seivot-branch=DIR
use DIR as the seivot branch (default: installed seivot)
--seivot-log=SEIVOT-LOG
seivot log setting
--sftp-delay=SFTP-DELAY
add artifical delay to sftp transfers (in milliseconds)
--size=PAIR
add PAIR to list of sizes to benchmark (e.g., 10g/1m)
--use-sftp-repository
access the repository over SFTP (requires ssh to localhost to work)
--use-sftp-root
access the live data over SFTP (requires ssh to localhost to work)
--verify
verify restores
--version
show program's version number and exit
--with-encryption
run benchmark using encryption
ENVIRONMENT
TMPDIR This variable must be set. It controls where the temporary files (generated test data) is stored. If this variable was not set,
they'd be put into /tmp, which easily fills up, to the detriment of the entire system. Thus. obnam-benchmark requires that the lo-
cation is set explicitly. (You can still use /tmp if you want, but you have to set TMPDIR explicitly.)
FILES
../benchmarks/
The default directory where results of the benchmark are stored, in a subdirectory named after the branch and revision numbers.
EXAMPLE
To run a small benchmark:
TMPDIR=/var/tmp obnam-benchmark --size=10m/1m
To run a benchmark using existing data:
TMPDIR=/var/tmp obnam-benchmark --use-existing=$HOME/Mail
To view the currently available benchmark results:
seivots-summary ../benchmarks/*/*mail*.seivot | less -S
seivots-summary ../benchmarks/*/*media*.seivot | less -S
(You need to run seivots-summary once per usage profile.)
SEE ALSO
obnam(1), seivot(1), seivots-summary(1).
OBNAM-BENCHMARK(1)