Details on the use of Catchall emails

I just put this on my projects, so I do not necessarily talk about experience. But I think I understand the concept behind the use of e-mails "catch-all" when using GSA SER. And since this is a somewhat "technical" problem, I thought that some people might probably need help to solve it. My hosting company uses cPanel, the examples of images I have shown come from that. If your hosting provider uses something else, it may be slightly different.

Before starting with the instructions, it is probably useful to explain what is a "catch-all" e-mail account. This is a special email account that you have configured on your own domain (You can not use Hotmail, Gmail, etc.). When you set up this account, the emails that are sent to it and their email address on your domain which is not defined, will automatically be sent to this email account instead. (A big advantage of using it in GSA SER is that you do not have to create a set of email accounts, just enter the email address of your choice and, as it does not was not found, it is sent to the Account Captive Mail.

OK … so here's what you need to do.

# 1) Create an email account (on any domain you own) that will be used as a "catch-all" email account. In fact, no matter if you have already created other email accounts that you use, only emails from undefined accounts will be transferred to this account.
picture

# 2) Assign it as an e-mail "catchall" for this domain (on cPanel accounts, it is called the "default" e-mail).
picture
picture

You're done creating your "tote bag" email account!

Now, on your GSA SER projects, you can enter this email / password into the "Check" area of ​​each project for which you wish to use it. For the e-mail address in the "Data" area of ​​the project, you can specify the e-mail address of your choice (for this area) (make sure that it does not appear). NOT acts as a valid e-mail address). If this email address (in the "Data" area) becomes a blacklist, change it a bit and you're ready to start again.

*NOTE: I think you should be able to rotate the email address in the "Data" area. Can someone check this for me? (Change … no matter … I found the answer … see the second post in this thread.) If this is the case, you can create a single email for each project and not never have to worry about anything ever blacklisted. . (Pleasant!)

This approach probably raises questions for some people. I will try to answer some of the questions I have encountered here.

1.) Is there a problem / conflict between the projects since, in reality, they share the same email account? Sven said the program keeps track of the URLs associated with which projects and ignores e-mails that do not apply to this project.

2.) Should I delete messages after their treatment? Yes, on the "Email Verification" screen, click "Delete message when the verification link has been found".
* Note: DO NOT select the third option, "Delete all messages …". This will cause problems with this installation.
* Note: It is also probably wise to select the first option "Wait at least 15 minutes between connections".

3.) What should I do about spam (or others) that accumulate in this account over time?

It is important that all spam and junk e-mails are removed from this account from time to time as they will slow down the GSA SER. From now on, I've been able to suggest three options.

1.) Create an "unwanted" project (in SER) normally set to "Inactive" and on which the third option is selected ("Delete all messages"). Activate this project from time to time to remove old messages that have accumulated. However, this is potentially dangerous. You need to make sure that all your other projects are stopped and that all emails have been verified before starting this. You should also make sure that you have kept this project inactive unless you want to run it specifically or if the emails you need would be deleted.

2.) Manually enter and delete all emails older than XX days (at your convenience). It's painful to do.

3.) Create a "Cron" job that runs on your server and deletes all emails longer than xx days. It's a bit technical, but I've outlined the steps below. I've tested this and it works, but if you decide to use it, make sure you set it up correctly or you could delete emails (or other files) from your server that you do not have. Had not the intention to do. It works because every email is actually stored on your server in a separate file. This process simply removes files older than a certain number of days.

Here's how to configure it …

1.) Create a Cron job.
picture
picture
In the field "Command", enter this line (modified for your configuration) …

find -P /home/account/mail/yourdomain.com/emailacctid/cur -type f -mtime +30 -exec rm {} ;

Edit the following in the line above …

/ home / account / —-> What appears in the "Stats" section of your cPanel screen (see photo)
picture

yourdomain.com —-> your domain name (without www.)

emailacctid —-> the email account you created (name only – without @ yourdomain.com)

+30 —-> age of emails to delete (in this case> 30 days)

And do not leave the semicolon at the end. All spaces and everything are important too, so make sure it's entered correctly.