sigmasternchen/php-doc-en
1
0
Fork 0
mirror of https://github.com/sigmasternchen/php-doc-en synced 2025-03-16 00:48:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Fixed mb_send_mail() addtional_header param description. (Copied from mail())

Browse source 
git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@332513 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Yasuo Ohgaki 2013-12-26 06:58:01 +00:00
parent d059bd81d5
commit 719247b2cc
1 changed files with 31 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
reference/mbstring/functions/mb-send-mail.xml
View file

@ -55,14 +55,40 @@
</listitem>
</varlistentry>
<varlistentry>
<term><parameter>additional_headers</parameter></term>
<term><parameter>additional_headers</parameter> (optional)</term>
<listitem>
<para>
<parameter>additional_headers</parameter> is inserted at
the end of the header. This is typically used to add extra
headers. Multiple extra headers are separated with a
newline ("\n").
String to be inserted at the end of the email header.
</para>
<para>
This is typically used to add extra headers (From, Cc, and Bcc).
Multiple extra headers should be separated with a CRLF (\r\n).
</para>
<note>
<para>
When sending mail, the mail <emphasis>must</emphasis> contain
a <literal>From</literal> header. This can be set with the
<parameter>additional_headers</parameter> parameter, or a default
can be set in &php.ini;.
</para>
<para>
Failing to do this will result in an error
message similar to <literal>Warning: mail(): "sendmail_from" not
set in php.ini or custom "From:" header missing</literal>.
The <literal>From</literal> header sets also
<literal>Return-Path</literal> under Windows.
</para>
</note>
<note>
<para>
If messages are not received, try using a LF (\n) only.
Some Unix mail transfer agents (most notably
<link xlink:href="&url.qmail;">qmail</link>) replace LF by CRLF
automatically (which leads to doubling CR if CRLF is used).
This should be a last resort, as it does not comply with
<link xlink:href="&url.rfc;2822">RFC 2822</link>.
</para>
</note>
</listitem>
</varlistentry>
<varlistentry>