10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am having trouble getting mail to work on a red hat server. At first I was getting this message.
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to :25: Connection refused
Then added the port to my firewall. Then I temporarily turned off selinux. I then copied this file... (1 Reply)
Discussion started by: cokedude
1 Replies
2. Linux
Hi guys,
i am using the below command to send mail
mail -s "HI" abcd@how.com < temp_mail.txt
I am getting the below error
send-mail: fatal: bad string length 0 < 1: myorigin =
My os version is as
Linux
Help me with ur suggestion guys thank u. (3 Replies)
Discussion started by: mohanalakshmi
3 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have a application that writes log details to a file in a folder.
I am trying to write script to send mail to the user whenever the log is appended with "Error" string and details.
The user should receive error and error details in mail whenever there is a error in the file.
The... (4 Replies)
Discussion started by: maddy26615
4 Replies
4. UNIX for Dummies Questions & Answers
A linux box is supposed to emailing the results of backups to the windows exchange server, but nothing arrives. it never has, as the muppet who set up the Windows domain knew nothing about linux. I know only slightly more than that...
pretty sure sendmail is the daemon running to handle mail. it... (0 Replies)
Discussion started by: Noewon
0 Replies
5. UNIX for Advanced & Expert Users
i have sun machines having solaris 9 & 10 OS . Now i need to send mail from the machines to my outlook account . I have the ip adress of OUTLOOK mail server. Now what are the setting i need to do in solaris machines so that i can use mailx or sendmail.
actually i am trying to automate the high... (2 Replies)
Discussion started by: amitranjansahu
2 Replies
6. Ubuntu
Hi all,
I'm new here. I already install ubuntu 9.10 and mail server (Dovecot + Postfix + SASL + Squirrel Mail). But after login on squirrelmail. an error message appeared "Error connecting to IMAP server: localhost. 111 : Connection refused". Any solutions?
Thanks (1 Reply)
Discussion started by: dnet
1 Replies
7. Solaris
Dear All,
Now I use solaris 10 and I try to forward mail from /var/mail/username to their external mail so what should I do?
thank u in advance (2 Replies)
Discussion started by: unitipon
2 Replies
8. HP-UX
Hi,
I am getting illegal option error while using -c to CC in mail.
command used:
mailx -s "Report" -c xyz@abc.com < /tmp/report
Machine: HP UX.
Please help me out.
Looking you forward.
Thanks in Advance.
Jagadeesh. (3 Replies)
Discussion started by: bjagadeesh
3 Replies
9. Shell Programming and Scripting
help i get this error when i sending a mail
send-mail: fatal: open /etc/postfix/main.cf: No such file or directory
Can't send mail: sendmail process failed
this is my coding
echo "$PRONAME is being restart" | mailxs "Subject:Process" "sally@$THISHOST"
i wish to send this mail to my... (2 Replies)
Discussion started by: kkc
2 Replies
10. UNIX for Advanced & Expert Users
Hi When trying to access my UNIX mail account I am getting this error message, can anyone suggest a way to get in and delete some of these messages please?
Can I simply delete my mail file or hack it with a text editor?
Thanks
:confused: (3 Replies)
Discussion started by: deggzy
3 Replies
LEARN ABOUT DEBIAN
mail::transport::mailx
Mail::Transport::Mailx(3pm) User Contributed Perl Documentation Mail::Transport::Mailx(3pm)
NAME
Mail::Transport::Mailx - transmit messages using external mailx program
INHERITANCE
Mail::Transport::Mailx
is a Mail::Transport::Send
is a Mail::Transport
is a Mail::Reporter
SYNOPSIS
my $sender = Mail::Transport::Mailx->new(...);
$sender->send($message);
DESCRIPTION
Implements mail transport using the external programs 'mailx', "Mail", or 'mail'. When instantiated, the mailer will look for any of these
binaries in specific system directories, and the first program found is taken.
WARNING: There are many security issues with mail and mailx. DO NOT USE these commands to send messages which contains data derived from
any external source!!!
Under Linux, freebsd, and bsdos the "mail", "Mail", and "mailx" names are just links to the same binary. The implementation is very
primitive, pre-MIME standard, what may cause many headers to be lost. For these platforms (and probably for other platforms as well), you
can better not use this transport mechanism.
METHODS
Constructors
Mail::Transport::Mailx->new(OPTIONS)
-Option --Defined in --Default
executable Mail::Transport undef
hostname Mail::Transport 'localhost'
interval Mail::Transport 30
log Mail::Reporter 'WARNINGS'
password Mail::Transport undef
port Mail::Transport undef
proxy Mail::Transport undef
retry Mail::Transport <false>
style <autodetect>
timeout Mail::Transport 120
trace Mail::Reporter 'WARNINGS'
username Mail::Transport undef
via Mail::Transport 'mailx'
executable => FILENAME
hostname => HOSTNAME|ARRAY-OF-HOSTNAMES
interval => SECONDS
log => LEVEL
password => STRING
port => INTEGER
proxy => PATH
retry => NUMBER|undef
style => 'BSD'|'RFC822'
There are two version of the "mail" program. The newest accepts RFC822 messages, and automagically collect information about where
the message is to be send to. The BSD style mail command predates MIME, and expects lines which start with a '~' (tilde) to specify
destinations and such. This field is autodetect, however on some platforms both versions of "mail" can live (like various Linux
distributions).
timeout => SECONDS
trace => LEVEL
username => STRING
via => CLASS|NAME
Sending mail
$obj->destinations(MESSAGE, [ADDRESS|ARRAY-OF-ADDRESSES])
See "Sending mail" in Mail::Transport::Send
$obj->putContent(MESSAGE, FILEHANDLE, OPTIONS)
See "Sending mail" in Mail::Transport::Send
$obj->send(MESSAGE, OPTIONS)
See "Sending mail" in Mail::Transport::Send
$obj->trySend(MESSAGE, OPTIONS)
Server connection
$obj->findBinary(NAME [, DIRECTORIES])
See "Server connection" in Mail::Transport
$obj->remoteHost()
See "Server connection" in Mail::Transport
$obj->retry()
See "Server connection" in Mail::Transport
Error handling
$obj->AUTOLOAD()
See "Error handling" in Mail::Reporter
$obj->addReport(OBJECT)
See "Error handling" in Mail::Reporter
$obj->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])
Mail::Transport::Mailx->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])
See "Error handling" in Mail::Reporter
$obj->errors()
See "Error handling" in Mail::Reporter
$obj->log([LEVEL [,STRINGS]])
Mail::Transport::Mailx->log([LEVEL [,STRINGS]])
See "Error handling" in Mail::Reporter
$obj->logPriority(LEVEL)
Mail::Transport::Mailx->logPriority(LEVEL)
See "Error handling" in Mail::Reporter
$obj->logSettings()
See "Error handling" in Mail::Reporter
$obj->notImplemented()
See "Error handling" in Mail::Reporter
$obj->report([LEVEL])
See "Error handling" in Mail::Reporter
$obj->reportAll([LEVEL])
See "Error handling" in Mail::Reporter
$obj->trace([LEVEL])
See "Error handling" in Mail::Reporter
$obj->warnings()
See "Error handling" in Mail::Reporter
Cleanup
$obj->DESTROY()
See "Cleanup" in Mail::Reporter
$obj->inGlobalDestruction()
See "Cleanup" in Mail::Reporter
DIAGNOSTICS
Warning: Message has no destination
It was not possible to figure-out where the message is intended to go to.
Error: Package $package does not implement $method.
Fatal error: the specific package (or one of its superclasses) does not implement this method where it should. This message means that
some other related classes do implement this method however the class at hand does not. Probably you should investigate this and
probably inform the author of the package.
Warning: Resent group does not specify a destination
The message which is sent is the result of a bounce (for instance created with Mail::Message::bounce()), and therefore starts with a
"Received" header field. With the "bounce", the new destination(s) of the message are given, which should be included as "Resent-To",
"Resent-Cc", and "Resent-Bcc".
The "To", "Cc", and "Bcc" header information is only used if no "Received" was found. That seems to be the best explanation of the
RFC.
As alternative, you may also specify the "to" option to some of the senders (for instance Mail::Transport::SMTP::send(to) to overrule
any information found in the message itself about the destination.
Error: Sending via mailx mailer $program failed: $! ($?)
Mailx (in some shape: there are many different implementations) did start accepting messages, but did not succeed sending it.
SEE ALSO
This module is part of Mail-Box distribution version 2.105, built on May 07, 2012. Website: http://perl.overmeer.net/mailbox/
LICENSE
Copyrights 2001-2012 by [Mark Overmeer]. For other contributors see ChangeLog.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See
http://www.perl.com/perl/misc/Artistic.html
perl v5.14.2 2012-05-07 Mail::Transport::Mailx(3pm)