View Issue Details

IDProjectCategoryView StatusLast Update
0004697SOGoWeb Calendarpublic2019-10-30 08:06
Reporterjohan.smits Assigned Toludovic  
PrioritynormalSeveritymajorReproducibilityalways
Status feedbackResolutionreopened 
PlatformLinuxOSDebianOS VersionJessie
Product Version4.0.5 
Summary0004697: Invalid calendar message
Description

When a calendar message is send (as a confirmation) by SOGo this gets rejected by AWS SES.

We use a SES relay for postfix but these messages get rejected.

email-smtp.eu-west-1.amazonaws.com[54.229.202.252] said: 554 Transaction
failed: Expected parameter value, got ";" (in reply to end of DATA command)

Steps To Reproduce

Confirm a calendar invite.

Additional Information

Return-Path: <johan.smits@domain.com>
Received: from authenticated-user (mail.domain.com [127.0.0.1])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by mail.leftclick.eu (Postfix) with ESMTPSA id 149C064FBE5C
for <art@other-domain.com>; Mon, 4 Mar 2019 16:10:08 +0000 (UTC)
To: "Art | Company" <aart@other-domain.com>
Content-Type: multipart/mixed; boundary="----=_=-_OpenGroupware_orgNGMime-5734-1551715808.583314-1------"
MIME-Version: 1.0
Date: Mon, 04 Mar 2019 17:10:08 +0100
Subject: Uitnodiging =?utf-8?q?geaccepteerd=3A?==?utf-8?q?
=22Customer?=
project =?utf-8?q?bespreking=22?=
Message-ID: <1666-5c7d4e00-f-4d3c5080@203957316>
X-Sogo-Message-Type: calendar:invitation-reply
From: "Johan Smits" <johan.smits@domain.com>

TagsNo tags attached.

Activities

ludovic

ludovic

2019-10-28 19:38

administrator   ~0013864

The only ; I see is:

Content-Type: multipart/mixed; boundary="----=_=-_OpenGroupware_org_NGMime-5734-1551715808.583314-1------"

which is legit.

johan.smits

johan.smits

2019-10-29 08:03

reporter   ~0013868

I know but why does this generate a error? The issue still exists and it only occurs when accepting a reservation (which the server generates). Not a reservation that I create and invites others.

Christian Mack

Christian Mack

2019-10-30 08:06

developer   ~0013870

Your guess is as good as ours.
Ask AWS instead.
When they provide some clue, perhaps there is a fix on their side or SOGo's.

Issue History

Date Modified Username Field Change
2019-03-05 06:39 johan.smits New Issue
2019-10-28 19:38 ludovic Note Added: 0013864
2019-10-28 19:38 ludovic Status new => closed
2019-10-28 19:38 ludovic Assigned To => ludovic
2019-10-28 19:38 ludovic Resolution open => suspended
2019-10-29 08:03 johan.smits Note Added: 0013868
2019-10-29 08:03 johan.smits Status closed => feedback
2019-10-29 08:03 johan.smits Resolution suspended => reopened
2019-10-30 08:06 Christian Mack Note Added: 0013870