6 More Discussions You Might Find Interesting
1. Red Hat
Hello,
We have been looking for ways of implementing some redundancy on our postfix gateways in our company. We have 4 Postfix Gateways.
mail2.domain.ro 10
mail.domain.ro 20
mail1.domain.ro 30
mail3.domain.ro 40
On nslookup we have like this:
domain.ro MX preference = 10,... (0 Replies)
Discussion started by: panaitescuionel
0 Replies
2. HP-UX
We have configured our mail unix server and can send out emails automatically from applications running on unix to different people in our company as well as outside our company. However there is an outside client who is not receiving these emails because the settings on their mail server cannot... (4 Replies)
Discussion started by: Tenyhwa
4 Replies
3. Shell Programming and Scripting
i am new in AIX i am trying to write a script to take a backup for specific files on server to and check error log if backup success send email to administrator , script done except for sending mail , i try to configure sendmail on aix to use our exchange server to send emails but still get error... (0 Replies)
Discussion started by: ahmed_salah
0 Replies
4. Red Hat
we have an exchange server in company as excmailbocx.company.com
i wanna send mail using sendmail from redhat to my exchange mail account
how can it be possible? (1 Reply)
Discussion started by: oguzhantrg
1 Replies
5. UNIX for Advanced & Expert Users
Is it possible to configure the Solairs (2.6) mail client to get it's email from an MS Exchange server ? If so can soemone point me in the right direction.
Thanx
:confused: (5 Replies)
Discussion started by: ianf
5 Replies
6. UNIX for Dummies Questions & Answers
Hi everyone
I am setting up my own web hosting and dns server - have got all the dns and web server things sorted out. I am wondering if anyone knows what I need to do to enable my customers to have their own pop and smtp access under their own domains which they host with me. I have two ip... (2 Replies)
Discussion started by: alwayslearningunix
2 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)