Email Forwarders and :blackhole:
Hi,
First I create a forwarder called "testbh@example.com" and send it to :blackhole:. It saves properly and "testbh" is now a valid forwarder in the database (albeit to nowhere).
When I try to create a mail forwarder called "test2@example.com" that sends to "testbh@example.com" I get the error message:
But "testbh@example.com" is a valid forwarder in the forwarder database, it just happens to send to blackhole. Since the system allows a single forwarder to send to blackhole, I'm curious as to why this (albeit inefficient) configuration would not be allowed as the end result of delivery is the same... blackhole delivery. Thanks for any clarification you can provide!
The system could not add the forwarder: (Warning: testbh@example.com" does not refer to a valid local email account or alias. The system will not create a forwarder, because it already sends that email to the default address.)But "testbh@example.com" is a valid forwarder in the forwarder database, it just happens to send to blackhole. Since the system allows a single forwarder to send to blackhole, I'm curious as to why this (albeit inefficient) configuration would not be allowed as the end result of delivery is the same... blackhole delivery. Thanks for any clarification you can provide!
-
You're attempting to forward mail from an existing account to an account that exists as an alias only and sends to a blackhole. If it was a valid email account the forwarder would function. Is the end goal just to have all mail to test2@example.com blackholed? If so the best option for that would be to select Discard in the forwarder menu under the advanced options. 0 -
Thanks. I'm working with a custom front-end script using the API to create the forwarders. It processes a UI forwarder list from the top down calling the API to create each forwarder as it goes. If the first forwarder is configured in my custom UI to send to blackhole and the second one is set to forward to the first one, it fails with this error. In this particular use case, a user wanted to set up all their forwarders with the intent of adding valid recipient email addresses for one or two of them at a later time. The one that didn't have a valid recipients yest was also also the target of other forwarders, so the forwarder at least needed to exist as a placeholders so the ones down the list could be created if they referenced it. 0 -
@swbrains that sounds pretty complicated! As far as I know, if the target of a forwarder is not a valid email this isn't going to work, so it'd have to be a limitation added to your customization. I'm not sure I fully understand the purpose of this with that description, so I don't think I can give you further advice on a workaround at this time, unfortunately. 0 -
No problem -- Thanks anyway! 0
Please sign in to leave a comment.
Comments
4 comments