PHP_ Mail - Manual

DownloadsDocumentationGet InvolvedHelp

Getting StartedIntroductionA simple tutorial

Language ReferenceBasic syntaxTypesVariablesConstantsExpressionsOperatorsControl StructuresFunctionsClasses and ObjectsNamespacesExceptionsGeneratorsReferences ExplainedPredefined VariablesPredefined ExceptionsPredefined Interfaces and ClassesContext options and parametersSupported Protocols and Wrappers

SecurityIntroductionGeneral considerationsInstalled as CGI binaryInstalled as an Apache moduleFilesystem SecurityDatabase SecurityError ReportingUsing Register GlobalsUser Submitted DataMagic QuotesHiding PHPKeeping Current

FeaturesHTTP authentication with PHPCookiesSessionsDealing with XForms

PHP: mail - Manual http://php.net/manual/en/function.mail.php

1 of 51 6/17/2014 2:07 PM

Handling file uploadsUsing remote filesConnection handlingPersistent Database ConnectionsSafe ModeCommand line usageGarbage CollectionDTrace Dynamic Tracing

Function ReferenceAffecting PHP's BehaviourAudio Formats ManipulationAuthentication ServicesCommand Line Specific ExtensionsCompression and Archive ExtensionsCredit Card ProcessingCryptography ExtensionsDatabase ExtensionsDate and Time Related ExtensionsFile System Related Extensions

Human Language and Character Encoding SupportImage Processing and GenerationMail Related ExtensionsMathematical ExtensionsNon-Text MIME OutputProcess Control ExtensionsOther Basic ExtensionsOther ServicesSearch Engine ExtensionsServer Specific ExtensionsSession ExtensionsText ProcessingVariable and Type Related ExtensionsWeb ServicesWindows Only ExtensionsXML Manipulation

Keyboard Shortcuts?

This helpj

Next menu itemk

Previous menu itemg p

Previous man pageg n

Next man pageG

Scroll to bottomg g


2 of 51 6/17/2014 2:07 PM

Scroll to topg h

Goto homepageg s

Goto search(current page)

/Focus search box

Mailparse ezmlm_hash

PHP ManualFunction ReferenceMail Related ExtensionsMailMail Functions

Change language:

Edit Report a Bug

mail

(PHP 4, PHP 5)

mail Send mail

Description

bool mail ( string $to , string $subject , string $message [, string $additional_headers [, string$additional_parameters ]] )

Sends an email.

Parameters

to

Receiver, or receivers of the mail.

The formatting of this string must comply with RFC 2822. Some examples are:

[email protected]@example.com, [email protected] User , Another User

subject

Subject of the email to be sent.

Caution


3 of 51 6/17/2014 2:07 PM

Subject must satisfy RFC 2047.

message

Message to be sent.

Each line should be separated with a CRLF (\r\n). Lines should not be larger than 70 characters.

Caution

(Windows only) When PHP is talking to a SMTP server directly, if a full stop is found on the startof a line, it is removed. To counter-act this, replace these occurrences with a double dot.

additional_headers (optional)

String to be inserted at the end of the email header.

This is typically used to add extra headers (From, Cc, and Bcc). Multiple extra headers should be

separated with a CRLF (\r\n). If outside data are used to compose this header, the data should besanitized so that no unwanted headers could be injected.

Note:

When sending mail, the mail must contain a From header. This can be set with theadditional_headers parameter, or a default can be set in php.ini.

Failing to do this will result in an error message similar to Warning: mail():"sendmail_from" not set in php.ini or custom "From:" header missing. The Fromheader sets also Return-Path under Windows.

Note:

If messages are not received, try using a LF (\n) only. Some Unix mail transfer agents(most notably qmail) replace LF by CRLF automatically (which leads to doublingCR if CRLF is used). This should be a last resort, as it does not comply with RFC2822.

additional_parameters (optional)

The additional_parameters parameter can be used to pass additional flags as command lineoptions to the program configured to be used when sending mail, as defined by the sendmail_pathconfiguration setting. For example, this can be used to set the envelope sender address when usingsendmail with the -f sendmail option.

This parameter is escaped by escapeshellcmd() internally to prevent command execution.escapeshellcmd() prevents command execution, but allows to add addtional parameters. Forsecurity reasons, it is recommended for the user to sanitize this parameter to avoid adding unwantedparameters to the shell command.

Since escapeshellcmd() is applied automatically, some characters that are allowed as emailaddresses by internet RFCs cannot be used. mail() can not allow such characters, so in programs


4 of 51 6/17/2014 2:07 PM

where the use of such characters is required, alternative means of sending emails (such as using aframework or a library) is recommended.

The user that the webserver runs as should be added as a trusted user to the sendmail configurationto prevent a 'X-Warning' header from being added to the message when the envelope sender (-f) isset using this method. For sendmail users, this file is /etc/mail/trusted-users.

Return Values

Returns TRUE if the mail was successfully accepted for delivery, FALSE otherwise.

It is important to note that just because the mail was accepted for delivery, it does NOT mean the mailwill actually reach the intended destination.

Changelog

Version Description

4.3.0(Windowsonly)

All custom headers (like From, Cc, Bcc and Date) are supported, and are notcase-sensitive. (As custom headers are not interpreted by the MTA in the first place, but

are parsed by PHP, PHP < 4.3 only supported the Cc header element and wascase-sensitive).

4.2.3The additional_parameters parameter is disabled in safe_mode and the mail() functionwill expose a warning message and return FALSE when used.

4.0.5 The additional_parameters parameter was added.

Examples

Example #1 Sending mail.

Using mail() to send a simple email:

Example #2 Sending mail with extra headers.

The addition of basic headers, telling the MUA the From and Reply-To addresses:

'Reply-To: [email protected]' . "\r\n" .

'X-Mailer: PHP/' . phpversion();

mail($to, $subject, $message, $headers);

?>

Example #3 Sending mail with an additional command line parameter.

The additional_parameters parameter can be used to pass an additional parameter to the programconfigured to use when sending mail using the sendmail_path.

Example #4 Sending HTML email

It is also possible to send HTML email with mail().

$headers = 'MIME-Version: 1.0' . "\r\n";

$headers .= 'Content-type: text/html; charset=iso-8859-1' . "\r\n";

// Additional headers

$headers .= 'To: Mary , Kelly ' . "\r\n";

$headers .= 'From: Birthday Reminder ' . "\r\n";

$headers .= 'Cc: [email protected]' . "\r\n";

$headers .= 'Bcc: [email protected]' . "\r\n";

// Mail it

mail($to, $subject, $message, $headers);

?>

Note:

If intending to send HTML or otherwise Complex mails, it is recommended to use the PEARpackage PEAR::Mail_Mime.

Notes

Note:

The Windows implementation of mail() differs in many ways from the Unix implementation.First, it doesn't use a local binary for composing messages but only operates on direct socketswhich means a MTA is needed listening on a network socket (which can either on thelocalhost or a remote machine).

Second, the custom headers like From:, Cc:, Bcc: and Date: are not interpreted by the MTAin the first place, but are parsed by PHP.

As such, the to parameter should not be an address in the form of "Something". The mail command may not parse this properly while talkingwith the MTA.

Note:

It is worth noting that the mail() function is not suitable for larger volumes of email in a loop.This function opens and closes an SMTP socket for each email, which is not very efficient.

For the sending of large amounts of email, see the PEAR::Mail, and PEAR::Mail_Queuepackages.

Note:

The following RFCs may be useful: RFC 1896, RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049, and RFC 2822.

See Also

imap_mail() - Send an email message PEAR::Mail PEAR::Mail_Mime


7 of 51 6/17/2014 2:07 PM

add a note

User Contributed Notes 88 notes

updown53bimal at sanjaal dot com 2 years agoYou can write clean PHP code while creating the headers correctly. First, build a list

of all headers in an array. Then, glue them with "\r\n" character.

The code now looks clean and straight forward.

(Just compare it with the manual's example ;-) )

updown11yarik dot bohatsky at gmail dot com 2 years agoIf you want to send UTF-8 HTML letter you need to mention charset twice:

1) In message header:

2) In HTML header:

dans le Var.

';

In this case Outlook will also "understand" that message is encoded using UTF-8.

updown7pavel.lint at vk.com 2 years agoHere's a small handy function I use to send email in UTF-8.

updown5php dot net at schrecktech dot com 9 years agoWhen sending MIME email make sure you follow the documentation with the "70" characters

per line...you may end up with missing characters...and that is really hard to track

down...

updown5antoine dot php dot net at bonnefoy dot eu 9 months agoHello,

it's sometime hard to include multiple attachment, or to include pictures inside body.

Please find these 2 functions allowing sending email with attachment.

usage :


9 of 51 6/17/2014 2:07 PM

source :

// Message Body

$msg = $rn . '--' . $boundary . $rn;

$msg.= "Content-Type: multipart/alternative;" . $rn;

$msg.= " boundary=\"$boundary_content\"" . $rn;

//Body Mode text

$msg.= $rn . "--" . $boundary_content . $rn;

$msg .= 'Content-Type: text/plain; charset=ISO-8859-1' . $rn;

$msg .= strip_tags($content) . $rn;

//Body Mode Html

$msg.= $rn . "--" . $boundary_content . $rn;

$msg .= 'Content-Type: text/html; charset=ISO-8859-1' . $rn;

$msg .= 'Content-Transfer-Encoding: quoted-printable' . $rn;

if ($_headers) {

$msg .= $rn . '' . $rn;

}

//equal sign are email special characters. =3D is the = sign

$msg .= $rn . '' . nl2br(str_replace("=", "=3D", $content)) . '' .

$rn;

if ($_headers) {

$msg .= $rn . '' . $rn;

}

$msg .= $rn . '--' . $boundary_content . '--' . $rn;

//if attachement

if ($path != '' && file_exists($path)) {

$conAttached = self::prepareAttachment($path);

if ($conAttached !== false) {

$msg .= $rn . '--' . $boundary . $rn;

$msg .= $conAttached;

}

}

//other attachement : here used on HTML body for picture headers/footers

if ($_headers) {

$imgHead = dirname(__FILE__) . '/../../../../modules/notification

/ressources/img/template-H.PNG';

$conAttached = self::prepareAttachment($imgHead);




}

$imgFoot = dirname(__FILE__) . '/../../../../modules/notification

/ressources/img/template-F.PNG';

$conAttached = self::prepareAttachment($imgFoot);




}

}


11 of 51 6/17/2014 2:07 PM

// Fin

$msg .= $rn . '--' . $boundary . '--' . $rn;

// Function mail()

mail($to, $subject, $msg, $headers);

}

}

?>

updown2arunm 2 years agoIt is also advisable to set the return path in the headers; hence it will avoid the

email to land in the spam folder!

eg:

$headers.="Return-Path:\r\n";

updown2Porjo 3 years agoMake sure you enclose \r\n in double quotes (not single quotes!) so that PHP can

translate that into the correct linefeed code

updown1msheldon at desertraven dot com 9 years agoJust a comment on some of the examples, and as a note for those who may be unaware. The

SMTP RFC 822 is VERY explicit in stating that \r\n is the ONLY acceptable line break

format in the headers, though is a little vague about the message body. While many MTAs

will deal with just \n, I've run accross plenty of them that will exhibit "interesting"

behaviours when this happens. Those MTAs that are strict in compliance will definitely

break when header lines are terminated with only \n. They will also most likely break

if the body of the message contains more than 1000 consecutive characters without a

\r\n.*

Note that RFC 821 is a little more clear in defining:

"line

A a sequence of ASCII characters ending with a ."

RFC 821 makes no distinction between header lines and message body lines, since both

are actually transmitted during the DATA phase.

Bottom line, best practice is to be sure to convert any bare \n characters in the

message to \r\n.


12 of 51 6/17/2014 2:07 PM

* "The maximum total length of a text line including the is 1000 characters"

(RFC 821)

updown1shuitest at gmail dot com 3 years agoIf you use mutt, do as below,

/usr/bin/mutt -s '$subject' -f /dev/null -e 'set copy=no' -e 'set from =

"{$GLOBALS[cfg][email_from]}"' -a '$attach_file_full_path' '{$GLOBALS[cfg][email_to]}'

&1;

updown1Edward 4 years agoCurrently my hosting service is on Godaddy. When attempting to use the mail function

without the fifth parameter containing "-f", my message headers would not work.

Whenever your message headers do not work, simply try using the fifth parameter:

updown3g dot kuizinas at anuary dot com 1 year ago

(

'MIME-Version: 1.0',

'Content-Type: text/html; charset="UTF-8";',

'Content-Transfer-Encoding: 7bit',

'Date: ' . date('r', $_SERVER['REQUEST_TIME']),

'Message-ID: ',

'From: ' . $from,

'Reply-To: ' . $from,

'Return-Path: ' . $from,

'X-Mailer: PHP v' . phpversion(),

'X-Originating-IP: ' . $_SERVER['SERVER_ADDR'],

);

mail($to, '=?UTF-8?B?' . base64_encode($arr['subject']) . '?=', $arr['message'],

implode("\n", $headers));

}

?>

Here is my helper function for those who are having problems properly handling UTF-8,

subject, HTML, or even the headers data. I've been using it for over a year. It works

fine with simple emails.

For anything more advanced (specifically, handling attachments and multiple email

versions), you should be using an existing library like http://swiftmailer.org/.

updown1vigo dot von dot harrach at gmx dot de 3 years agoIf using sendmail as transport agent, setting the "DeliveryMode" to "background"

(asynchronous) instead of the default "interactive" (synchronous) makes mail() a lot

faster, while still sending immediately.

You can either use the "additional parameters", e.g. mail($to, $subject, $message,

$headers, 'O DeliveryMode=b'), or make this mode default by changing php.ini's

"sendmail_path" to 'sendmail -t -i -O DeliveryMode=b'.

updown1Marc Parillo 2 years agoIf you follow the suggested format for the $to field, you can list multiple addresses

in a comma-delimited string with spaces.

The spaces could be an issue if you're experiencing a similar problem. I was unable to

send an e-mail to multiple addresses using that format. It started working for me when

I removed all of the spaces in the $to string.

Example:

spaces

mail($to, 'the subject', 'the message');

?>

updown1shenyqwilliam 1 year agoIf you're sending a large attachment, you may encounter overflow problem.

AFAIK, two common limits could be responsible.

1. Postfix message size limit.

Edit /etc/postfix/main.cf . Change the value of "message_size_limit".

2. Apache memory size limit for scripts.

Edit /etc/php.ini . Change the value of "memory_limit".

//Then reload (or restart) Postfix and Apache.

//Empirically, sending 200MB attachment requires 500MB memory.

Be careful! Raising memory limits may cause unexpected consequences, and is hence

deprecated.

Recommended alternatives include:

* Pack and split attachment into several emails.

* Only include a link to the file. The receiver can download it later.

* Use IMAP/POP3 server (e.g. Dovecot).

updown1akam 6 years agoThere differenece in body, headers of email (with attachment, without attachment), see

this complete example below:

work great for me (LINUX , WIN) and (Yahoo Mail, Hotmail, Gmail, ...)

.rand(10000,99999);

$boundary2 =rand(0,9)."-".rand(10000000000,9999999999)."-"

.rand(10000000000,9999999999)."=:"

.rand(10000,99999);

for($i=0; $i < count($_FILES['youfile']['name']); $i++){

if(is_uploaded_file($_FILES['fileatt']['tmp_name'][$i]) &&

!empty($_FILES['fileatt']['size'][$i]) &&

!empty($_FILES['fileatt']['name'][$i])){

$attach ='yes';

$end ='';

$handle =fopen($_FILES['fileatt']['tmp_name'][$i], 'rb');

$f_contents =fread($handle, $_FILES['fileatt']['size'][$i]);

$attachment[]=chunk_split(base64_encode($f_contents));

fclose($handle);

$ftype[] =$_FILES['fileatt']['type'][$i];

$fname[] =$_FILES['fileatt']['name'][$i];

}

}

/***************************************************************

Creating Email: Headers, BODY

1- HTML Email WIthout Attachment!!

--$boundary1

Content-Type: text/html;

charset="windows-1256"

Content-Transfer-Encoding: quoted-printable

$HTMLMessage

--$boundary1--

AKAM;

/***************************************************************

2- HTML Email WIth Multiple Attachment

$TextMessage

--$boundary2

Content-Type: text/html;

charset="windows-1256"

Content-Transfer-Encoding: quoted-printable

$HTMLMessage

--$boundary2--

$attachments

--$boundary1--

AKAM;

}

/***************************************************************

Sending Email

***************************************************************/

$ok=mail($To, $Subject, $Body, $Headers);

echo $ok?" Mail Sent":" Mail not SEND";

?>

updown1roberto dot silva at mexicoshipping dot net 10 years agoIf you can't use or don't understand how to use the sendmail program from linux, you

can use a PEAR object to send mail.


18 of 51 6/17/2014 2:07 PM

In my case, i use a smtp server that require authentication, and sendmail configuration

is almost cryptic to me.

PEAR is already installed in PHP 4.0.3 , if not, you must go to http://pear.php.net/

and install it, in my case, I needed to add the Socket.php to the PEAR library.

updown0pierreantoine dot covet at gmail dot com 2 months agoHi,

I had lots of problems using the code in the exemple. HTML was not rightly formated in

my email.

Problem solved by replacing "\r\n" by "\n" as header end line.

updown0

Joost Brugman 1 year agoWhen using mail() under a windows installation (tested under Xampp 1.7.7) any line in

$headers that is (between the first and last properly formatted mail header and not a

properly formatted mail headers itself) or (that is empty) is removed. As a result MIME

formatted messages get scrambled. I am not sure if this behaviour is by design, but

this is what it seems to do.

Example $headers:

01 From: "me"

02 MIME-Version: 1.0

03 Content-Type: multipart/mixed;

04 boundary=streamline503e8a5d00efdMessage

05

06 --streamline503e8a5d00efdMessage

07 Content-Type: multipart/alternative;

08 boundary=streamline503e8a5d00efdBody

09

10 --streamline503e8a5d00efdBody

11 Content-Type: text/plain;

12 charset=UTF-8

13 Content-Transfer-Encoding: quoted-printable

14

15 This message is written in HTML only.

16

17 --streamline503e8a5d00efdBody

18 Content-Type: text/html;

19 charset=UTF-8

20 Content-Transfer-Encoding: quoted-printable

21

22 This is an email with htmlcontent

23 --streamline503e8a5d00efdBody--


19 of 51 6/17/2014 2:07 PM

24

25 --streamline503e8a5d00efdMessage--

26

27 .

Here, lines 05, 09, 10, 14, 15, 16, 17 are removed. The first properly formatted mail

header is on line 01. The last properly formatted mail header is on line 20. The before

mentioned entries are between 01 and 20, not properly formatted mail headers themselves

and are therefore removed.

Also, lines 21, 24, 26 are removed because they are empty.

As a result this message will be delivered, but the mime structure is broken, since

relevant lines are left out.

The solution is to pass lines 01 through 04 in $headers and to pass 06 through 26 to

$message. $message will passed unchanged and the mime structure will remain intact.

updown0

rexlorenzo at gmail dot com 2 years agoBe careful to not put extra spaces for the $headers variable.

For example, this didn't work on our servers:

$headers = "From: $from \r\n Bcc: $bcc \r\n";

But this did:

$headers = "From: $from\r\nBcc: $bcc\r\n";

Notice the removal of the spaces around the first \r\n.

updown0geeralo at gmx dot de 2 years agoHello programmers!

There is something important I want to notice about charsets here:

"Content-Type: text/plain; charset = \"UTF-8\";\n"

is right and not only

"Content-Type: text/plain; charset=UTF-8\n"

Hope I could help other people who frustrate while searching the same mistake like me.

Remember also to write only \r for windows and not for Linux-Servers.

And at the end of the header should be an extra blank line:


20 of 51 6/17/2014 2:07 PM

$headers .= "Content-Type: text/plain; charset = \"UTF-8\";\n";

$headers .= "Content-Transfer-Encoding: 8bit\n";

$headers .= "\n";

Greetings

updown0Anda 2 years agoSend Multi attachment email

$returnpath = "-f" . $sendermail;

$ok = @mail($to, $subject, $message, $headers, $returnpath);

if($ok){ return $i; } else { return 0; }

}

?>

updown0matthew dot mckay at uwrf dot edu 4 years agoNote: On some windows platforms this is NOT thread safe.

We are having email message bodies being sent out to the wrong headers multiple times,

some failing to send, and other bizarre stuff. If you google search for "php mail

thread safe" you can find a ton of relevant information.

This is not a bug in php, there have been multiple bugs closed with this issue being

dismissed as not an issue with PHP.

updown0

John 4 years agoA quick note about the optional flags that can be passed to sendmail. -f will set the

From address, -r will override the default Return-path that sendmail generates

(typically the From address gets used). If you want your bouncebacks to go to a

different address than the from address, try using both flags at once: "-f

[email protected] -r [email protected]"

updown0Erich at gasboysnospam dot net 5 years agoif your mail is failing (returns false) be aware that many servers are configured to

kill mail going out with a bcc or cc header.

The ideal workaround is to use the smtp functions which servers allow because of its

better audit trail. Alternatively call the mail function several times.

I've just spent about four hours trying to work out what I was doing wrong!!

updown0molotster on google mail com 5 years agoNote, that single line should not contain more than 78 character, but is not allowed to

contain more than 998 characters.

The possible consequences are:

Over 78 - clients are allowed to display the message in a "harder to read" way.

Over 998 - clients and servers are allowed to drop the message or cause any

buffer-limit error.


22 of 51 6/17/2014 2:07 PM

See:

http://www.faqs.org/rfcs/rfc2822 part 2.1.1.

updown0richard at richard-sumilang dot com 6 years agoIf you are using the sendmail app from an exim package or something you don't really

need to change the normal parameters PHP gives it (-t -i) as other posts described.

I just added "-f [email protected]" and it worked.

One thing that got me stuck for a few hours was trying to figure out why the

return-path was set as the user (user running php) and not what I was setting it with

the -f option then I later found at that in order to forcefully set the return-path the

user account running the command must be in exim's trusted users configuration! It

helps to add trusted_groups as well then everything works fine :)

- Richard Sumilang

up

down0panoramical at gmail dot com 7 years agoSearched for ages on the internet trying to find something that parses EML files and

then sends them...for all of you who want to send an EML files you first have to upload

it, read it, then delete it. Here's my function...it's specialised for a single form

where the user uploads the EML file.

// Now attempt to read the file

if($eml_file = file($file))

{

// Create the array to store preliminary headers

$headers = array();

$body = '';

$ii = -1;

// For every line, carry out this loop

foreach($eml_file as $key => $value)

{

$pattern = '^';

if(((eregi($pattern, $value)))||($carry == 'no'))

{

// Stop putting data into the $headers array

$carry = 'no';

$i++;

$body .= $value;

}

else

{

// Separate each one with a colon

if(($eml_file_expl = explode(':', $value))&&($carry == 'yes'))

{

// The row has been split in half at least...

if(isset($eml_file_expl[1]))

{

// Put it into the preliminary headers

$headers[$eml_file_expl[0]] = $eml_file_expl[1];

// There might be more semicolons in it...

for($i=2;$i

}

}

}

}

// Clear up the headers array

$eml_values = array();

$eml_values[to] = $headers[To];

$eml_values[from] = $headers[From];

$eml_values[subject] = $headers[Subject];

$eml_values['reply-to'] = $headers['Reply-To'];

$eml_values['content-type'] = $headers['Content-Type'];

$eml_values[body] = $body;

unlink($file);

return $eml_values;

}

}

else

{

return 'File not uploaded - there was an error';

}

}

}

// Takes information automatically from the $_FILES array...

$eml_pattern = eml_read_in()

// Headers definable...through eml_read_in() again, but I'm guessing they'll be the

same for each doc...

if(mail($eml_pattern[to], $eml_pattern[subject], $eml_pattern[content], $headers)) echo

'Mail Sent';

?>

updown


25 of 51 6/17/2014 2:07 PM

0Anonymous 7 years agocorrection for class multipartmail

if you are adding attachment first and then addmessage you can easy overwrite added

attachment - better use

updown0GwarDrazul 8 years agoThe article mentioned below is quite good to understand the problem of header

injection. However, it suggests the following as a solution: look for "\n" and "\r"

inside your user input fields (especially in those used for the $header param) and, if

found reject the mail.

Allthough this will probably work I still believe it is better to have a "white list"

of allowed characters instead of a "black list" with forbidden characters.

Example:

If you want a user to enter his name, then allow characters only!

If you want a user to enter his email adress, then check if the entry is a valid email

adress.

Doing so might automatically solve problems which you didn't think of when you created

the "black list". For SMTP headers colons are needed. If you check for a valid email

adress the hacker won't be able to enter colons inside that form field.

I suggest using regular expressions for those checks.

For more information about regular expressions see:

http://www.regular-expressions.info/

updown0jonte at macnytt dot com 9 years agoUsers of Mac OS X Server need to activate SMTP part of the Mailserver before this is


26 of 51 6/17/2014 2:07 PM

working.

Also note that if the ISP has blocked port 25 outgoing, you run into problems. You can

find more info about this in the SMTP server log in Server Admin application if you run

OSX Server.

updown0benles at bldigital dot com 9 years agoI get a 550 error when using mail() with this To format:

User

When it's changed to just the bare email, it works fine. Just FYI that some mail

servers may behave this way.

updown0

Sven Riedel 9 years agomail() requires /bin/sh to exist in Unix environments, next to a mail delivery program.

This is very relevant when setting up apache in a chroot environment. Unfortunately

this isn't anywhere in the documentation and took me several months to figure out.

updown0nospam at mingo dot ath dot cx 10 years agoIf you're using a linux server using Postfix, and your server hasn't the host name set

to a valid name (because it's behind a firewall in an intranet), it's possible that

when sending mails using the mail function, some mail servers reject them. This is

because they can't check the return path header. If you want to change the Return-Path

used by sendmail init the php.ini and edit the sendmail_path variable to this:

sendmail_path = "sendmail -t -i -F [email protected] -f [email protected]"

updown-1umangberi at gmail dot com 4 years ago

updown-1martin dot farrow at versacloud dot com


27 of 51 6/17/2014 2:07 PM

1 year ago

updown-1buraks78 at gmail dot com 3 years ago


28 of 51 6/17/2014 2:07 PM

updown-1sander at cartel dot nl 7 years ago

updown-1epheterson at gmail dot com 2 years ago

updown-1php at caves dot org dot uk 4 years ago


29 of 51 6/17/2014 2:07 PM

updown-1aldertb at XS4ALL dot nl 5 years ago

updown-1Gianluigi_Zanettini-MegaLab.it 6 years ago

updown-1bigtree at dontspam dot 29a dot nl 7 years ago


30 of 51 6/17/2014 2:07 PM

updown-1thomas at p-devion dot de 7 years ago

updown-1Anonymous 9 years ago

updown-1stevenlim at Edinburgh-Consulting dot com 11 years ago


31 of 51 6/17/2014 2:07 PM

updown-4krzysiek dot 333 at gmail dot com 2 years ago

updown-1Tobias Christensen 6 months ago


32 of 51 6/17/2014 2:07 PM

updown-1bburch at bouncingpixel dot com 1 year ago

updown

-1phadley at reliableid dot com 3 years ago

updown-1rch+php at online dot lt 4 years ago

updown-1dtbaker.com.au 4 years ago


33 of 51 6/17/2014 2:07 PM

updown-1d dot r at usask dot ca 5 years ago

updown-1alex_ramos at sourceforge dot net 5 years ago

updown-2mulllhausen 2 years ago

updown-1bob 5 years ago

updown-3ABOMB 2 years ago


34 of 51 6/17/2014 2:07 PM

updown-2php at ontheroad dot net dot nz

5 years ago

updown-1Ben Cooke 8 years ago

updown-1grey at greywyvern dot moc 9 years ago

updown-1


35 of 51 6/17/2014 2:07 PM

f dot touchard at laposte dot net 11 years ago


36 of 51 6/17/2014 2:07 PM

updown-3Maven1 at example dot com 4 years ago

updown-3webmaster at plumage dot nl 5 years ago

updown-3Alex Jaspersen 7 years ago


37 of 51 6/17/2014 2:07 PM


38 of 51 6/17/2014 2:07 PM

updown-2ittasks at gmail dot com 1 year ago


39 of 51 6/17/2014 2:07 PM

updown-2Max AT 2 years ago

updown-2saganwebdesign 2 years ago

updown-2Michiel Uitdehaag


40 of 51 6/17/2014 2:07 PM

3 years ago

updown

-2Systemx 4 years ago

updown-2Clayton Ginsburg 4 years ago


41 of 51 6/17/2014 2:07 PM

updown-2Tomer 4 years ago

updown-2Anonymous 4 years ago

updown-2phpcoder at cyberpimp dot ig3 dot net 6 years ago


42 of 51 6/17/2014 2:07 PM

updown-2johniskew2 7 years ago

updown-2Nimlhug 8 years ago

updown-2fontajos at phpeppershop dot com 8 years ago


43 of 51 6/17/2014 2:07 PM

updown-4Alex M. 4 years ago


44 of 51 6/17/2014 2:07 PM

updown-2Paul 10 years ago

updown-4orjtor 5 years ago

updown-4


45 of 51 6/17/2014 2:07 PM

fnjordy at gmail dot com 8 years ago

updown

-3akger1379 at gmail dot com 2 years ago

updown-5marcel dot portela at gmail dot com 5 years ago


46 of 51 6/17/2014 2:07 PM

updown-5Josh 7 years ago

updown-3

mortoray at ecircle-ag dot com 6 years ago

updown-3admin at chatfamy dot com 7 years ago


47 of 51 6/17/2014 2:07 PM

updown-3tdaniel at univ dot haifa dot ac dot il 7 years ago

updown-3junaid at techni-serve dot com 8 years ago


48 of 51 6/17/2014 2:07 PM

updown-5debis at woh dot rr dot com 2 years ago


49 of 51 6/17/2014 2:07 PM

updown-7me at arronwoods dot com 2 years ago

add a note

Mail Functionsezmlm_hashmail

Copyright 2001-2014 The PHP GroupMy PHP.netContact


50 of 51 6/17/2014 2:07 PM

Other PHP.net sitesMirror sitesPrivacy policy


51 of 51 6/17/2014 2:07 PM

Date post:	22-Nov-2015
Category:	Documents
Upload:	dickysurachman
View:	26 times
Download:	3 times

PHP_ Mail - Manual

Documents