{
    "content": [
        {
            "type": "text",
            "text": "# Mail::Transport::Mailx (info)\n\n## NAME\n\nMail::Transport::Mailx - transmit messages using external mailx program\n\n## SYNOPSIS\n\nmy $sender = Mail::Transport::Mailx->new(...);\n$sender->send($message);\n\n## DESCRIPTION\n\nImplements mail transport using the external programs 'mailx', \"Mail\",\nor 'mail'.  When instantiated, the mailer will look for any of these\nbinaries in specific system directories, and the first program found is\ntaken.\n\n## Sections\n\n- **Mail::Transport::MailxUser)Contributed Perl DocumenMail::Transport::Mailx(3pm)**\n- **NAME**\n- **INHERITANCE**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **METHODS**\n- **DIAGNOSTICS**\n- **SEE ALSO**\n- **LICENSE**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "Mail::Transport::Mailx",
        "section": "",
        "mode": "info",
        "summary": "Mail::Transport::Mailx - transmit messages using external mailx program",
        "synopsis": "my $sender = Mail::Transport::Mailx->new(...);\n$sender->send($message);",
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "Mail::Transport::MailxUser)Contributed Perl DocumenMail::Transport::Mailx(3pm)",
                "lines": 1,
                "subsections": []
            },
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "INHERITANCE",
                "lines": 5,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 17,
                "subsections": []
            },
            {
                "name": "METHODS",
                "lines": 119,
                "subsections": []
            },
            {
                "name": "DIAGNOSTICS",
                "lines": 30,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "LICENSE",
                "lines": 7,
                "subsections": []
            }
        ],
        "sections": {
            "Mail::Transport::MailxUser)Contributed Perl DocumenMail::Transport::Mailx(3pm)": {
                "content": "",
                "subsections": []
            },
            "NAME": {
                "content": "Mail::Transport::Mailx - transmit messages using external mailx program\n",
                "subsections": []
            },
            "INHERITANCE": {
                "content": "Mail::Transport::Mailx\nis a Mail::Transport::Send\nis a Mail::Transport\nis a Mail::Reporter\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "my $sender = Mail::Transport::Mailx->new(...);\n$sender->send($message);\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Implements mail transport using the external programs 'mailx', \"Mail\",\nor 'mail'.  When instantiated, the mailer will look for any of these\nbinaries in specific system directories, and the first program found is\ntaken.\n\nWARNING: There are many security issues with mail and mailx. DO NOT USE\nthese commands to send messages which contains data derived from any\nexternal source!!!\n\nUnder Linux, freebsd, and bsdos the \"mail\", \"Mail\", and \"mailx\" names\nare just links to the same binary.  The implementation is very\nprimitive, pre-MIME standard,  what may cause many headers to be lost.\nFor these platforms (and probably for other platforms as well), you can\nbetter not use this transport mechanism.\n\nExtends \"DESCRIPTION\" in Mail::Transport::Send.\n",
                "subsections": []
            },
            "METHODS": {
                "content": "Extends \"METHODS\" in Mail::Transport::Send.\n\nConstructors\nExtends \"Constructors\" in Mail::Transport::Send.\n\nMail::Transport::Mailx->new(%options)\n-Option    --Defined in     --Default\nexecutable  Mail::Transport  undef\nhostname    Mail::Transport  'localhost'\ninterval    Mail::Transport  30\nlog         Mail::Reporter   'WARNINGS'\npassword    Mail::Transport  undef\nport        Mail::Transport  undef\nproxy       Mail::Transport  undef\nretry       Mail::Transport  <false>\nstyle                        <autodetect>\ntimeout     Mail::Transport  120\ntrace       Mail::Reporter   'WARNINGS'\nusername    Mail::Transport  undef\nvia         Mail::Transport  'mailx'\n\nexecutable => FILENAME\nhostname => HOSTNAME|ARRAY\ninterval => SECONDS\nlog => LEVEL\npassword => STRING\nport => INTEGER\nproxy => PATH\nretry => NUMBER|undef\nstyle => 'BSD'|'RFC822'\nThere are two version of the \"mail\" program.  The newest accepts\nRFC822 messages, and automagically collect information about\nwhere the message is to be send to.  The BSD style mail command\npredates MIME, and expects lines which start with a '~' (tilde)\nto specify destinations and such.  This field is autodetect,\nhowever on some platforms both versions of \"mail\" can live (like\nvarious Linux distributions).\n\ntimeout => SECONDS\ntrace => LEVEL\nusername => STRING\nvia => CLASS|NAME\n\nSending mail\nExtends \"Sending mail\" in Mail::Transport::Send.\n\n$obj->destinations( $message, [$address|ARRAY] )\nInherited, see \"Sending mail\" in Mail::Transport::Send\n\n$obj->putContent($message, $fh, %options)\nInherited, see \"Sending mail\" in Mail::Transport::Send\n\n$obj->send($message, %options)\nInherited, see \"Sending mail\" in Mail::Transport::Send\n\n$obj->trySend($message, %options)\n\nServer connection\nExtends \"Server connection\" in Mail::Transport::Send.\n\n$obj->findBinary( $name, [@directories] )\nInherited, see \"Server connection\" in Mail::Transport\n\n$obj->remoteHost()\nInherited, see \"Server connection\" in Mail::Transport\n\n$obj->retry()\nInherited, see \"Server connection\" in Mail::Transport\n\nError handling\nExtends \"Error handling\" in Mail::Transport::Send.\n\n$obj->AUTOLOAD()\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->addReport($object)\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->defaultTrace( [$level]|[$loglevel, $tracelevel]|[$level,\n$callback] )\nMail::Transport::Mailx->defaultTrace( [$level]|[$loglevel,\n$tracelevel]|[$level, $callback] )\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->errors()\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->log( [$level, [$strings]] )\nMail::Transport::Mailx->log( [$level, [$strings]] )\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->logPriority($level)\nMail::Transport::Mailx->logPriority($level)\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->logSettings()\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->notImplemented()\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->report( [$level] )\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->reportAll( [$level] )\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->trace( [$level] )\nInherited, see \"Error handling\" in Mail::Reporter\n\n$obj->warnings()\nInherited, see \"Error handling\" in Mail::Reporter\n\nCleanup\nExtends \"Cleanup\" in Mail::Transport::Send.\n\n$obj->DESTROY()\nInherited, see \"Cleanup\" in Mail::Reporter\n",
                "subsections": []
            },
            "DIAGNOSTICS": {
                "content": "Warning: Message has no destination\nIt was not possible to figure-out where the message is intended to\ngo to.\n\nError: Package $package does not implement $method.\nFatal error: the specific package (or one of its superclasses) does\nnot implement this method where it should. This message means that\nsome other related classes do implement this method however the\nclass at hand does not.  Probably you should investigate this and\nprobably inform the author of the package.\n\nWarning: Resent group does not specify a destination\nThe message which is sent is the result of a bounce (for instance\ncreated with Mail::Message::bounce()), and therefore starts with a\n\"Received\" header field.  With the \"bounce\", the new destination(s)\nof the message are given, which should be included as \"Resent-To\",\n\"Resent-Cc\", and \"Resent-Bcc\".\n\nThe \"To\", \"Cc\", and \"Bcc\" header information is only used if no\n\"Received\" was found.  That seems to be the best explanation of the\nRFC.\n\nAs alternative, you may also specify the \"to\" option to some of the\nsenders (for instance Mail::Transport::SMTP::send(to) to overrule\nany information found in the message itself about the destination.\n\nError: Sending via mailx mailer $program failed: $! ($?)\nMailx (in some shape: there are many different implementations) did\nstart accepting messages, but did not succeed sending it.\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "This module is part of Mail-Transport distribution version 3.005, built\non July 22, 2020. Website: http://perl.overmeer.net/CPAN/\n",
                "subsections": []
            },
            "LICENSE": {
                "content": "Copyrights 2001-2020 by [Mark Overmeer]. For other contributors see\nChangeLog.\n\nThis program is free software; you can redistribute it and/or modify it\nunder the same terms as Perl itself.  See http://dev.perl.org/licenses/\n\nperl v5.30.3                      2020-07-25       Mail::Transport::Mailx(3pm)",
                "subsections": []
            }
        }
    }
}