On 6/8/2015 1:02 AM, Chris Ferebee wrote:
> Thanks for clarifying the syntax, I was unsure about that.
>
> Unfortunately, that’s not a practical solution in this case. In a strict sense, I’d need to list all the domains hosted on my server, which is a long (and growing) list. In particular, they need to be able to send email to me at my own domain, and there are others.
>
> I think I don’t understand the meaning of g_route_local and why it doesn’t apply here. Could you explain how to use it/what it’s for? Or is there a way to specify
>
> !*@
>
> in the "to" field of g_route_from?

Actually, now I look more closely, I think that is actually a bug, let
me know your platform and I'll send you a new build to fix that.

ChrisP.

>
> Thanks,
> Chris
>
>
>> Am 07.06.2015 um 07:10 schrieb Surgemail Support surgemail-support@netwinsite.com:
>>
>> Would this help?
>> g_route from=
>> "*@example.com" to="*,!*@example.com
>> " dest="smtp.example.com" user="xyz" pass="xyz"
>>
>> I fear not...
>> ChrisP.
>>
>>
>>
>>
>> On 6/5/2015 2:08 AM, surgemail-list@netwinsite.com wrote:
>>> Thanks, this works, but with one twist.
>>>
>>> I set g_route as follows
>>>
>>> g_route from=
>>> "*@example.com"
>>> to="*" dest="smtp.example.com" user="xyz" pass="xyz"
>>>
>>> When one of my users with a From address of
>>> abc@example.com
>>> sends email through my server to another address hosted on my server, it creates a routing loop, even though
>>>
>>> g_route_local
>>>
>>> is not set. Does g_route_local default to TRUE? (The web GUI suggests otherwise.) Or does it not do what I think it should?
>>>
>>> I’ve worked around the issue by setting
>>>
>>> g_route_except "1.2.3.4"
>>>
>>> with 1.2.3.4 being the IP of the outbound SMTP server for example.com, but it would be preferable (e. g., much quicker) to deliver the email directly.
>>>
>>> Best,
>>> Chris
>>>
>>>
>>>
>>>> Am 01.06.2015 um 01:52 schrieb Surgemail Support surgemail-support@netwinsite.com
>>>> :
>>>>
>>>> On 6/1/2015 11:49 AM, Chris Ferebee wrote:
>>>>
>>>>> Thanks, I'll try it.
>>>>>
>>>>> I had considered that possibility, but was put off by the description:
>>>>>
>>>>> "Allows a message that has already been accepted for local delivery to be delivered to another server."
>>>>>
>>>>> What is the meaning of "that has already been accepted for local delivery" in this context? The messages I'm trying to re-route are for the most part intended for remote delivery.
>>>>>
>>>> That just means the routing can be modified and it will change the destination of messages already in the queue but not yet sent (sometimes useful when a destination server is moved
>>>> and you have a bunch of queued messages). But for your purpose that isn't relevant.
>>>>
>>>> ChrisP.,
>>>>
>>>>
>>>>> Best,
>>>>> Chris
>>>>>
>>>>>
>>>>>
>>>>>> Am 01.06.2015 um 01:38 schrieb Surgemail Support surgemail-support@netwinsite.com
>>>>>> :
>>>>>>
>>>>>>
>>>>>> Here's the setting you need:
>>>>>> g_route from=string to=string dest=string user=string pass=string
>>>>>>
>>>>>> ChrisP.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 6/1/2015 8:43 AM,
>>>>>> surgemail-list@netwinsite.com
>>>>>> wrote:
>>>>>>
>>>>>>> Is there a way to specify a smarthost, as with g_gateway, but restricted to outbound email *from* certain users?
>>>>>>>
>>>>>>> To explain...
>>>>>>>
>>>>>>> I host email for a local branch office of a client whose corporate email server is on a different continent. They need to use their main corporate email domain.
>>>>>>>
>>>>>>> I can g_popfetch their email from the remote server and serve it locally, but I need to gateway their outbound email through the corporate server.
>>>>>>>
>>>>>>> They would like to submit their outbound email to my server because connectivity is much better from their mobile devices than to the remote server. My server can then gateway the email, retrying as needed.
>>>>>>>
>>>>>>> Previously, I would simply send out their email from my server. However, that no longer works because the central office recently added an SPF record to their email domain, so email sent out from my server is now being bounced by servers with strict inbound SPF policies.
>>>>>>>
>>>>>>> Therefore, I would like to specify a smarthost for outbound email, similar to g_gateway, but I would like to use this smarthost only for outbound messages that are from specific authenticated users, or authenticated users of a specific domain, or, failing that, with a From: address in a specific domain.
>>>>>>>
>>>>>>> Is this possible?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Chris
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>


/surgemail-support@netwinsite.co/surgemail-support@netwinsite.co/surgemail-support@netwinsite.co