search

OpenESignForms / openesignforms

Open eSignForms is the first open source SaaS web contracting platform
https://open.esignforms.com
107 stars 50 forks source link

Improved support for externally hosted email servers. #109

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
     Configure system to user external email servers.
     smtp.1and1.com
     imap.1and1.com

     Enter usernames for both and enable SSL|TLS
     user@domain.tld

     Send emails|notifications|invites.

What is the expected output? What do you see instead?
     The email should go through to the user.

     Get a illegal character in domain name.

What version of the product are you using? On what operating system?
     13.6.8 p0613 + updated PickupTransaction.class
     Redhat OpenShift hosted platform
     2.6.32-358.14.1.el6.x86_64

Please provide any additional information below.
     https://groups.google.com/forum/#!topic/openesignformsdev/av9CHYdXaYE

     https://forums.aws.amazon.com/thread.jspa?messageID=363239
     1.  Code should manually set the message ID.
     2.  Code should also watch for message ID appended to the OK message of the DATA command.

    If a message ID is returned different than the randomly generated one then update the messageID in the database for that outbound email.

    Provide an option to disable the SMTP Return Host Path.

Original issue reported on code.google.com by yap...@gmail.com on 1 Aug 2013 at 7:33

GoogleCodeExporter commented 9 years ago 
I think the method your using now is similar to(or exactly) like VERP?
http://cr.yp.to/proto/verp.txt

Looks like 1and1 does allow the creation of catch-all email addresses.
http://help.1and1.com/e-mail-c37589/standard-e-mail-c37590/using-the-product-c85
088/create-a-catch-all-e-mail-account-a624597.html

So maybe we just need a more detailed method of crafting the SMTP Reply Host 
Path that will be used?

I created a sub-domain esign.<mydomain>.tld.  Then created a catch all email 
address for that sub-domain that forwards to my SMTP|IMAP account I used in 
OpenESF.

*@esign.<mydomain>.tld forwards to esign@<mydomain>.tld that would get received 
by OpenESF.

So the return path would need to be something 
like:<randomstuffIwontuse>_<randommessageid>@esign.<mydomain>.tld

I am trying to make this work without having to change how the bounced messages 
get processed.

Original comment by yap...@gmail.com on 1 Aug 2013 at 8:06

GoogleCodeExporter commented 9 years ago 
Yes, it's based on VERP.  With our new normalize of the imap user name, we 
should be able to generate a legal return-path even if your imap user name is 
more than just a single name, but is itself an email address or more.

This may be fixed already in 13.8.10.

Original comment by yoz...@gmail.com on 1 Aug 2013 at 9:51

GoogleCodeExporter commented 9 years ago 
Wonderful.  Was the change simple enough that you can provide the updated files 
to downnload?

Original comment by yap...@gmail.com on 1 Aug 2013 at 9:55

GoogleCodeExporter commented 9 years ago 
I think you can call this fixed. :)

Original comment by yap...@gmail.com on 2 Aug 2013 at 5:41

GoogleCodeExporter commented 9 years ago 
Fixed in 13.8.10 by normalizing the imap user name as described in

http://code.google.com/p/openesignforms/wiki/InstallationUsingVaadin7#SMTP_and_I
MAP

(normalized to lowercase and replacing any non-alphanumeric, period, underscore 
or hyphen by '_')

Original comment by yoz...@gmail.com on 2 Aug 2013 at 6:29