Re: [rt-users] Need RT to send mail to a group
In case anyone is interested - I figured out the problem. Everything I did was correct, however, the only member of the group to which I wanted the mail sent was also the user moving the ticket. The transacting user, apparently, is exempt from the rt-email-group-admin action. I added an additional user to the group and that user receives mails exactly as expected. Brandon From: rt-users-boun...@lists.bestpractical.com [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of Brandon Olszewski Sent: Wednesday, March 09, 2011 4:12 PM To: rt-users@lists.bestpractical.com Subject: [rt-users] Need RT to send mail to a group Greetings, I am trying to get my RT 3.8.9 instance running on SLES11 to send emails to all members of an RT group whenever a ticket is moved from any queue into the LAN queue. I've created a group called LAN, and placed the desired recipient's RT user account as a member. I've used the following command to create a custom action to send email to this group: /opt/rt3/sbin/rt-email-gorup-admin -add 'Notify LAN group' -group 'LAN' And I have verified the successful creation of this action with this command: /opt/rt3/sbin/rt-email-group-admin -list 'Notify LAN group' Result of the above command: Name: Notify LAN group Module: NotifyGroup Members: Group = LAN I've created a scrip (number 14 for this RT instance) in the LAN queue with the following paramaters: Description: NotifyLAN Condition: On Queue Change Action: Notify LAN group (the custom action created in the above step) Template: Global template: Admin Correspondence (unchanged default template) Stage: TransactionCreate When I move a ticket to the LAN queue, no email is sent, and these two lines appear in the RT log file: [info]: #27/427 - Scrip 14 NotifyLAN (/opt/rt3/bin/../lib/RT/Interface/Email.pm:302) [info]: No recipients found. Not Sending. (/opt/rt3/bin/../lib/RT/Interface/Email.pm:352) I'm not set on using this method of sending email to a group if someone has an easier/working way to do it. Any help would be greatly appreciated. Brandon The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and privileged material. Unauthorized review, use, disclosure, or distribution is prohibited. If you receive this material/information in error, please contact the sender and destroy the material/information. Email is not a secure form of communication and should not be used to transmit personal or confidential information such as account numbers, balance information, or wire transfer requests. The PrivateBank is not responsible for the security of sensitive information received by email. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and privileged material. Unauthorized review, use, disclosure, or distribution is prohibited. If you receive this material/information in error, please contact the sender and destroy the material/information. Email is not a secure form of communication and should not be used to transmit personal or confidential information such as account numbers, balance information, or wire transfer requests. The PrivateBank is not responsible for the security of sensitive information received by email.
[rt-users] Need RT to send mail to a group
Greetings, I am trying to get my RT 3.8.9 instance running on SLES11 to send emails to all members of an RT group whenever a ticket is moved from any queue into the LAN queue. I've created a group called LAN, and placed the desired recipient's RT user account as a member. I've used the following command to create a custom action to send email to this group: /opt/rt3/sbin/rt-email-gorup-admin -add 'Notify LAN group' -group 'LAN' And I have verified the successful creation of this action with this command: /opt/rt3/sbin/rt-email-group-admin -list 'Notify LAN group' Result of the above command: Name: Notify LAN group Module: NotifyGroup Members: Group = LAN I've created a scrip (number 14 for this RT instance) in the LAN queue with the following paramaters: Description: NotifyLAN Condition: On Queue Change Action: Notify LAN group (the custom action created in the above step) Template: Global template: Admin Correspondence (unchanged default template) Stage: TransactionCreate When I move a ticket to the LAN queue, no email is sent, and these two lines appear in the RT log file: [info]: #27/427 - Scrip 14 NotifyLAN (/opt/rt3/bin/../lib/RT/Interface/Email.pm:302) [info]: No recipients found. Not Sending. (/opt/rt3/bin/../lib/RT/Interface/Email.pm:352) I'm not set on using this method of sending email to a group if someone has an easier/working way to do it. Any help would be greatly appreciated. Brandon The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and privileged material. Unauthorized review, use, disclosure, or distribution is prohibited. If you receive this material/information in error, please contact the sender and destroy the material/information. Email is not a secure form of communication and should not be used to transmit personal or confidential information such as account numbers, balance information, or wire transfer requests. The PrivateBank is not responsible for the security of sensitive information received by email.
[rt-users] rt-mailgate rejects incoming email
I have a new install of RT 3.8.9 running on SLES11, and I cannot get incoming emails to update/create tickets. I'm using postfix for email routing. Outgoing mail works (all mail routed to an Exchange smarthost). I put a debug switch in my aliases file and the error generated by an incoming email is: [error] Couldn't find sender's address (/opt/rt3/bin/../lib/RT/Interface/Email/Auth/MailFrom/pm:67) [error] Could not record email: Could not load a valid user (/opt/rt3/share/html/REST/1.0/noAuth/mail-gateway:75) From what I understand, this error means that postfix received the email properly and passed it to rt-mailgate, which failed to parse a valid FROM email address from the headers thus rejecting the message. The only instance I've found of this error happing was resolved by adding CreateTicket permissions to the Everyone group in RT - I've done this to no avail. Linux version: 2.6.32.27-0.2-default Perl version: 5.10.0 built for x86_64-linux-thread-multi Non-standard configurations: Default http site redirects to https Additional module RT::Authen::ExternalAuth 0.08_01 - authenticates via LDAP against Active Directory - is working properly. Any advice would be much appreciated! The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and privileged material. Unauthorized review, use, disclosure, or distribution is prohibited. If you receive this material/information in error, please contact the sender and destroy the material/information. Email is not a secure form of communication and should not be used to transmit personal or confidential information such as account numbers, balance information, or wire transfer requests. The PrivateBank is not responsible for the security of sensitive information received by email.
Re: [rt-users] rt-mailgate rejects incoming email
Yes - the user has authenticated a number of times, and opened a ticket via the web interface. I did verify that the proper email address was imported from AD to the RT database. From: Giuseppe Sollazzo [mailto:gsoll...@sgul.ac.uk] Sent: Friday, March 04, 2011 11:57 AM To: Brandon Olszewski Cc: rt-users@lists.bestpractical.com Subject: Re: [rt-users] rt-mailgate rejects incoming email Just a question... had the user authenticated at least once? If they aren't in the db or imported from ldap, there's no mention of them in the RT users db hence incoming e-mails can't create tickets. Giuseppe On 04/03/11 17:46, Brandon Olszewski wrote: I have a new install of RT 3.8.9 running on SLES11, and I cannot get incoming emails to update/create tickets. I'm using postfix for email routing. Outgoing mail works (all mail routed to an Exchange smarthost). I put a debug switch in my aliases file and the error generated by an incoming email is: [error] Couldn't find sender's address (/opt/rt3/bin/../lib/RT/Interface/Email/Auth/MailFrom/pm:67) [error] Could not record email: Could not load a valid user (/opt/rt3/share/html/REST/1.0/noAuth/mail-gateway:75) From what I understand, this error means that postfix received the email properly and passed it to rt-mailgate, which failed to parse a valid FROM email address from the headers thus rejecting the message. The only instance I've found of this error happing was resolved by adding CreateTicket permissions to the Everyone group in RT - I've done this to no avail. Linux version: 2.6.32.27-0.2-default Perl version: 5.10.0 built for x86_64-linux-thread-multi Non-standard configurations: Default http site redirects to https Additional module RT::Authen::ExternalAuth 0.08_01 - authenticates via LDAP against Active Directory - is working properly. Any advice would be much appreciated! The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and privileged material. Unauthorized review, use, disclosure, or distribution is prohibited. If you receive this material/information in error, please contact the sender and destroy the material/information. Email is not a secure form of communication and should not be used to transmit personal or confidential information such as account numbers, balance information, or wire transfer requests. The PrivateBank is not responsible for the security of sensitive information received by email. -- Giuseppe Sollazzo Senior Systems Analyst Computing Services Information Services St. George's, University Of London Cranmer Terrace London SW17 0RE Email: gsoll...@sgul.ac.ukmailto:gsoll...@sgul.ac.uk Direct Dial: +44 20 8725 5160 Fax: +44 20 8725 3583 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and privileged material. Unauthorized review, use, disclosure, or distribution is prohibited. If you receive this material/information in error, please contact the sender and destroy the material/information. Email is not a secure form of communication and should not be used to transmit personal or confidential information such as account numbers, balance information, or wire transfer requests. The PrivateBank is not responsible for the security of sensitive information received by email.
