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.
When user wants to reply on a email that he has received, I want to customize the reply To field in Hybris so that It can be another email instead of the sender's email.
Could any one suggest how it can be achieved?
Just have a look in your local.properties. There I found the following property:
# Email address used for replying to emails (mandatory)
mail.replyto=dev#hybris.de
Overwrite
de.hybris.platform.acceleratorservices.email.impl.DefaultEmailGenerationService#generate
and create a new method like de.hybris.platform.acceleratorservices.email.impl.DefaultEmailGenerationService#createEmailMessage
that accepts a replyTo address as parameter. Then call your createEmailMessage method instead the old one.
I am working on a CRM.
We recieve reply from the leads and customers.
We have sequences(Workflows and scripts) by which we send Emails to our customers or leads. When they reply to the mail I can see the mail in the netsuite as well as the sending mail id recieves them as response.
I want to forward this mails to a particular mail id which is not the sending nor cc or bcc mail id. How can i achieve this? which script needs to be written or any workflow to be created for this.
Thanks In advance
Gladiator
Try build an action on top of the "event" record maybe? Whenever an email is created with said characteristics do X.
Same could be done searching for customer records on a scheduled basis.
You could also try building an email plugin to collect responses.
For some reason receipt emails are not being BCC'd to any address I enter in the email template. I've tried multiple addresses. Receipt comes through fine to customer, though.
Usually when this happens it's getting caught in a spam filter (e.g. many spam filters will catch mail if the "from address" and "to address" are the same). The BCC is sent exactly the same way as the customer email, so if the customer email is coming through it's highly unlikely to be Store/EE's fault.
What is the exact difference between the envelope and the email in smtp?
Why does the protocol need the envelope? In snail mail, the letter needs not contain addresses and is not visible to the postman (at least that's what you want to believe), so all the routing is made entirely based on the envelope and that is clear to me.
However in e-mail, the letter itself is parseable and has headers such as From: and To:. Why is that not enough to route email? Why do we need an envelope?
And what is the meaning of a divergence between the envelope and the email itself? Does it necessarily mean that someone is trying to game the system, or is it, under certain circumstances (what circumstances?), legal to have a difference between them.
Your clarifications are more than welcome.
Puzzled email receiver.
The recipient address in the SMTP RCPT TO: command is what mail transports use to determine the actual recipient of an email. The addresses in the To: and Cc: headers are there for mail readers to display to users who the recipients are, but they're not actually used by mail transports.
Most mail clients set the same addresses in SMTP RCPT TO: and MAIL FROM: commands that they insert in To:, Cc:, and From: headers, so the "envelope" addresses will be the same as the addresses in the headers.
Envelope and header addresses will usually agree for most legitimate mail. Notable exceptions are Bcc: addresses and mailing lists.
Spammers often forge header addresses to try to avoid spam filters.
The bottom line is that the overhead would be too great. When mail servers are processing millions of messages per day, it's much faster during the SMTP session (The Envelope) when the mail server can process individual commands.
If you didn't use an Envelope, you would have to push the entire message at the SMTP server, before you could find out if the message needs to be rejected. Some messages are quite large (I've seen 100+Meg messages working with GIS images).
By using an Envelope, we can issue specific 1 line commands against the mail server, and the mail server will tell us if we are successful or not, right then and there.
The envelope is used by the SMTP server and the message headers are used by a mail reader as everyone else has said.
What has not been said is that the RCPT TO: is used to route the message to a specific user regardless of where the user's name appears in the headers. The user does not necessarily need to appear in the To: or even the Cc: headers. Think of a Bcc: where the only thing that the receiver knows is who the message was from. In this case, the To: and CC: headers should be empty - hence the blind part of BCC. In another case, if an email message has the user mentioned in the CC list along with 10 other users, how can the SMTP routing pick the appropriate user. The answer is that it uses the RCPT line to route the message.
This is also used when routing via mailing lists. The To: header will contain the mailing list e-mail address. An SMTP system will generate separate messages for each user in the list each with a specific RCPT TO: user#host... envelope. In this case, the user's name will not even appear in any of the other headers.
An email message is very similar to a physical letter that you would send in the mail. There is an envelope, with To/From information, and there is the actual letter on the inside, with it's own To/From information. The envelope to/from information is the real information that is used for message delivery, for both email servers and post offices.
When an envelope comes into a post office, they inspect the To address on the envelope, and send it to the correct destination. The post office workers have no knowledge of the letter inside the envelope. The letting inside could have completely different To/From information than the envelope says. The Envelope could say the message is to Bob, but the letter inside may say it's for Alice. Or in real world: The envelope could say the message is to SomeCompanyName, and when secretary open envelope, letter inside say, it's is for Mr. Brown which work in SomeCompanyName.
Source: Email Envelope vs Email Header