[RANDOM_CONTENT: Hello | Howdy | Hi]
Use a preheader text to avoid this. (see the preheader field in campaign setup step)After random content yahoo puts first email text after subject..
It always worked for me in either way, but if for you it works with spaces, use spacests fixed now or do we need to put a blank space after : and after every | like you did ?
@twisted1919 - I've just updated to the latest version and the [RANDOM_CONTENT:Hey|Hello|Hi] does not work. I tested on a real list. I've also tried with spacing and it also doesn't work. Did the last update break this by any chance? i.t's the 1.8.6 version I think.Use a preheader text to avoid this. (see the preheader field in campaign setup step)
It always worked for me in either way, but if for you it works with spaces, use spaces
@laurentiu -@Alex Read - it is in tests, fix will be included in the next update.
The issue seems to only happen when you have multiple random-content tags per line. If you have them in separate places, they work just fine. so it's not completely broken, but we will push the version on Monday most likely.1) that's pretty big! All mailers have weird tags in them now. Any idea when the fix will be pushed out?
Yes.Will the attached block all emails with the word 'abuse' in them?
Those are emails you should never have in your system.with the words abuse@spamcop.com, and similar
1) I do have multiple in a message. I have them for the greeting & the salutation. (goodbye etc)The issue seems to only happen when you have multiple random-content tags per line. If you have them in separate places, they work just fine. so it's not completely broken, but we will push the version on Monday most likely.
Yes.
Those are emails you should never have in your system.
Yes, see any of the extensions: https://store.onetwist.com/index.php?product[]=mailwizz&tag[]=email validation4) Is there a way to have an email address validated before being added to a list?
E.g. BEFORE a subcriber is 'confirmed' it checks if the email is valid using an email verification service?
This was already possible via filters:5) Did you ever add a feature that let's us choose the case of custom fields?
e.g. FNAME = will always use format Fname (e.g. Alex, Sean, etc) so the first letter is capitalised? It looks much better when it says 'Hey Alex,' rather than 'Hey ALEX', in the ARs. Some people enter in their details in caps.
[FNAME:filter:lowercase|ucfirst]
4) Before I buy it can I confirm -Yes, see any of the extensions: https://store.onetwist.com/index.php?product[]=mailwizz&tag[]=email validation
This was already possible via filters:
Code:[FNAME:filter:lowercase|ucfirst]
I saw that and updated asap!@Alex Read - release was pushed for several days.
@twisted1919 - can it:@Alex Read - Based on those requirements, you might be better with some custom code to do all that, it should be doable and tailored to your specific needs.
Yup.1) Stop bad emails getting into the system.
Nope2) Does it have any scheduling or an ability to clean out old bad emails?