Skip to content

How Does GSA Deal With Catchall Emails

If you have multiple projects in GSA using a catch all email, does GSA only try to do one set of verification and then apply it to those projects using the catch all or is each project getting the email when it checks it and only checks for that individual project instead of all?


  • SvenSven
    each project does the check. But if you do not use the option to delete all emails, it will work fine.
  • HinkysHinkys - Catchalls for SER - 30 Day Free Trial
    This is why it's important, if you have more than 1 catchall, to use only 1 / project.

    If you just jam multiple catchalls in each projects, you will unnecessarily slow down SER. Here's an example.

    Let's say you have 100 projects and 10 catchalls with an average of 1,000 emails in each of the catchall's inbox.

    Example #1 - 100 projects, 1 catchall / project

    When SER goes to verify emails, it needs to check it once for each project. In order to check all of them, SER had to download a total of 100,000 emails (1,000 emails / project).

    Example #2 - 100 projects, all 10 catchalls in each project

    Now SER needs to check all 10 catchalls / project. And it needs to download all emails in each catchall in order to do that. So in order to verify emails in this example, SER would download need to download 1 million (10 times more than in example #1) emails.

    Now you might be thinking it's easier to import all 10 catchalls than 1 random one / project but it's actually quite simple.

    Just select all your project and do Modify Project -> Import -> Email Accounts


    Delete all present email accounts if needed...


    And import 1 random once in each project!


    I know this isn't what the OP asked but it's still one of the most overlooked ways of optimizing your SER if you're using catchalls.
  • TryAMillionTryAMillion United Kingdom
    edited December 2016
    @Sven thanks for clarifying. A good feature request might be to have an option to make GSA check and update all active projects or selected projects + checkbox in project email section to select if it is a catch all. This would reduce the issue @Hinkys said.

    Adding to that, the feature could hold the data for the other projects in cache, so if running it updates and if not active then can hold in cache till those projects are started again to update and do verification.

    A workaround for @Hinkys is to schedule multiple projects with 1 running at any one time for 16+ minutes and setting checking pop no faster than 15 mins for example. Has worked but yes, still have the going through of all the emails, but found this helps with multiple projects end up keep trying to download emails.

Sign In or Register to comment.