RT with authenticated mail server

Hi

I have a setup where RT is installed in specific server with it’s own
email system.
And we have setup mails in such a way that my corporate group email id
has one additional email as RT’s email id, so the ticket is getting
generated.
In RT’s email queue, the configured email address is from corporate’s
email. this is to hide mail system of RT.

Now, when RT sends any reply/notification, it show from address as
corporate’s email.
Till now, we have anonymous access in our corporate email server, and
things were working find.

But, due to spam attack, our IT team has disallowed anonymous access in
our corporate email server, and made authentication compulsory.
Due to this RT’s emails are getting bounced and are not getting
delivered to our corporate users.

Please let me know how to overcome this issue.

FYI, setup details is as follows:
RT: installed in Linux with postfix having email address as
/@rt.corporate.co.in/
Corporate Mail: /@corporate.com/ on Microsoft Exchange
// Group Mail id corporate users to generate ticket:
/it-admin@corporate.com/ which forwards mail to
/it-admin@rt.corporate.co.in/
RT Queue: it-admin@rt.corporate.co.in is aliased to RT queue using
RT URL, and tickets getting generated in /it-admin/
Queue: it-admin, reply to address as /it-admin@corporate.com/
Autoreply/Notifications configured as usual
Whole setup was working fine. But, after enabling authentication in
Exchange, it stopped working.

Regards,
Jignesh

jignesh.vcf (153 Bytes)

Hi

I have a setup where RT is installed in specific server with it’s own email
system.
And we have setup mails in such a way that my corporate group email id has
one additional email as RT’s email id, so the ticket is getting generated.
In RT’s email queue, the configured email address is from corporate’s email.
this is to hide mail system of RT.

Now, when RT sends any reply/notification, it show from address as
corporate’s email.
Till now, we have anonymous access in our corporate email server, and things
were working find.

But, due to spam attack, our IT team has disallowed anonymous access in our
corporate email server, and made authentication compulsory.
Due to this RT’s emails are getting bounced and are not getting delivered to
our corporate users.

Please let me know how to overcome this issue.

Identify the SMTP server you’re using on your RT box and configure it
to use SMTP AUTH.

             Please keep list traffic on the list.

Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn’t become a monster. Friedrich Nietzsche

Hi

I have a setup where RT is installed in specific server with it’s own email
system.
And we have setup mails in such a way that my corporate group email id has
one additional email as RT’s email id, so the ticket is getting generated.
In RT’s email queue, the configured email address is from corporate’s
email. this is to hide mail system of RT.

Now, when RT sends any reply/notification, it show from address as
corporate’s email.
Till now, we have anonymous access in our corporate email server, and
things were working find.

But, due to spam attack, our IT team has disallowed anonymous access in our
corporate email server, and made authentication compulsory.
Due to this RT’s emails are getting bounced and are not getting delivered
to our corporate users.

Please let me know how to overcome this issue.

FYI, setup details is as follows:
RT: installed in Linux with postfix having email address as
/@rt.corporate.co.in/
Corporate Mail: /@corporate.com/ on Microsoft Exchange
// Group Mail id corporate users to generate ticket:
/it-admin@corporate.com/ which forwards mail to
/it-admin@rt.corporate.co.in/
RT Queue: it-admin@rt.corporate.co.in is aliased to RT queue using RT
URL, and tickets getting generated in /it-admin/
Queue: it-admin, reply to address as /it-admin@corporate.com/
Autoreply/Notifications configured as usual
Whole setup was working fine. But, after enabling authentication in
Exchange, it stopped working.

Regards,
Jignesh

Look in the postfix documentation at the SASL_README to see
how to enable the client side SMTP AUTH support and use that
to send authenticated mail.

Regards,
Ken