External email forwarding why not alias?

jonathanmmm

Hi,

In the admin menu under Alias is the hint that you should use Sieve or the inbuilt forwarding of SoGo for external emails. My question is, why?
What would be a possible downside? Would there be problems, like if the email can’t be forwarded the first time to all?

I would use to manage lists, like if you send an email to a-team@my-domain.com it should go to all their personal private email accounts (and a-team@my-domain.com will nobody use to login).

BusterB

I gave up trying to get that working on my setup – I never had any luck. Everything looked good in the gui but the forwards never went out externally. Going into SoGo and forwarding from within worked perfectly and is a 30 second “fix” instead of fiddling around with rules and such. Sure, you need to have SoGo installed but meh - at least it’s working.

I seem to recall that it had to do with either sieve or postfix not using the “sender-dependent transport” for sending the forwards properly. I remember seeing in the logs it defaulted those external outbound email forwards to port 25, which is blocked by my ISP and my sender transport is configured to send over port 2525.

jonathanmmm

BusterB Ok, so the problem could be the port? But if I use a server hosted somewhere I shouldn’t have ISP blockings.
Could something like the FROM email address be wrong?

Yes SoGo can be used or sieve, but both don’t give the overview as the ALIAS, if a few admin would manage multiple lists of external email addresses and use emails of mailcow like as a forwarding address, so everyone in a specific team gets a copy into their private email inbox.