1 / 8
Jul 2014

Hi

I want to stop people using anonymous email addresses when either buying products or downloading free products.

I know eJunkie admin has an email ban list, but it does not stop mailinator as I ahve tested it with a mailinator address.

How would I implement this to stop free downloads from [anything]@mailinator.com please?

  • created

    Jul '14
  • last reply

    Sep '14
  • 7

    replies

  • 1.6k

    views

  • 4

    users

  • 2

    links

You would simply go to Seller Admin > Block Buyers/Transactions and enter mailinator.com on a line by itself, as the block list matches whole or partial strings and even supports wildcards (e.g., *@mailinator.com would work just as well). Note this will not block their ability to place an order; it will just tell our system not to process such an order when it's placed, so we would not issue any download links, not send thank-you emails, etc.

I asked about this three years ago. I am glad a request/suggestion implemented.



1http://www.e-junkie.com/bb/topic/53521



On a side note, some of us have been doing this for a long time and the 250 limit on the block list just isn't cutting it anymore. Any way to increase the max entries?

I've asked Development to increase the block list limit. BTW, if you have any old, specific Transaction IDs blocked, you can safely remove those to free up lines in your block list, as they're really only relevant at the moment we receive payment confirmation from the payment processor; after that point, there's nothing left for us to block/ignore regarding those Transaction IDs, so removing them should have no effect.



I also just realized we never built a help page for blocking buyers/transactions, so I've just posted that now:

http://www.e-junkie.com/ej/help.block.htm

Development has now raised the block list limit to 500 entries.



Also, turns out I was misinformed about partial matching without wildcards, which won't work -- i.e., partial matching is only supported with wildcards (e.g., *@mailinator.com).

1 month later

Our development team has resolved the issue and it should be at 500 for you now.