• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

XENFORO Exclusive Offer: 100 Million Transactional Emails Free!

Pierce

Well-known member
#24
@Pierce , we are sorry for the inconvenience. This happened due to some unplanned activity on website.
This activity has not affected email delivarability. No delays, all the emails are going on time.
OK, it's just I was giving a recommendation to your platform elsewhere on xenforo. When I checked the links the site was dead this why I asked.
 

Mouth

Well-known member
#29
We just ditched SendGrid for Pepipost and saved almost 80 dollars a month. So far so good. I really enjoy the dashboard.
Thanks you @BamaStangGuy ! Encouraging words from happy customers like you keep us motivated. Savings customers’ money has been our motto. Glad you like our services :)
Have just been trialling Pepipost myself for less than 24 hours, and it is being rejected by a large number of recipient mail servers, due to Pepipost having a poor spam source reputation. A much larger number of my sites transactional emails are now being rejected/bounced. Think I'll have to go back to Amazon SES, who doesn't have these reputation problems. Examples .....

Code:
"smtp;550 ""JunkMail rejected - 175ip34.etransmail.com [175.158.64.34]:46724 is in an RBL, see Poor Reputation. See http://psky.me?175.158.64.34""

"smtp;554 icp-osb-irony-in15.iinet.net.au Your access to this mail system from 175.158.64.34 has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient vi

"smtp;522 email sent from (175.158.64.34) found on industry IP blacklists, please contact your mail sending service or use an alternate email service to send your email. Guide for bulk senders www.bt.com/bulksender

smtp;554 ipmailmx06.adl2.internode.on.net ESMTP; 175ip34.etransmail.com [175.158.64.34] in MX's BLACKLISTsbrs; crashed into the sunse

"smtp;554 mscip02.mailsentry.net.au Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.

"smtp;554 mx-asia.hafele.com Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
At least 2 of those recipient mail servers represent significant ISP's that my target audience would utilise.
 

Brent W

Well-known member
#30
I haven't ran into these issues but will keep my eye open. It would be nice to support dedicated ip addresses. We had one with SendGrid which solved this problem.
 
#31
Have just been trialling Pepipost myself for less than 24 hours, and it is being rejected by a large number of recipient mail servers, due to Pepipost having a poor spam source reputation. A much larger number of my sites transactional emails are now being rejected/bounced. Think I'll have to go back to Amazon SES, who doesn't have these reputation problems. Examples .....

Code:
"smtp;550 ""JunkMail rejected - 175ip34.etransmail.com [175.158.64.34]:46724 is in an RBL, see Poor Reputation. See http://psky.me?175.158.64.34""

"smtp;554 icp-osb-irony-in15.iinet.net.au Your access to this mail system from 175.158.64.34 has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient vi

"smtp;522 email sent from (175.158.64.34) found on industry IP blacklists, please contact your mail sending service or use an alternate email service to send your email. Guide for bulk senders www.bt.com/bulksender

smtp;554 ipmailmx06.adl2.internode.on.net ESMTP; 175ip34.etransmail.com [175.158.64.34] in MX's BLACKLISTsbrs; crashed into the sunse

"smtp;554 mscip02.mailsentry.net.au Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.

"smtp;554 mx-asia.hafele.com Your access to this mail system has been rejected due to the sending MTA's poor reputation. If you believe that this failure is in error, please contact the intended recipient via alternate means.
At least 2 of those recipient mail servers represent significant ISP's that my target audience would utilise.

Hello @Mouth - You were on shared IP pool which works well but we saw a malicious sender got us listed yest. We have changed the IPs and also removed the bad sender. We regret the inconvenience. Let us know the response now?
 
#34
@Sachin Tiwari when will the ability to define a Bounce Notification email address be working again so that Xenforo's core bounce handling functionality can be utilised?
Please do the below settings:
Go to Account Settings -> Customize-> Bounce Notification->Enter email ID-> Save

Above steps are possible only if Custom Envelope is set.
To set custom envelope go to Domain Management-> Settings(symbol)->Custom Envelope->Verify your sub domain->Save
 

Mouth

Well-known member
#35
Please do the below settings:
Go to Account Settings -> Customize-> Bounce Notification->Enter email ID-> Save

Above steps are possible only if Custom Envelope is set.
To set custom envelope go to Domain Management-> Settings(symbol)->Custom Envelope->Verify your sub domain->Save
As I stated, it's broken and doesn't work.
Despite entering an en email address here (custom envelope is already active), you system just changes it to 'discard:[127.0.0.1]' immediately afterwards.

Pepipost representative Prathamesh Walke already acknowledged, via support email response, 3 days ago that this functionality is broken.

Since putting site emails through Pepipost, I found;
  • Too many recipient mail servers bouncing due to Pepipost having poor DNSBL reputation (you fixed by moving me to a different sender ip address)
  • Bounced email notification functionality doesn't work
  • Click tracking functionality that replaces 'base href' statements within emails, and thus causes image URL's within emails to fail
It really feels to me like Pepipost is a beta service and has a way to go before it's ready for usage that relies on email communication/marketing.
 
#36
As I stated, it's broken and doesn't work.
Despite entering an en email address here (custom envelope is already active), you system just changes it to 'discard:[127.0.0.1]' immediately afterwards.

Pepipost representative Prathamesh Walke already acknowledged, via support email response, 3 days ago that this functionality is broken.

Since putting site emails through Pepipost, I found;
  • Too many recipient mail servers bouncing due to Pepipost having poor DNSBL reputation (you fixed by moving me to a different sender ip address)
  • Bounced email notification functionality doesn't work
  • Click tracking functionality that replaces 'base href' statements within emails, and thus causes image URL's within emails to fail
It really feels to me like Pepipost is a beta service and has a way to go before it's ready for usage that relies on email communication/marketing.

Sorry for the inconvenience, we are looking into both of your pending issues on high priority - "Bounced email notification" and "Click tracking functionality".
You can expect a solution from our end within next 48 hrs. we are working hard every day to improve the quality of our service and your inputs are highly appreciated.
 

Mouth

Well-known member
#37
Sorry for the inconvenience, we are looking into both of your pending issues on high priority - "Bounced email notification" and "Click tracking functionality".
Suggest you get someone whom understands HTML and what a 'base href' is to look at the issue. Prathamesh clearly does not, and his/her email responses are not helpful.
When XenForo sends emails to Pepipost SMTP with 'base href' of
Code:
<base href="https://mydomain.com" />
and Pepipost changes this, with click functionality tracking turned on, to
Code:
<base href="http://delivery.mydomain.com/lt.pl?id=28601chhTAFAPVFZSHgEFVgADAAAHUxgUlARDl4lQVFSVVxeVAoQHgtTTAcWHgABXgUGBAEPU1UJB1ZWAFcB&flWRAXQBENTUkNB0VHD1RWQh5ZBhAWUBdO" />
causing 'img src' within the email of
Code:
<img src="styles/mydomain/style/logo.png" border="0" />
to fail with a 404 error.

Appears your click tracking code is doing a grep/find and replace on "href=" which catches both 'base href' and 'a href'. The grep/find should be on "<a href="
 

Mouth

Well-known member
#38
I've now moved back to Amazon SES.
Bounced emails aren't delivered back to you, and Yahoo started blocking emails from me sent through Pepipost (back to Amazon and immediately working fine).
IMHO, it's just not an appropriate service for community sites with transactional or newsletter type emails. It's far too loose with spammers and marketers sending junk mails.
 
#40
I've now moved back to Amazon SES.
Bounced emails aren't delivered back to you, and Yahoo started blocking emails from me sent through Pepipost (back to Amazon and immediately working fine).
IMHO, it's just not an appropriate service for community sites with transactional or newsletter type emails. It's far too loose with spammers and marketers sending junk mails.
Sorry for the delay in response. We have fixed both the issues, they were related to configuration settings at our end. Yahoo was blocking the domain which we have changed on the same day itself.
And, bounce forwarding was dependent on a custom envelope which is now set and working fine.

We have observed that you have removed the CNAME record for your sub domain. I completely apologize for the bad experience you had with our services. We are always open for the feedbacks and want to keep improving our services. Could you please restore the sub-domain settings and give Pepipost a try. I have emailed you my skype-id, so that we can chat in real time for any issues for faster resolution.