I'm wondering what expected invitee acceptance behavior is of a self hosted CalDAV server.
We have a Baikal server set up but are having issues with recipients (that are not on the bakail server) accepting calendar invites. The real issue being that that calendar events are not being updated with the acceptance status. Reviewing the ics files/nodes within dav.php shows that the PARTSTAT data always show =NEEDS-ACTION.
Again, this is only for users/email addresses that are not on the Baikal server.
Scenario:
user1#domain1.com sets up calendar event in Mac Calendar
Invites user2#domain1.com and user1#gmail.com
Invites sent out as IMip - we have also extended this plugin to use PHPMailer so that emails that are sent have better delivery
Emails received and user2#domain1.com accepts, event is displayed in their calendar and shows they have accepted and that user1#domain1.com is the organizer and accepted, shows user1#gmail.com as not accepted
user1#gmail.com also accepts, event is displayed in their Google calendar and shows they have accepted, shows user1#domain1.com is organizer and accepted, user2#domain1.com shows not accepted
user1#domain1.com gets IMip email that user2#domain1.com has accepted.
Gets a Gmail email that user1#gmail.com has accepted.
user1#domain1.com goes to Mac Calendar and status shows as not accepted from user1#gmail.com
Seems kind of similar to sabre-io/dav#556 but its clear the PARTSTAT is not being updated on our end.
So the real question is... is this normal behavior? ie. iCal acceptance not working across multiple domains?
Related
I have a website that allows visitors to fill in a form with their name, email address, and a question, and this is sent as an email message to the nominated website member.
The email messages are plain text and contain a 'Reply-To' header with the name and email address provided by the visitor. They are sent from noreply#mydomain which is managed by Google Workspaces.
Here is an edited snippet of the relevant headers:
Date: Wed, 10 Nov 2021 11:25:55 +0000
Subject: Question
From: My Business <noreply#mydomain>
Reply-To: Visitor <visitor#theirdomain>
To: Member <member#theirdomain>
When this is working correctly, the recipient receives the message from noreply#mydomain, and when they click the reply button in their email client, the reply will be addressed to the visitor. Most email clients are compliant and this arrangement has worked reasonably well for many years.
However, over the last few days a number of website members with gmail addresses are replying to the noreply#mydomain address. I have sent myself a test message through the website, and when I click the 'Reply' button on the received message, the reply is addressed to noreply#mydomain. This occurs on Gmail for web, Android and ios.
I have also noticed that gmail is no longer displaying the account name for the noreply#mydomain account. It's there in the headers, but only the address is displayed in list view and message detail view.
I have opened up older messages from 2017 (these are the most recent ones I have) and they still display and create a reply correctly. I have compared headers, and both pass SPF and DKIM. The major difference is the new message contains ARC- headers that weren't implemented in the past.
Does anyone have any ideas how I can fix this problem?
We have an on-premise hosted Jira 6.0.8. We have set up an outgoing mail server using a Gmail account and used the send test e-mail feature to successfully send an e-mail out.
Our problem is with e-mail notifications. We are not getting any at all. We have gone through troubleshooting docs https://confluence.atlassian.com/jirakb/troubleshoot-notifications-in-jira-203394737.html here but have not been able to find the solution.
Here is what we have already tried;
Ensured user profile 'My Changes setting' was set to 'Notify Me'
Ensured Notification scheme was correct and associated with the project
Ensured Project Notification email was set to the same as the outgoing mail server Gmail address
Checked the 'Mail Queue' after making a comment on an issue and saw waiting messages in it for the correct issue. These then disappeared from the queue without error within 60 seconds, indicating that they had been sent.
Enabled DEBUG logging under 'Logging and Profiling' for the outgoing mail server and com.atlassian.jira.service and com.atlassian.jira.service.services.DebugService. We reviewed the log file and saw nothing that indicated error but did see the log of the MailqueueService sending the e-mail.
have used the 'Notifcation Helper' tool and it verified that the user would receive the appropriate notification indicating notifcation scheme and permission are set up ok.
Still the notification e-mail is not received.
There was a point made in the troubleshooting link above
Check that your Base URL is set to a domain / IP which your SMTP server will accept. Example: Google apps accounts must have a matching base url to their Google Apps domain.
However, our Adminsistration> System>General Configuration>Base Url for Jira is something like http://myservername:8880 since it is internal self-hosted. This did not cause a problem with the test mail. Could this be an issue for the notification e-mails?
Any help would be greatly appreciated.
I'm using App Engine to send text messages to users (by sending e-mails to their SMS/MMS gateways). The e-mails act essentially as push notifications for iPhone users (since Apple doesn't support Web Push at this time).
The plan is to allow users to also reply to those messages and tweak their subscription (for example, replying with "unsubscribe" would remove their subscription and stop sending them text messages without having to log in to the site and make changes in the "account" screen).
I am sending e-mails using a From: address of notification#XXXX.appspotmail.com, where XXXX is my App Engine project ID.
If I send an e-mail to an AT&T subscriber at NNNNNNNNNN#mms.att.net (or my personal e-mail addresss ZZZZZZ#gmail.com), the sender appears exactly as I originally sent it, and those users may reply to the message (and it is received by App Engine, since it is of the proper format for App Engine to proces it).
However, when App Engine sends an identical e-mail to NNNNNNNNNN#msg.fi.google.com, the sender (the address in the From: line) is always rewritten to be XXXX#appid.googleusercontent.com (where "XXXX" is the App Engine project ID). I don't have any access to the mail for that e-mail address, and it is not posted to App Engine.
When sending mail from App Engine, it adds the following MIME headers:
X-Google-Appengine-App-Id: s~XXXX
X-Google-Appengine-App-Id-Alias: XXXX
My guess is that there's something on the Project Fi MMS gateway that's doing some translation that it shouldn't be doing, using those headers.
I couldn't find any useful references to appid.googleusercontent.com online, so I thought that I'd post here.
I checked in with Project Fi's support, and this was not in their playbooks or documentation at all.
So, two questions:
Why are e-mails sent from App Engine to Project Fi having their From: address rewritten?
Is there anything that can be done to fix it?
Up until approximately 1 month ago, we were able to achieve full calendar sync using event response email notifications from google calendar:
our system generated an email with an ics attachment
the user responded via gmail or google calendar
the email address listed for the organizer in the ics file received an event response email notification with corresponding ics information
our system ingested the ics file to keep their response in sync
We have now noticed that event response email notifications are no longer sent to non-gmail organizer email addresses.
We were able to confirm the change in behavior using yahoo calendar/mail as well:
Notifications Sent:
create google calendar event, invite user via a gmail address, invitee responds via google calendar/gmail
create google calendar event, invite yahoo email address, invitee responds via yahoo calendar/yahoo mail
Notifications Not Sent:
create yahoo calendar event, invite gmail address, invitee responds via google calendar/gmail
Anybody have experience with this? Any workarounds?
Checkout these few resources:
google calendar invites are sometimes marked as spam
solution: add email filter to never mark emails from calendar-notification#google.com as spam.
google calendar help - invitation not received
solution 1: same thing, check spam folder.
solution 2: check calendar notification settings.
yahoo calenda help - not getting reminders
solution: check spam filters.
It may also help to add the address to your contacts so that it will be less likely that the notifications are marked as spam.
I am trying to test the new EventReservation Schema that Gmail offers to transaction confirmation emails sent from my site. I have followed all the steps recommendend on the site (https://developers.google.com/gmail/schemas/reference/event-reservation).
I also used the Structured data markup helper (https://www.google.com/webmasters/markup-helper/?email=true) to generate the Tags. using the script.google.com site i wrote a test to send the same confirmation emails but NO DICE!! Would anyone be able to help me?
How is your test failing? Are you expecting an inbox action button and not seeing it? Or are you expecting Google Now to generate a reminder card?
The Event Registration schema does not give the recipient an action button in the inbox. It should however be used by Google Now to generate a reminder card which will remind the recipient of the date/time of the event.
Google Now will remind the user on the day of the event. The user will
receive a time to leave reminder (based on traffic etc).
- Basic Event Reminder
When using the RSVP Action schema it should cause an action button to be displayed in the inbox that shows a dialog for the recipient to respond with a yes/no/maybe in regard to if they will attend the event.
In either case there are currently (at the time of this writing) a few gotchas in regard to using these schemas.
The first thing you need to know is that you must register with Google in order to be whitelisted to use these inbox actions in Gmail. Without registering and being whitelisted all you can do is send emails to yourself (your own Gmail account) in order to test these schemas out. If your trying to send to someone else's Gmail account it will not work.
Many of these schemas are only in API Preview mode for now.
As of July 11, 2013 the RSVP Action is only enabled for emails sent by Google Calendar.
You can follow updates relating to the inbox actions on the Release Notes page.