WireMailSmtp

[Peter Knight]

Hey Adrian. I did thanks.
I'll open another thread as my issue seems to be now unrelated to WMSMTP

[bluellyr]

Hi,

it is possible to set the WireMailSmtp config settings at runtime and send email using different settings for each user?

Thank you

[horst]

Yes you can read and write modules config data via PWs API for all modules. Please refer to the docs, or search the forum via google for something like $modules->get("WireMailSMTP")-> getConfigData(), or readConfigData() ? and ->writeConfigData($data).

Sorry, I'm on mobile and cannot provide links or exact code snippets ATM.

----

EDIT:

you can use this:

$data = wire('modules')->getModuleConfigData("WireMailSmtp");

// or, regarding on scope,
$data = $modules->getModuleConfigData("WireMailSmtp");

after modifying, you can write it back:

wire('modules')->saveModuleConfigData("WireMailSmtp", $data);

// or

$modules->saveModuleConfigData("WireMailSmtp", $data);

Edited March 12, 2016 by horst
added code snippets

[opalepatrick]

I wonder if someone could give me an idea how to use the attachment aspect to WireMailSmtp? I am doing a simple form that allows the upload of pdf's only. I am unsure how to access the file size, type, etc. so that I can sanitize things a bit.

Thanks in advance.

Edited March 24, 2016 by kongondo
No need to start a new topic for a module that has its own support forum + have a look at page 1 of this thread

[opalepatrick]

Thanks Kongondo. By the way, page 1 doesn't answer this question (unless I am being a complete dunce!)

[horst]

Thanks Kongondo. By the way, page 1 doesn't answer this question (unless I am being a complete dunce!)

It does:

attachment ($filename) - add attachment file(s) - string or array()

$mail = wireMail(); 
$mail->attachment($filename); // string $filename or array $filenames

what means: you can add any single file path as a string with the attachment() method, or you can add multiple files at once with its pathes stored in an array.

Everything else, e.g. how you submit your form and / or upload the files, does not belong to WireMailSmtp. For this, you may find information and examples on php.net.

Edited March 24, 2016 by horst

[netcarver]

Attachments work very well using this mailer. I'm using it to send out event photos to purchasers - nice, nice, nice. Thanks for the work on this, Horst!

[opalepatrick]

OK thanks Horst. I did start to use it this way, but was unsure about the other aspects and if more was included. I don't have a problem with the validation/sanitising routines per se. So thank you.

[alan]

Horst, please can you tell me where the changelog for 0.2.2 is (I checked the usual spots), or am I safe to assume any _ . _ . N level change is so minor I can always just install it without any other checking on my sites etc? Thank you

[horst]

@alan: I just updated the readme: https://github.com/horst-n/WireMailSmtp

[alan]

@horst — you're boss

[mr-fan]

Using WireSmtp for WireMail so far...so great...my question is more based on the basic WireMail thing i think but i'm not shure:

using this call:

$mail = wireMail();
$mail->to($u->email);
$subject = '=?UTF-8?B?'.base64_encode('ÖÄÜ ö ä ü ß').'?=';
$mail->subject($subject);
$mail->bodyHTML($emailContentHtml);
$mail->send();

i don't get german umlaute öäüß working in the subject??

I've read the forum and stackoverflow but this is the only solution everyone points out so i'm a little lost...how to debug or get it work.

Best regards mr-fan

[horst]

You don't need anything like this. Just make sure that your php files are really stored in utf-8 encoding!! (PHP files you need to check in this reagrd are: the calling template file(s), the WireMailSMTP module files and the base WireMail files) Normally they all should be in utf-8 encoding, but better you check this thouroughly.

Then it works with simply using:

$subject = 'Ö Ä Ü ö ä ü ß';

I tested this just yet. The source of the received email looks like:

Subject: Wiremail-SMTP Test 15:57:23 =?UTF-8?q?=C3=A4=C3=B6=C3=BC_=C3=84=C3=96=C3=9C_=C3=9F?=
X-Mailer: ProcessWire/WireMailSmtp
Date: Wed, 8 Jun 2016 13:57:25 GMT +00:00
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

It does automated encoding, but you don't have to do anything by yourself.

[mr-fan]

Thank you very much - has a wrong encoding on my PHP Editor setup....so you saved my day!

Best regards mr-fan

[titanium]

Horst did a nice job building this module.

One thing I'm missing though: Is there a method to embed an image? (cid-method). I've searched through the documentation of Manuel Lemos classes and found the following:

Quote

 

Alternatively, an image file can be embedded in an HTML message using multipart/related message parts. This type of message part is composed by creating the image file part with the CreateFilePart function.

Then use the GetPartContentID function the image part identifier text. Prepend the string 'cid:' to this identifier to form a special URL that should be used in the HTML part to reference the image part like this:

$image_tag = '<img src="cid:' . $message_object->GetPartContentID($image_part) . '">';

When you have composed the whole HTML document, create the HTML message part with the CreateHTMLPart or the CreateQuotedPrintableHTMLPart functions, and finally use the CreateRelatedMultipart function to create a message part that can be added to the message with the function AddAlternativeMultipart like HTML messages with alternative text parts described before.

Note that the HTML part must be the first listed in the parts array argument that is passed to the function CreateRelatedMultipart, or else the message may not appear correctly.

Note also that when you are composing an HTML message with embedded images and an alternative text part, first you need to create the multipart/alternative part with the HTML and the text parts using the CreateAlternativeMultipart function, and then you add the multipart/related part to the message with the AddRelatedMultipart function, passing an array of parts that lists first the multipart/alternative part and then the image part created before.

 

Seems the classes support embedding, but I guess the module does not yet?

[horst]

No, the module doesn't support it. And I cannot see much benefit for it. This is the only part what would be a really pain in the ***, if one would try to integrate this. And AFAIK, you get the same effect if you use the base64 data with your img src. And this can be done outside of the module.

 

// when building your HTML-content, you simply can add something like

$htmlcontent .= "<img src='data:image/png;base64," . base64_encode(file_get_contents($image->width(300)->filename)) . "' />";

 

Edited June 21, 2016 by horst
added code example

[mrkhan]

Hello,

I am building one form to send email with WireMailSmtp

every thing is working fine, only thing attachments are sending with email without any extension.

what i want to do is
Send email with attachment, this script send attachment with email but files are names like bnvft & angth (random names without extensions).
 

here is my code

if (isset($input->post->submit)) {

$form = array(
'name' => $input->post->name,
'email' => $input->post->email,
'message' => $input->post->message,
'email2' => $input->post->email2
);

$photo=$filetemp = $_FILES["photo"];
/// how to check that file is only image

$resume=$filetemp = $_FILES["resume"];
/// how to check the file is only PDF or word file

/// email12 is for spam boot
if($form[email2] =="")
{
$toName='my website';
$toEmail=$page->email;
$subject="CV EMail";
$textBody= "Full name: $form[name]\n" .
               "Email: $form[email]\n" .
			   "Message: $form[message]";

$mail = wireMail();
$mail->to($toEmail, $toName);
$mail->from = $toEmail; 
$mail->subject($subject);

$mail->attachment($photo);
$mail->attachment($resume);

$mail->body($textBody);

$numSent = $mail->send();
if($numSent)
{
  $output="Message Send";
}else{
  $output="Message Not Send";
}

}

}

[horst]

From where do you get the file(s)?

Can you please show this exact code snippet? (and only this, please)

The module is working fine. It just uses what you passes to it. So, you probably do something wrong in regard of your filenames / files passing to the module.

[mrkhan]

Hello @horst,

Thanks for quick response, i am getting files from form , bellow is my form code

<form id="contactForm" action="" method='post' enctype="multipart/form-data" accept-charset='UTF-8'>
 <input type='text' name='name' id='name' required="" value='' maxlength="50" /><br/>
<input type='email' name='email' id='email' required="" value='' maxlength="50" /><br/>
<input type="file" name='photo' id='photo' accept='image/jpg,image/jpeg,image/gif,image/png' /><br/>
<input type="file" name='resume' required="" id='resume' accept="application/pdf,application/msword" /><br/>
</form>

and my php code is as i post above
 

$photo=$_FILES["photo"];
$resume=$_FILES["resume"];

$mail = wireMail();
$mail->to($toEmail, $toName);
$mail->from = $toEmail; 
$mail->subject($subject);

/// these are attachemnts
$mail->attachment($photo);
$mail->attachment($resume);

$mail->body($textBody);
$numSent = $mail->send();

But when i got email i got two attachments with random names but no extension.

Thanks

 

[horst]

Yes you get random names because you assigned them to your variables. If you don't like them, don't assign them.

$photo=$filetemp = $_FILES["photo"]["tmp_name"];

This has nothing to do with my module nor with PW. I suggest to follow up with the php docs on how to upload files, followed by how to use it with PWs WireUpload class. There you also have validation options for filetypes. IMO this is essential knowledge in regard of security to your website. Open it for uploads must be done in a secure way. Therefore you must understand, at least to a small extend, what you are doing.

[mrkhan]

3 minutes ago, horst said:

Yes you get random names because you assigned them to your variables. If you don't like them, don't assign them.

$photo=$filetemp = $_FILES["photo"]["tmp_name"];

This has nothing to do with my module nor with PW. I suggest to follow up with the php docs on how to upload files, followed by how to use it with PWs WireUpload class. There you also have validation options for filetypes.

even i use bellow i code i am getting same random names with no extension, why extensions are missing ?
 

$photo=$_FILES["photo"];
$resume=$_FILES["resume"];

[horst]

Once more but last one too: I strongly suggest to read the php docs on how to upload files:

http://php.net/manual/en/features.file-upload.php

 

[netcarver]

@mrkhan You are not handling the uploads correctly at the moment, take a close look at the first comment on the page horst pointed you to. It shows you what you need to know about handling file uploads. You should not trust the file-name supplied by the upload so that example shows you how to

• validate that the file was supplied via an upload (using the move_uploaded_file() function)
• how to name it without having to trust the supplied file name
• how to validate the mime type of the file
• how to append the extension that represents the file type of the uploaded file

You just need to remember the name you gave it when you moved it and attach that to your outgoing email. I've updated part of the code from the comment I linked to so that you can see how you might generate the new name and extension.

    // You should name it uniquely.
    // DO NOT USE $_FILES['upfile']['name'] WITHOUT ANY VALIDATION !!
    // On this example, obtain safe unique name from its binary data.
    $new_name = "./uploads/" . sha1_file($_FILES['upfile']['tmp_name'] . ".$ext";
    if (!move_uploaded_file($_FILES['upfile']['tmp_name'], $new_name))) {
        throw new RuntimeException('Failed to move uploaded file.');
    }

    // Now attach the uploaded, validated & renamed file to your email.
    $mail->attachment($new_name);

You'll need to tailor the code to do the needed validation on both of the files you want your users to upload of course. Don't forget to change where you want the files copied to as well.

[mrkhan]

Thanks @netcarver

[krisj]

a little feature request. what do we think? https://github.com/horst-n/WireMailSmtp/issues/7