Sponsored Content
Full Discussion: Sendmail issue
Operating Systems Linux Sendmail issue Post 57014 by moxxx68 on Friday 15th of October 2004 01:00:07 PM
Old 10-15-2004
Lightbulb mutt email system....

Smilie if you are using linux you should have an application called mutt installed on your system. a vary upto date mail system, some what like vi and emacs, that should help you organize and perform necessary tasks on all your email,, input and output. just type mutt and make the necessary changes to suite your needs..
moxxx68Smilie
 

10 More Discussions You Might Find Interesting

1. Solaris

sendmail issue

Hi, yesterday I had issues, sendmail was not responding quickly while sending email and users did not receive any email, This happened with sendmail on solaris 10 and also with sendmail on a linux box. Found it is something to do with DNS blacklists, following lists did not work for me,... (2 Replies)
Discussion started by: upengan78
2 Replies

2. UNIX for Dummies Questions & Answers

Issue with sendmail

Hi Team, I have a script written to sendmail along with attachment in html format. The code is export MAILFROM="abc@abc.com" export MAILTO="abc@abc.com" export CONTENT="./GRP_SPI_ERR.html" export SUBJECT="TEST EMAIL: TESTING HTML" { print - "From: $MAILFROM" print - "To: ${MAILTO}"... (3 Replies)
Discussion started by: Vinaykumar1
3 Replies

3. Solaris

Sendmail Issue

Hi, Guru i had configure in my two server to send out the email. One of the server able to send in the reasonable timing. but another not, it delay almost one day or two days but mostly not send at all. below is the syslog when i try to send out the mail. GOOD Server Dec 28 11:29:39... (5 Replies)
Discussion started by: SmartAntz
5 Replies

4. Solaris

Sendmail issue

Hi all, we are using solaris 10. we need to increase every users mail boxes size as all users mail boxes got filled..Please help..its urgent.. Thanks in advance.. (1 Reply)
Discussion started by: bpsunadm
1 Replies

5. Red Hat

Sendmail Issue.

Hi Gurus, I have been tampering around with sendmail for the past one week and seem to make little progress. Given below is an abstract of the issue. I have a Fedora 12 server(A VM on vitual Box bridged with a Windows XP host) which has to act as a SMTP server and have accordingly put up the... (8 Replies)
Discussion started by: Hari_Ganesh
8 Replies

6. AIX

Sendmail issue

My aix boxes have the port 25 listening and I want to bock that. But before that I want to check the recent logs of the sendmail activity and any open sockets using the port. Please advise. (1 Reply)
Discussion started by: ranasarkar
1 Replies

7. Red Hat

Sendmail issue

Hi Every One, one of our server configuration on sendmail config we are using SMAR_HOST ### define(`SMART_HOST', 'mail.xxx.com') and /etc/sysconfig/sednmail DAEMON is setted to NO so let me know why sendmail is not working for this server any this else u need please do let me know (0 Replies)
Discussion started by: venikathir
0 Replies

8. UNIX for Advanced & Expert Users

Sendmail issue

One of the applications sends mail to the users on daily basis. It sends mail within (internal users) the firewall (e.g., username@companyname.com) and not sending mail outside (external users) the firewall (e.g., username@yyyy.com). When we contacted the admin people they informed us to register... (5 Replies)
Discussion started by: abuibi
5 Replies

9. Emergency UNIX and Linux Support

Sendmail issue

Hi, I'm using sendmail version 8.13.8-8.1.el5_7. I'm pretty new to it. The servera are running RHEL 5.8. My question basically is that I would want to know is there a way to change the from address. I would be able to change it using the return address in mailx command. However I would like to... (3 Replies)
Discussion started by: maverick_here
3 Replies

10. Red Hat

Sendmail issue

Dear All , I have some problem in Sendmail , where it was sending mails perfectly fine with the Ip address of the client machine. But suddenly there was an issue , the SMTP takes the IP of the bond1 interface. So the IP could not get validated in the relay server. So how should i send... (1 Reply)
Discussion started by: jegaraman
1 Replies
mutt(1) 							   User Manuals 							   mutt(1)

NAME
mutt - The Mutt Mail User Agent SYNOPSIS
mutt [-nRyzZ] [-e cmd] [-F file] [-m type] [-f file] mutt [-nx] [-e cmd] [-F file] [-H file] [-i file] [-s subj] [-b addr] [-c addr] [-a file [...] --] addr [...] mutt [-nx] [-e cmd] [-F file] [-s subj] [-b addr] [-c addr] [-a file [...] --] addr [...] < message mutt [-n] [-e cmd] [-F file] -p mutt [-n] [-e cmd] [-F file] -A alias mutt [-n] [-e cmd] [-F file] -Q query mutt -v[v] mutt -D DESCRIPTION
Mutt is a small but very powerful text based program for reading and sending electronic mail under unix operating systems, including sup- port for color terminals, MIME, OpenPGP, and a threaded sorting mode. Note: This manual page gives a brief overview of mutt's command line options. You should find a copy of the full manual in /usr/share/doc/packages/mutt, in text, HTML, and/or PDF format. OPTIONS
-A alias An expanded version of the given alias is passed to stdout. -a file [...] Attach a file to your message using MIME. When attaching single or multiple files, separating filenames and recipient addresses with "--" is mandatory, e.g. mutt -a image.jpg -- addr1 or mutt -a img.jpg *.png -- addr1 addr2. The -a option must be placed at the end of command line options. -b address Specify a blind-carbon-copy (BCC) recipient -c address Specify a carbon-copy (CC) recipient -d level If mutt was complied with +DEBUG log debugging output to ~/.muttdebug0. Level can range from 1-5 and effects verbosity. A value of 2 is recommended. -D Print the value of all configuration options to stdout. -e command Specify a configuration command to be run after processing of initialization files. -f mailbox Specify which mailbox to load. -F muttrc Specify an initialization file to read instead of ~/.muttrc -h Display help. -H draft Specify a draft file which contains header and body to use to send a message. -i include Specify a file to include into the body of a message. -m type specify a default mailbox type for newly created folders. -n Causes Mutt to bypass the system configuration file. -p Resume a postponed message. -Q query Query a configuration variables value. The query is executed after all configuration files have been parsed, and any commands given on the command line have been executed. -R Open a mailbox in read-only mode. -s subject Specify the subject of the message. -v Display the Mutt version number and compile-time definitions. -vv Display license and copyright information. -x Emulate the mailx compose mode. -y Start Mutt with a listing of all mailboxes specified by the mailboxes command. -z When used with -f, causes Mutt not to start if there are no messages in the mailbox. -Z Causes Mutt to open the first mailbox specified by the mailboxes command which contains new mail. -- Treat remaining arguments as addr even if they start with a dash. See also "-a" above. ENVIRONMENT
EDITOR Specifies the editor to use if VISUAL is unset. EMAIL The user's e-mail address. HOME Full path of the user's home directory. MAIL Full path of the user's spool mailbox. MAILDIR Full path of the user's spool mailbox if MAIL is unset. Commonly used when the spool mailbox is a maildir (5) folder. MAILCAPS Path to search for mailcap files. MM_NOASK If this variable is set, mailcap are always used without prompting first. PGPPATH Directory in which the user's PGP public keyring can be found. TMPDIR Directory in which temporary files are created. REPLYTO Default Reply-To address. VISUAL Specifies the editor to use when composing messages. FILES
~/.muttrc or ~/.mutt/muttrc User configuration file. /etc/Muttrc System-wide configuration file. /tmp/muttXXXXXX Temporary files created by Mutt. ~/.mailcap User definition for handling non-text MIME types. /etc/mailcap System definition for handling non-text MIME types. ~/.mime.types User's personal mapping between MIME types and file extensions. /etc/mime.types System mapping between MIME types and file extensions. /usr/bin/mutt_dotlock The privileged dotlocking program. /usr/share/doc/packages/mutt/manual.txt The Mutt manual. BUGS
None. Mutts have fleas, not bugs. FLEAS
Suspend/resume while editing a file with an external editor does not work under SunOS 4.x if you use the curses lib in /usr/5lib. It does work with the S-Lang library, however. Resizing the screen while using an external pager causes Mutt to go haywire on some systems. Suspend/resume does not work under Ultrix. The help line for the index menu is not updated if you change the bindings for one of the functions listed while Mutt is running. For a more up-to-date list of bugs, errm, fleas, please visit the mutt project's bug tracking system under http://bugs.mutt.org/. NO WARRANTIES
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. SEE ALSO
curses(3), mailcap(5), maildir(5), mbox(5), mutt_dotlock(1), muttrc(5), ncurses(3), sendmail(1), smail(1). Mutt Home Page: http://www.mutt.org/ The Mutt manual AUTHOR
Michael Elkins, and others. Use <mutt-dev@mutt.org> to contact the developers. Unix January 2009 mutt(1)
All times are GMT -4. The time now is 06:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy