Gmail 'Fail' Folder - Githubissues

tarkal commented 9 years ago

The live system has 10 emails in the Fail folder. These need to be analysed to find out why they have failed and the parser needs to be adapted to prevent other emails from failing for the same reason.

They do all seem to have either attachments, images or tables / HTML.

Be careful not ingest the failed emails into the dev or QA system directly as they will send an email to the sender telling them that a new ticket has been created

N.B. Let me know how you would like me to get them to you

cantorfan commented 9 years ago

send the email to my gmail. cantorfan@gmail.com, and I will test them in my local env, it will not be ingested in QA or LIVE.

cantorfan commented 9 years ago

Hi Tarka,

I tested on QA, there is AWS key error, same as last time sending email. Please help to set the correct env properties on QA. It is also existing in sending email.

com.amazonaws.services.s3.model.AmazonS3Exception: The request signature we
calculated does not match the signature you provided. Check your key and
signing method. (Se
rvice: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch;
Request ID: 1A9A2FC71CA2D0BF), S3 Extended Request ID:
kxftNJhJbc1uQRCq4LuNIBWi4I5+ONHAfIVEx7sq6Y
dBEGkPGVaO8jqvxv58sW/88/ffF4NcZnQ=
        at
com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:937)
        at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:506)
        at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:273)
        at
com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:3660)
        at
com.amazonaws.services.s3.AmazonS3Client.initiateMultipartUpload(AmazonS3Client.java:2638)
        at
com.dastrax.app.service.internal.DefaultStorageManager.put(DefaultStorageManager.java:219)
        at
com.dastrax.app.upload.DefaultUploadManager.upload(DefaultUploadManager.java:177)
        at
com.dastrax.per.entity.Attachment.uploadEmailAttachment(Attachment.java:200)
        at
com.dastrax.app.gmail.EmailToTicket.dumpPart(EmailToTicket.java:513)
        at
com.dastrax.app.gmail.EmailToTicket.getMessage(EmailToTicket.java:351)

The request signature we calculated does not match the signature you
provided. Check your AWS Secret Access Key and signing method. Consult the
service documentation
for details. (Service: AmazonSimpleEmailService; Status Code: 403; Error
Code: SignatureDoesNotMatch; Request ID:
193cab76-2453-11e5-bc6b-219f5d8c538d)
com.amazonaws.AmazonServiceException: The request signature we calculated
does not match the signature you provided. Check your AWS Secret Access Key
and signing method
. Consult the service documentation for details. (Service:
AmazonSimpleEmailService; Status Code: 403; Error Code:
SignatureDoesNotMatch; Request ID: 193cab76-2453-11e5
-bc6b-219f5d8c538d)
        at
com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:937)
        at
com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:506)
        at
com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:273)
        at
com.amazonaws.services.simpleemail.AmazonSimpleEmailServiceClient.invoke(AmazonSimpleEmailServiceClient.java:1407)
        at
com.amazonaws.services.simpleemail.AmazonSimpleEmailServiceClient.sendEmail(AmazonSimpleEmailServiceClient.java:1145)
        at
com.dastrax.app.email.DefaultEmailer$Sender.sendEmail(DefaultEmailer.java:266)
        at
com.dastrax.app.email.DefaultEmailer.send(DefaultEmailer.java:137)
        at com.dastrax.per.entity.User.sendEmail(User.java:1033)
        at com.dastrax.per.entity.User.newUserEmail(User.java:901)
        at com.dastrax.per.entity.User.create(User.java:537)
        at
com.dastrax.app.gmail.EmailToTicket.createUser(EmailToTicket.java:310)
        at
com.dastrax.app.gmail.EmailToTicket.aquireAccount(EmailToTicket.java:264)
        at
com.dastrax.app.gmail.EmailToTicket.processEmail(EmailToTicket.java:91)

Regards, Cantor

tarkal commented 9 years ago

The code is correct but the credentials had an error. You can access the new credentials in QA using printenv in the docker container.

cantorfan commented 9 years ago

what's the correct credentials

tarkal commented 9 years ago

... my previous comment!

cantorfan commented 9 years ago

Hi Tarka,

I don't understand how to proceed, please help.

the key in dock env is AWS_SECRET_KEY=voMXioBC+Dy+nMUvAJ24dpRB0nnCSf3t7H8BLO8Z, Is that correct? If code is correct, so it should load this key, right?

2015-07-07 17:13 GMT+08:00 solid-tarka notifications@github.com:

... my previous comment!

— Reply to this email directly or view it on GitHub https://github.com/solid-software/dastrax/issues/47#issuecomment-119133591 .

cantorfan commented 9 years ago

tested, it is fixed. There are some test ticket created successfully. But I find a bug, when the email is FW several time and send to solid support. we can not parse the email content correctly. I will add a bug for this.

Next, how will we handle the failed emails? Manually handled them by someone? Or we write some code to read it once?

tarkal commented 9 years ago

Make sure that you improve the parser so that it can handle FWD emails. I will manually move emails from fail folder back to inbox.

tarkal commented 9 years ago

Let me know when you are ready for me to move the Fail mails back into the Inbox.

cantorfan commented 9 years ago

I am working on thee FW content parse issue, wait for my notification

2015-07-08 15:28 GMT+08:00 solid-tarka notifications@github.com:

Let me know when you are ready for me to move the Fail mails back into the Inbox.

— Reply to this email directly or view it on GitHub https://github.com/solid-software/dastrax/issues/47#issuecomment-119468320 .

ff36 / jnoc

Gmail 'Fail' Folder #47