Linux iad1-shared-b7-18 6.6.49-grsec-jammy+ #10 SMP Thu Sep 12 23:23:08 UTC 2024 x86_64
Apache
: 67.205.6.31 | : 216.73.216.171
Cant Read [ /etc/named.conf ]
8.2.29
fernandoquevedo
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
share /
perl5 /
Mail /
Transport /
[ HOME SHELL ]
Name
Size
Permission
Action
Exim.pm
1.61
KB
-rw-r--r--
Exim.pod
6.17
KB
-rw-r--r--
Mailx.pm
2.52
KB
-rw-r--r--
Mailx.pod
7.07
KB
-rw-r--r--
Qmail.pm
1.32
KB
-rw-r--r--
Qmail.pod
6
KB
-rw-r--r--
Receive.pm
615
B
-rw-r--r--
Receive.pod
4.61
KB
-rw-r--r--
SMTP.pm
4.79
KB
-rw-r--r--
SMTP.pod
9.39
KB
-rw-r--r--
Send.pm
2.73
KB
-rw-r--r--
Send.pod
8.88
KB
-rw-r--r--
Sendmail.pm
1.59
KB
-rw-r--r--
Sendmail.pod
7.14
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : Sendmail.pod
=encoding utf8 =head1 NAME Mail::Transport::Sendmail - transmit messages using external Sendmail program =head1 INHERITANCE Mail::Transport::Sendmail is a Mail::Transport::Send is a Mail::Transport is a Mail::Reporter =head1 SYNOPSIS my $sender = Mail::Transport::Sendmail->new(...); $sender->send($message); =head1 DESCRIPTION Implements mail transport using the external C<'Sendmail'> program. When instantiated, the mailer will look for the binary in specific system directories, and the first version found is taken. Some people use Postfix as MTA. Postfix can be installed as replacement for Sendmail: is provides a program with the same name and options. So, this module supports postfix as well. B<WARNING:> When you do bulk email sending with local delivery via Postfix, you can probably better use the SMTP backend to connect to postfix. The C<sendmail> command delivers to C<maildrop>. From C<maildrop>, the C<pickupd> will only sequentially insert messages into C<cleanup>. That process can take considerable elapse time. Directly inserting via C<smtpd> will parallellize the cleanup process. Extends L<"DESCRIPTION" in Mail::Transport::Send|Mail::Transport::Send/"DESCRIPTION">. =head1 METHODS Extends L<"METHODS" in Mail::Transport::Send|Mail::Transport::Send/"METHODS">. =head2 Constructors Extends L<"Constructors" in Mail::Transport::Send|Mail::Transport::Send/"Constructors">. =over 4 =item Mail::Transport::Sendmail-E<gt>B<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> sendmail_options [] timeout Mail::Transport 120 trace Mail::Reporter 'WARNINGS' username Mail::Transport undef via Mail::Transport 'sendmail' =over 2 =item executable => FILENAME =item hostname => HOSTNAME|ARRAY =item interval => SECONDS =item log => LEVEL =item password => STRING =item port => INTEGER =item proxy => PATH =item retry => NUMBER|undef =item sendmail_options => ARRAY Add to the command-line of the started sendmail MTU a list of separate words. So say C< [ '-f', $file ] > and not C< [ "-f $file" ] >, because the latter will be taken by sendmail as one word only. =item timeout => SECONDS =item trace => LEVEL =item username => STRING =item via => CLASS|NAME =back =back =head2 Sending mail Extends L<"Sending mail" in Mail::Transport::Send|Mail::Transport::Send/"Sending mail">. =over 4 =item $obj-E<gt>B<destinations>( $message, [$address|ARRAY] ) Inherited, see L<Mail::Transport::Send/"Sending mail"> =item $obj-E<gt>B<putContent>($message, $fh, %options) Inherited, see L<Mail::Transport::Send/"Sending mail"> =item $obj-E<gt>B<send>($message, %options) Inherited, see L<Mail::Transport::Send/"Sending mail"> =item $obj-E<gt>B<trySend>($message, %options) -Option --Default sendmail_options undef =over 2 =item sendmail_options => ARRAY =back =back =head2 Server connection Extends L<"Server connection" in Mail::Transport::Send|Mail::Transport::Send/"Server connection">. =over 4 =item $obj-E<gt>B<findBinary>( $name, [@directories] ) Inherited, see L<Mail::Transport/"Server connection"> =item $obj-E<gt>B<remoteHost>() Inherited, see L<Mail::Transport/"Server connection"> =item $obj-E<gt>B<retry>() Inherited, see L<Mail::Transport/"Server connection"> =back =head2 Error handling Extends L<"Error handling" in Mail::Transport::Send|Mail::Transport::Send/"Error handling">. =over 4 =item $obj-E<gt>B<AUTOLOAD>() Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<addReport>($object) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<defaultTrace>( [$level]|[$loglevel, $tracelevel]|[$level, $callback] ) =item Mail::Transport::Sendmail-E<gt>B<defaultTrace>( [$level]|[$loglevel, $tracelevel]|[$level, $callback] ) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<errors>() Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<log>( [$level, [$strings]] ) =item Mail::Transport::Sendmail-E<gt>B<log>( [$level, [$strings]] ) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<logPriority>($level) =item Mail::Transport::Sendmail-E<gt>B<logPriority>($level) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<logSettings>() Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<notImplemented>() Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<report>( [$level] ) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<reportAll>( [$level] ) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<trace>( [$level] ) Inherited, see L<Mail::Reporter/"Error handling"> =item $obj-E<gt>B<warnings>() Inherited, see L<Mail::Reporter/"Error handling"> =back =head2 Cleanup Extends L<"Cleanup" in Mail::Transport::Send|Mail::Transport::Send/"Cleanup">. =over 4 =item $obj-E<gt>B<DESTROY>() Inherited, see L<Mail::Reporter/"Cleanup"> =back =head1 DIAGNOSTICS =over 4 =item Error: Errors when closing sendmail mailer $program: $! The was no problem starting the sendmail mail transfer agent, but for some specific reason the message could not be handled correctly. =item Warning: Message has no destination It was not possible to figure-out where the message is intended to go to. =item 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. =item Warning: Resent group does not specify a destination The message which is sent is the result of a bounce (for instance created with L<Mail::Message::bounce()|Mail::Message::Construct::Bounce/"Constructing a message">), and therefore starts with a C<Received> header field. With the C<bounce>, the new destination(s) of the message are given, which should be included as C<Resent-To>, C<Resent-Cc>, and C<Resent-Bcc>. The C<To>, C<Cc>, and C<Bcc> header information is only used if no C<Received> was found. That seems to be the best explanation of the RFC. As alternative, you may also specify the C<to> option to some of the senders (for instance L<Mail::Transport::SMTP::send(to)|Mail::Transport::Send/"Sending mail"> to overrule any information found in the message itself about the destination. =back =head1 SEE ALSO This module is part of Mail-Transport distribution version 3.005, built on July 22, 2020. Website: F<http://perl.overmeer.net/CPAN/> =head1 LICENSE Copyrights 2001-2020 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 F<http://dev.perl.org/licenses/>
Close
