Re: [SOGo] Issues with Apostrophe (Single Quote)

[Christian Mack]

Hi Andrew

Sorry, but all "Received" Headers are added by SMTP server en route of
the email, not SOGo.
That specific Received header is added by the first postfix on mercury.

As I said, most SMTP Servers do not support those characters.
Standards conform or not, it is a gamble to use such an address.


Kind regards,
Christian Mack

Am 27.11.19 um 13:42 schrieb Andrew Mogg (and...@logicomm.co.uk):
> Hi Anselm
> SOGo version is 4.1.1
> It is running onNethServer 7.7.1908
> 
> The original email headers (with quote marks now included):
> Return-Receipt-To: "Andy Hope" 
> From: "Andy Hope" 
> To: <"Danny.O'Brien"@#>
> References: 
> 
>  
> 
>  
> 
> In-Reply-To: 
> 
> Subject: RE: water meter transducer
> Date: Wed, 27 Nov 2019 09:49:06 -
> Message-ID:
> 
> 
> The return Bounce message fails on the user not known, Notice the single 
> quote has been removed in the header on the For header, but not the To. Sogo 
> has stripped the ‘ from the email address. I cannot ask a customer to change 
> their email address due to our systems.
> 
> Return-Path: 
> Received: from localhost (localhost [127.0.0.1])
> (Authenticated sender: andy.hope@)
> by mercury.#(Postfix) with ESMTPA id A26BE10093573
> for ; Wed, 27 Nov 2019 09:49:06 + 
> (GMT)
> Return-Receipt-To: "Andy Hope" 
> From: "Andy Hope" 
> To: 
> References: 
> 
>  
> 
>  
> 
> In-Reply-To: 
> 
> 
> From: users-requ...@sogo.nu  On Behalf Of Anselm 
> Martin Hoffmeister
> Sent: 26 November 2019 17:10
> To: users@sogo.nu
> Subject: Re: [SOGo] Issues with Apostrophe (Single Quote)
> 
> 
> Hi Andrew,
> 
> I just tested writing a mail from SOGo webmail (4.1.0 in this case) to a fake 
> version of my private account elsewhere, having inserted an apostrophe '. My 
> private server rightfully refuses the (invalid) destination address - it 
> seems SOGo does everything correctly here and hands through the apostrophe 
> exactly as I would expect.
> 
> Trying to replicate the problem, doing the same with both the forward and 
> backward tick ´` (single quotation marks or accent over blank, or whatever 
> you call them), the same happens, SOGo hands through those mails and the 
> destination server then refuses - the forward tick for "invalid postbox", the 
> backtick as "restricted characters in address", and the non-delivery mail 
> quotes the refused target address including the superfluous characters.
> 
> So it seems (my) SOGo 4.1.0 works correctly. But there may be other parties 
> involved: Usually SOGo hands off the mail to a local running exim (or 
> postfix), which then forwards the mail as applicable. There may be a 
> different mail path between roundcube and SOGo, depending on your local 
> configuration.
> 
> Can you find some relevant lines in the mail server logs? In exim case and on 
> Debian(ish) Linuxes, /var/log/exim4/mainlog would be the place to investigate.
> 
> Also having details on the software version involved and perhaps the relevant 
> parts of the SOGO config may be helpful.
> 
> Best regards
> 
> Anselm
> Am 26.11.2019 um 13:37 schrieb Andrew Mogg 
> (and...@logicomm.co.uk<mailto:and...@logicomm.co.uk>):
> 
> Hi
> We are having issues with a particular email address which has a ‘ in its 
> email address. Such as Dano’rou...@gmail.com<mailto:rou...@gmail.com>
> When the email is sent from SOGo, it removes the ‘ from the email address, so 
> the email is actually sent to 
> danorou...@gmail.com<mailto:danorou...@gmail.com> and therefore fails (ie 
> bounces). Interestingly, when I access the server via Roundcube and send, 
> this does not happen, so its SOGo
> Has anyone had any experience of this?
> 
> This email has been scanned for email related threats and delivered safely by 
> Exascale.
> For more information please visit https://www.exascale.co.uk
> 
> 
> --
> users@sogo.nu<mailto:users@sogo.nu>
> https://inverse.ca/sogo/lists
> --
> users@sogo.nu<mailto:users@sogo.nu>
> https://inverse.ca/sogo/lists
> 


-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature

RE: [SOGo] Issues with Apostrophe (Single Quote)

[Andrew Mogg]

Hi Anselm
SOGo version is 4.1.1
It is running onNethServer 7.7.1908

The original email headers (with quote marks now included):
Return-Receipt-To: "Andy Hope" 
From: "Andy Hope" 
To: <"Danny.O'Brien"@#>
References: 
 
 

In-Reply-To: 

Subject: RE: water meter transducer
Date: Wed, 27 Nov 2019 09:49:06 -
Message-ID:


The return Bounce message fails on the user not known, Notice the single quote 
has been removed in the header on the For header, but not the To. Sogo has 
stripped the ‘ from the email address. I cannot ask a customer to change their 
email address due to our systems.

Return-Path: 
Received: from localhost (localhost [127.0.0.1])
(Authenticated sender: andy.hope@)
by mercury.#(Postfix) with ESMTPA id A26BE10093573
for ; Wed, 27 Nov 2019 09:49:06 + (GMT)
Return-Receipt-To: "Andy Hope" 
From: "Andy Hope" 
To: 
References: 
 
 

In-Reply-To: 


From: users-requ...@sogo.nu  On Behalf Of Anselm Martin 
Hoffmeister
Sent: 26 November 2019 17:10
To: users@sogo.nu
Subject: Re: [SOGo] Issues with Apostrophe (Single Quote)


Hi Andrew,

I just tested writing a mail from SOGo webmail (4.1.0 in this case) to a fake 
version of my private account elsewhere, having inserted an apostrophe '. My 
private server rightfully refuses the (invalid) destination address - it seems 
SOGo does everything correctly here and hands through the apostrophe exactly as 
I would expect.

Trying to replicate the problem, doing the same with both the forward and 
backward tick ´` (single quotation marks or accent over blank, or whatever you 
call them), the same happens, SOGo hands through those mails and the 
destination server then refuses - the forward tick for "invalid postbox", the 
backtick as "restricted characters in address", and the non-delivery mail 
quotes the refused target address including the superfluous characters.

So it seems (my) SOGo 4.1.0 works correctly. But there may be other parties 
involved: Usually SOGo hands off the mail to a local running exim (or 
postfix), which then forwards the mail as applicable. There may be a 
different mail path between roundcube and SOGo, depending on your local 
configuration.

Can you find some relevant lines in the mail server logs? In exim case and on 
Debian(ish) Linuxes, /var/log/exim4/mainlog would be the place to investigate.

Also having details on the software version involved and perhaps the relevant 
parts of the SOGO config may be helpful.

Best regards

Anselm
Am 26.11.2019 um 13:37 schrieb Andrew Mogg 
(and...@logicomm.co.uk<mailto:and...@logicomm.co.uk>):

Hi
We are having issues with a particular email address which has a ‘ in its email 
address. Such as Dano’rou...@gmail.com<mailto:rou...@gmail.com>
When the email is sent from SOGo, it removes the ‘ from the email address, so 
the email is actually sent to danorou...@gmail.com<mailto:danorou...@gmail.com> 
and therefore fails (ie bounces). Interestingly, when I access the server via 
Roundcube and send, this does not happen, so its SOGo
Has anyone had any experience of this?

This email has been scanned for email related threats and delivered safely by 
Exascale.
For more information please visit https://www.exascale.co.uk


--
users@sogo.nu<mailto:users@sogo.nu>
https://inverse.ca/sogo/lists
--
users@sogo.nu<mailto:users@sogo.nu>
https://inverse.ca/sogo/lists
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Issues with Apostrophe (Single Quote)

[Markus Winkler]

Hello Christian,

On 26.11.19 18:03, Christian Mack (christian.m...@uni-konstanz.de) wrote:

We are having issues with a particular email address which has a ' in its email 
address. Such as Dano'rou...@gmail.com
When the email is sent from SOGo, it removes the ' from the email address, so 
the email is actually sent to danorou...@gmail.com



That is an invalid email address.
You need Quotes around it to work:
"Dano'rourke"@gmail.com


according to RFC 2822 and it's successor RFC 5322 and IMHO that's not 
necessary and it's a bug if SOGo removes the "'":


https://tools.ietf.org/html/rfc5322

3.2.3.  Atom

   Several productions in structured header field bodies are simply
   strings of certain basic characters.  Such productions are called
   atoms.

   Some of the structured header field bodies also allow the period
   character (".", ASCII value 46) within runs of atext.  An additional
   "dot-atom" token is defined for those purposes.

  Note: The "specials" token does not appear anywhere else in this
  specification.  It is simply the visible (i.e., non-control, non-
  white space) characters that do not appear in atext.  It is
  provided only because it is useful for implementers who use tools
  that lexically analyze messages.  Each of the characters in
  specials can be used to indicate a tokenization point in lexical
  analysis.

   atext   =   ALPHA / DIGIT /; Printable US-ASCII
   "!" / "#" /;  characters not including
   "$" / "%" /;  specials.  Used for atoms.
   "&" / "'" /
   "*" / "+" /
   "-" / "/" /
   "=" / "?" /
   "^" / "_" /
   "`" / "{" /
   "|" / "}" /
   "~"

   atom=   [CFWS] 1*atext [CFWS]

   dot-atom-text   =   1*atext *("." 1*atext)

   dot-atom=   [CFWS] dot-atom-text [CFWS]

   specials=   "(" / ")" /; Special characters that do
   "<" / ">" /;  not appear in atext
   "[" / "]" /
   ":" / ";" /
   "@" / "\" /
   "," / "." /
   DQUOTE


   Both atom and dot-atom are interpreted as a single unit, comprising
   the string of characters that make it up.  Semantically, the optional
   comments and FWS surrounding the rest of the characters are not part
   of the atom; the atom is only the run of atext characters in an atom,
   or the atext and "." characters in a dot-atom.

3.2.4.  Quoted Strings

   Strings of characters that include characters other than those
   allowed in atoms can be represented in a quoted string format, where
   the characters are surrounded by quote (DQUOTE, ASCII value 34)
   characters.
[...]



I would ditch that address and get one without special characters.
I have seen too many SMTP servers not accepting such addresses at all.


Then they aren't RFC compliant.

For instance: an e-mail address like foo+...@example.com (Postfix: 
recipient_delimiter = + and the e-mail will then finally be delivered to 
f...@example.com) is widely used (and I never saw a problem with such an 
address on Postfix, Dovecot, Thunderbird etc.).


According to the RFC that "+" is within the same category of characters 
like the "'" of Dano'rou...@gmail.com (atext) and therefore has to be 
accepted by any compliant software.


Just my $ 0.02

Kind regards,
Markus
--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Issues with Apostrophe (Single Quote)

[Anselm Martin Hoffmeister]

Hi Andrew,

I just tested writing a mail from SOGo webmail (4.1.0 in this case) to a 
fake version of my private account elsewhere, having inserted an 
apostrophe '. My private server rightfully refuses the (invalid) 
destination address - it seems SOGo does everything correctly here and 
hands through the apostrophe exactly as I would expect.


Trying to replicate the problem, doing the same with both the forward 
and backward tick ´` (single quotation marks or accent over blank, or 
whatever you call them), the same happens, SOGo hands through those 
mails and the destination server then refuses - the forward tick for 
"invalid postbox", the backtick as "restricted characters in address", 
and the non-delivery mail quotes the refused target address including 
the superfluous characters.


So it seems (my) SOGo 4.1.0 works correctly. But there may be other 
parties involved: Usually SOGo hands off the mail to a local running 
exim (or postfix), which then forwards the mail as applicable. There 
may be a different mail path between roundcube and SOGo, depending on 
your local configuration.


Can you find some relevant lines in the mail server logs? In exim case 
and on Debian(ish) Linuxes, /var/log/exim4/mainlog would be the place to 
investigate.


Also having details on the software version involved and perhaps the 
relevant parts of the SOGO config may be helpful.


Best regards

Anselm

Am 26.11.2019 um 13:37 schrieb Andrew Mogg (and...@logicomm.co.uk):


Hi

We are having issues with a particular email address which has a ‘ in 
its email address. Such as Dano’rou...@gmail.com


When the email is sent from SOGo, it removes the ‘ from the email 
address, so the email is actually sent to danorou...@gmail.com 
 and therefore fails (ie bounces). 
Interestingly, when I access the server via Roundcube and send, this 
does not happen, so its SOGo


Has anyone had any experience of this?


This email has been scanned for email related threats and delivered 
safely by Exascale.

For more information please visit https://www.exascale.co.uk


--
users@sogo.nu
https://inverse.ca/sogo/lists

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Issues with Apostrophe (Single Quote)

[Christian Mack]

Hello

Am 26.11.19 um 13:37 schrieb Andrew Mogg (and...@logicomm.co.uk):
> Hi
> We are having issues with a particular email address which has a ' in its 
> email address. Such as Dano'rou...@gmail.com
> When the email is sent from SOGo, it removes the ' from the email address, so 
> the email is actually sent to 
> danorou...@gmail.com and therefore fails (ie 
> bounces). Interestingly, when I access the server via Roundcube and send, 
> this does not happen, so its SOGo
> Has anyone had any experience of this?
> 
> 

That is an invalid email address.
You need Quotes around it to work:
"Dano'rourke"@gmail.com

I would ditch that address and get one without special characters.
I have seen too many SMTP servers not accepting such addresses at all.


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature