Yes, I could, but I was really hoping to avoid managing psudo users as employees come and go from support here as well as AD.
A single common account and password seems to be the best way to handle this One password to change when an employee leaves. That account would only be used for sending. I would need to block pop access and prevent the mailbox from storing mail. On Mar 9, 2014, at 7:34 PM, Eric Shubert <e...@shubes.net> wrote: > Can't you (simply) set up each support person with their own authentication > account, and configure their client with supp...@mydomain.com as the sender > email address? > > -- > -Eric 'shubes' > > On 03/09/2014 07:11 AM, Scot wrote: >> I would prefer not to have a local account and password shared by everyone >> in support. >> >> Sending mail from an authenticated user was the only way it would relay the >> mail. >> >> I don't want to inadvertently create an open relay either. My support users >> can come from a variety of ip's but even adding an ip whitelist for the >> local office subnet, mail was denied. >> >> Sent from my iPad >> >>> On Mar 8, 2014, at 1:21 PM, Eric Shubert <e...@shubes.net> wrote: >>> >>>> On 03/07/2014 11:57 PM, sco...@gmail.com wrote: >>>> For my purpose I just want them to be able to reply to these forwards >>>> assupp...@mydomain.com. And send new mail assupp...@mydomain.com so when >>>> customers reply, mail goes back tosupp...@mydomain.com >>> >>> That's trivial, right? >>> >>> -- >>> -Eric 'shubes' >>> >>> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com > For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com > --------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
