{
    "content": [
        {
            "type": "text",
            "text": "# mailaddr (info)\n\n## NAME\n\nmailaddr - mail addressing description\n\n## DESCRIPTION\n\nThis  manual page gives a brief introduction to SMTP mail addresses, as\nused on the Internet.  These addresses are in the general format\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **FILES**\n- **SEE ALSO**\n- **COLOPHON**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "mailaddr",
        "section": "",
        "mode": "info",
        "summary": "mailaddr - mail addressing description",
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [
            {
                "name": "mail",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/mail/1/json"
            },
            {
                "name": "aliases",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/aliases/5/json"
            },
            {
                "name": "forward",
                "section": "5",
                "url": "https://www.chedong.com/phpMan.php/man/forward/5/json"
            },
            {
                "name": "sendmail",
                "section": "8",
                "url": "https://www.chedong.com/phpMan.php/man/sendmail/8/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 64,
                "subsections": []
            },
            {
                "name": "FILES",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "SEE ALSO",
                "lines": 4,
                "subsections": []
            },
            {
                "name": "COLOPHON",
                "lines": 6,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "mailaddr - mail addressing description\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "This  manual page gives a brief introduction to SMTP mail addresses, as\nused on the Internet.  These addresses are in the general format\n\nuser@domain\n\nwhere a domain is a  hierarchical  dot-separated  list  of  subdomains.\nThese examples are valid forms of the same address:\n\njohn.doe@monet.example.com\nJohn Doe <john.doe@monet.example.com>\njohn.doe@monet.example.com (John Doe)\n\nThe  domain  part (\"monet.example.com\") is a mail-accepting domain.  It\ncan be a host and in the past it usually was, but it  doesn't  have  to\nbe.  The domain part is not case sensitive.\n\nThe  local  part  (\"john.doe\")  is often a username, but its meaning is\ndefined by  the  local  software.   Sometimes  it  is  case  sensitive,\nalthough  that  is  unusual.   If  you see a local-part that looks like\ngarbage, it is usually because of a gateway between an internal  e-mail\nsystem and the net, here are some examples:\n\n\"surname/admd=telemail/c=us/o=hp/prmd=hp\"@some.where\nUSER%SOMETHING@some.where\nmachine!machine!name@some.where\nI2461572@some.where\n\n(These  are,  respectively, an X.400 gateway, a gateway to an arbitrary\ninternal mail system  that  lacks  proper  internet  support,  an  UUCP\ngateway, and the last one is just boring username policy.)\n\nThe  real-name  part (\"John Doe\") can either be placed before <>, or in\n() at the end.  (Strictly speaking the two aren't  the  same,  but  the\ndifference  is beyond the scope of this page.)  The name may have to be\nquoted using \"\", for example, if it contains \".\":\n\n\"John Q. Doe\" <john.doe@monet.example.com>\n\nAbbreviation\nSome mail systems let users abbreviate the domain name.  For  instance,\nusers at example.com may get away with \"john.doe@monet\" to send mail to\nJohn Doe.  This behavior is deprecated.  Sometimes it  works,  but  you\nshould not depend on it.\n\nRoute-addrs\nIn the past, sometimes one had to route a message through several hosts\nto get it to its final destination.  Addresses which show these  relays\nare termed \"route-addrs\".  These use the syntax:\n\n<@hosta,@hostb:user@hostc>\n\nThis  specifies that the message should be sent to hosta, from there to\nhostb, and finally to hostc.  Many hosts disregard route-addrs and send\ndirectly to hostc.\n\nRoute-addrs  are  very  unusual  now.  They occur sometimes in old mail\narchives.  It is generally possible to ignore all but the  \"user@hostc\"\npart of the address to determine the actual address.\n\nPostmaster\nEvery  site  is  required  to  have  a  user  or  user alias designated\n\"postmaster\" to which problems with the mail system may  be  addressed.\nThe \"postmaster\" address is not case sensitive.\n",
                "subsections": []
            },
            "FILES": {
                "content": "/etc/aliases\n~/.forward\n",
                "subsections": []
            },
            "SEE ALSO": {
                "content": "mail(1), aliases(5), forward(5), sendmail(8)\n\nIETF RFC 5322 <http://www.ietf.org/rfc/rfc5322.txt>\n",
                "subsections": []
            },
            "COLOPHON": {
                "content": "This  page  is  part of release 5.10 of the Linux man-pages project.  A\ndescription of the project, information about reporting bugs,  and  the\nlatest     version     of     this    page,    can    be    found    at\nhttps://www.kernel.org/doc/man-pages/.\n\n4.2 Berkeley Distribution         2020-08-13                       MAILADDR(7)",
                "subsections": []
            }
        }
    }
}