bbs.spamgourmet.com

Sometimes it's known at the moment an address is created that it will need to be configured.

Because the 2nd field is often used from something meaningful other than a number, there are cases where the new address gets hit with more legitimate mail than the 2nd field allows for, and excess messages are deleted. Eg. I created a new account somewhere, and immediately made several changes to that account. Each change was confirmed with an email. So a burst of messages came through and 3 of them were deleted.

I knew it would happen, so I logged into SG, and did a search on the new address, and refreshed the search periodically in hopes that I could get into the configuration page before the messages would hit. I could not time it so that it refreshed after the first message.

The workaround is to send myself a message to that address before disclosing it.. but that doesn't always occur to me, and isn't always convenient - and when I do think of it, sometimes the delay is too great for it to work.

The workaround is to send myself a message to that address before disclosing it.. but that doesn't always occur to me, and isn't always convenient - and when I do think of it, sometimes the delay is too great for it to work.

Better: create an address "before disclosing it" in "advanced mode." Use"send a message from one of your disposable addresses," and use the "or create a new one [address]" option, obviously. As per sg FAQ, the address is created immediately, & is available in your address list for editing.

Nice! Thanks!

If this sort of thing happens to you a lot, you could increase your "default number" from 3 up to any number that's 20 or less in advanced mode (although a lower number is good for other reasons I suppose).

josh wrote:If this sort of thing happens to you a lot, you could increase your "default number" from 3 up to any number that's 20 or less in advanced mode (although a lower number is good for other reasons I suppose).

I have gotten in the habit of using that 2nd field for something meaningful. Eg. the second field is "forum" for web-based forum accounts, which overrides the default allowance with 6. Or if I create a stock account, the 2nd field might be "brokerage", for example. Then I code procmail to parse that and use it for filtering. Perhaps that's a habit I should avoid, but the suggestion from sg-since03 is probably ideal.

Hm, if you're postprocessing your mails with procmail, couldn't you beef up your filter to drop a prefix in the 2nd field?

Suppose you'd have:

sg.z_forum.username@spamgourmet

Now you now that the 2nd field is "z_forum". Sg would allow 26 (or rather 20) mails to that adress. In your procmail recipe, you could drop the "z_" prefix.

Wouldn't that work for you?

Cheers,
Alexander

askwar wrote:Hm, if you're postprocessing your mails with procmail, couldn't you beef up your filter to drop a prefix in the 2nd field?

Yeah, procmail is quite powerful. There's almost no limit to the amount of parsing it can do. But once I adopt a convention, I hate to go back and change the scripts. It can be a very error prone process.. and I'm talking about human error. The slightest error in a procmail script can cause email to get trashed until it's discovered. I'm also not necessarily sitting at the procmail host the moment I would decide to start using a slightly different convention. In the case above, the burst of email would have been sent before I'd have a chance to alter the filters.

askwar wrote:Suppose you'd have:

sg.z_forum.username@spamgourmet

Now you now that the 2nd field is "z_forum". Sg would allow 26 (or rather 20) mails to that adress. In your procmail recipe, you could drop the "z_" prefix.

Wouldn't that work for you?

Yeah, that would work. Although I think the limit is 20 regardless. I think a z still gets capped at 20.