Public or not, they still do some analysis on the *content* of the incoming
message, and that's the likely thing that's biting you. Something in the
content of the message is triggering a filter at the receiving site. There's
nothing OTRS can do about that.
From: otrs-boun...@otrs.org [mailto:
I'm not totally sure if it is an OTRS problem or not, since the customer
received the email when he asked for his password.
Like I said, at this point, it's not your server. Something outside the OTRS
environment is intercepting the mail, based on some criteria you can't see. If
he got the pass
I don't know Steve, because It works when the customer asks for his
password. If the customer receives the password and his email is from a
google group, why he can not receive an auto response? The group is set to
be public.
Best regards,
---
Carlos Eduardo Ribas
20
It's not an OTRS issue as you've indicated the email was sent on to
Google OK, it is a problem with Google Groups (more than likely their
spam filters, or the email address that the email is being sent as
does not have the right to deliver mail to the group).
Steve
On 10 September 2012 13:48, Ca
Hello all,
I was looking for any other log in my server, but all I can see is what I
said in the last email. My OTRS system says the message was sent. The
account used by OTRS (a google email) also says the email was sent. Here I
think there is nothing more to see. I dont know if I can see any MTA
I made a mistake about this. Apparently, yes, there is a group_id in the
ticket table, so there is some group that is assigned to the ticket. I
still think the idea is not a good one to have a customer be able to see
all the tickets attached to a specific group id, as the group doesn't
necessarily
