AquaMail Forum

English - Android => Bug reports => Topic started by: garyelmes on January 05, 2019, 07:00:09 am

Title: Non compliance with RFC 5321
Post by: garyelmes on January 05, 2019, 07:00:09 am

Hi.

I've noticed that Aqua mail appears to have a small but irritating non-compliance with RFC 5321.

When testing the server configuration by logging in and testing sending of email to the SMTP server, Aqua mail sends a non-compliant "MAIL FROM:" command. The command is sent in the form "MAIL FROM: <user@example.com>" rather than in the compliant form of "MAIL FROM:<user@example.com>"; i.e. there is a space between the "FROM:" and the reverse path. It may do this when actually sending emails as well - I couldn't get that far :-)

This means that Aqua mail is unable to validate against a dovecot/submission server unless that server is specifically configured to handle this type of broken behaviour. By default, dovecot will respond with a 501 error "Invalid FROM: Unexpected whitespace before path" unless it has been configured with "submission_client_workarounds = whitespace-before-path".

Title: Re: Non compliance with RFC 5321
Post by: Kostya Vasilyev on January 08, 2019, 12:45:16 pm

I'll check this thanks.

Title: Re: Non compliance with RFC 5321
Post by: Kostya Vasilyev on January 08, 2019, 01:08:22 pm

Same with

RCPT TO: <...>

I suppose - but you don't get that far without enabling the workaround, and once you do, that doesn't matter. Right?

Title: Re: Non compliance with RFC 5321
Post by: Kostya Vasilyev on January 08, 2019, 02:03:06 pm

Let's see if this helps:

https://www.aqua-mail.com/staging/AquaMail-market-1.18.1-1407-stable-c7b59972e4c7.apk

You can update in-place.