I'm using PHPMailer to send PDF attachments to an online fax machine. My problem is when I send a "body" through even if it's just a 'space' it will add a separate page since it sees the character. Is there a way to send mail WITHOUT a body? If i try sending without a body i just get the error "Mailer Error: Message body empty" :(
You need to update version of PHPMailer. This issue was listed as a bug some time ago. It appears it was fixed in newer versions.
Related
I need a information about PHPMailer about replying my own mails.
I need send a empty mail(subject, body), and when the first mail sent second mail need sending with replying first mail.
That's possible ?
I tried but never can repyling my own mails.
Yes, but PHPMailer won't do this for you. You will need to do it by getting and setting appropriate headers, in particular the Message-ID header that identifies each message, and the In-Reply-To and References headers which are used to track whether something is a reply. Probably the best way to see these working is to simulate it using your regular email client - Outlook, Gmail, Apple Mail – all of which will set those headers correctly.
I am currently developing a gmail addon. The addon sends an email, with an attached eml file, to a particular recipient. Unfortunately, the recipient is not able to open the eml file attached with the email I sent via GMAIL API. If they click on the attached eml file they will receive the message "An error occurred while loading the attached message."
I found two issues, which might be related to this issue, when I analyzed the data I saw when I clicked "show original" on the email. One is that all emails I sent via GMAIL API have the "Received from xxxxxxxxxxx named unknown by gmailapi.google.com with HTTPREST" header. And that the entire base64-encoded eml file is missing in the content of the email. Please see image below :
Is this related to Emails sent via GMAIL API are flagged as Phishy? Or am I missing or doing something wrong? If I set the "attachment-type" to "text/plain" then the base64-encoded eml file data is present and viewable when I "show original" the email. Thank you all in advance.
#GovZ you can use MailApp.send rather than GmailApp.send, along with setting the content-type to "message/rfc822" and the email should preview correctly.
Details here: https://issuetracker.google.com/issues/155736170
When sending drafts via the Gmail REST API, the message in the "Sent Mail" folder can't be opened by the sender in the new Gmail UI. You get the error message "The conversation that you requested could not be loaded.".
The message on the recipient side can be opened without problem though, new UI or not.
Reverting to the old/classic Gmail UI allows the sender to open the sent message.
Steps to reproduce:
Compose a draft in Gmail (new or old UI doesn't matter)
Find the draft ID via GET https://www.googleapis.com/gmail/v1/users/me/drafts
Send the draft via POST https://www.googleapis.com/gmail/v1/users/me/drafts/send with body {"id": "<draftId>"}
Go back to Gmail and switch to the new Gmail UI, then attempt to open the recently sent draft in the Sent folder. Attempting to open the message will fail.
Revert to the old/classic Gmail UI and open the recently sent draft in the Sent folder. You will be able to open the message without issues.
The recipient will be able to open the message without issues, using either the new or old UI.
UPDATE
When the broken sent email receives a reply, it seems to get 'fixed' and the sender can now open the sent email from the new Gmail UI. This seems to suggest that the REST API is missing something that gets fixed once the thread is updated by other means?
The error message in the browser console when attempting to open the broken sent message:
Error: Ppa No message loaded when we received the DETAILED_CONVERSATION_MESSAGES_LOADED event.
I can't reproduce this. Note that in the reproduction steps #2 is unnecessary. Instead, the result of drafts.create() in #1 should be analyzed, the id of the new draft message is present there.
Also worth noting, Draft IDs are not the same as Message IDs. The response of drafts.create() and drafts.update() will be a Draft ID while the result of drafts.send() will be the message ID. When viewing the sent message in Gmail UI make sure you are using the message ID.
I am new to node.js where in my requirement is to grab received email subject, attachment and email body using node.js I am not able to find any solutions. Can anyone suggest me what kind of approach I should take.
I've read that nodemailer only permits to send mail (if I m not wrong).
You should use a librarie that allow you to receive message, like using POP3 protcole (https://www.npmjs.com/search?q=pop3)
Recieving an error Code when making a demo call using the rest api v2 with an an email configured as a prospect to a template. Can anyone please let me know why this is being returned and it seems to work fine when the request is with a test#email.com
errorDetails INVALID_EMAIL_ADDRESS_FOR_RECIPIENTThe email address for one of the recipients is not valid.
Answering my question again - ive actually removed the email tag from the envelope request , this was causing the problem
The DocuSign system does not know if it's actually a valid email address (it would have to do a test send to figure that out), the only validation that is done through the platform is on the actual format of the email address.
If it's not in the format (at least one character)#something.something then it will be flagged as an invalid email address. Looks like you've figured this out on your own though.