AOL email problems - Looking for an extension to Mercury

androidery

posted Jan 1 '13 at 10:03 am

Yes I use mail merge too. This becomes easy for me to indentify emails

Yes I use mail merge too. This becomes easy for me to indentify emails <a mce_href="http://www.gamesfreeforandroid.com" href="http://www.gamesfreeforandroid.com">Android Games</a> <a mce_href="http://www.gamesfreeforandroid.com" href="http://www.gamesfreeforandroid.com">Free Android Games</a>

mcorrow

posted Oct 22 '12 at 3:59 pm

We send a lot of email to AOL users who have all optedin to receiving email from us. However, there are times that an AOL user clicks on the "call this spam" button, which then results in us receiving an email from AOL(feeback loop).

The problem is, that because of privacy concerns, they do not give us the AOL email address that reported our email as spam. (really helpful (NOT)). They do, however, give us the message ID of the email that was clicked on.

Since most of our emails are sent to multiple email addresses (usually in BCC), we cannot determine what email address the email was sent to...

So, what I am asking for is an extension that will take an email that has AOL addresses in the BCC or CC (or has multiple addresses in the To: field, sets up a separate email to each of the AOL email addresses(To:), and removes them from the original email, resulting in a complete email to each AOL address, so that when AOL sends us back a feeback loop, we can look up the message ID and find the email address being sent to.

Make sense?

Thanks for any help!

We send a lot of email to AOL users who have all optedin to receiving email from us.&nbsp; However, there are times that an AOL user clicks on the "call this spam" button, which then results in us receiving an email from AOL(feeback loop).&nbsp;The problem is, that because of privacy concerns, they do not give us the AOL email address that reported our email as spam. (really helpful (NOT)).&nbsp; They do, however, give us the message ID of the email that was clicked on.&nbsp;Since most of our emails are sent to multiple email addresses (usually in BCC), we cannot determine what email address the email was sent to...&nbsp;So, what I am asking for is an extension that will take an email that has AOL addresses in the BCC or CC (or has multiple addresses in the To: field, sets up a separate email to each of the AOL email addresses(To:), and removes them from the original email, resulting in&nbsp; a complete email to each AOL address, so that when AOL sends us back a feeback loop, we can look up the message ID and find the email address being sent to.&nbsp;Make sense?&nbsp;Thanks for any help!&nbsp;

KSQR

posted Oct 24 '12 at 12:32 am

[quote user="mcorrow"]

[chop]

[/quote]

While I don't know if there is such an extension in Mercury, I have had success in identifying such AOL addresses by using Mail Merge in Pegasus Mail (F1 | Index | Merge).

KSQR

[quote user="mcorrow"]We send a lot of email to AOL users who have all optedin to receiving email from us.&nbsp; However, there are times that an AOL user clicks on the "call this spam" button, which then results in us receiving an email from AOL(feeback loop).[chop] &nbsp;So, what I am asking for is an extension that will take an email that has AOL addresses in the BCC or CC (or has multiple addresses in the To: field, sets up a separate email to each of the AOL email addresses(To:), and removes them from the original email, resulting in&nbsp; a complete email to each AOL address, so that when AOL sends us back a feeback loop, we can look up the message ID and find the email address being sent to.&nbsp;[/quote]While I don't know if there is such an extension in Mercury, I have had success in identifying such AOL addresses by using Mail Merge in Pegasus Mail (F1 | Index | Merge).KSQR &nbsp;

FJR

posted Nov 21 '12 at 8:08 pm

Is there any reason not using mailinglists for those mails?

When using mailinglists Mercury's MAISER is capable / may be configured to send an individual mail to every member of that mailinglist with an individual return-path. Mercury remembers that return-path and for which mailadress it was generated. On return of an errormessage on that return-path you may configure the mailinglist to remove or deactivate the involved mailadress from the list - automatically. For shure there is more load on Mercury, but would be a simple solution.

Is there any reason not using mailinglists for those mails?When using mailinglists Mercury's MAISER is capable / may be configured to send an individual mail to every member of that mailinglist with an individual return-path. Mercury remembers that return-path and for which mailadress it was generated. On return of an errormessage on that return-path you may configure the mailinglist to remove or deactivate the involved mailadress from the list - automatically. For shure there is more load on Mercury, but would be a simple solution.&nbsp;

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history