amazon ses sending problem

[David Kimont]

Hello everybody,

I am using ec2,e3 and ses for my grails application and the aws plugin. Everything works nice except of sending mails.

I have a verified email for ses and this config

grails {

   plugin {

      aws {

         credentials {

            accessKey = "blabla"

            secretKey = "blublub"

         }

      }

     ses {

            catchall = "[hidden email]" 

            from = "[hidden email]"

            enabled = true

      }

   }

}

and in the controller I am doing sth like this

            sesMail {

                to user.email

                subject "welcome"

                body "text"

            }

But in the log is always 

[AWS SES] E-mail sending disabled on this environment

 

If I am performing ping test, the mails will be delivered and checking quota is printing

aws-ses-get-send-quota

[AWS SES] The maximum number of emails the user is allowed to send in a 24-hour interval: 10000.0

[AWS SES] The maximum number of emails the user is allowed to send per second: 5.0

[AWS SES] The number of emails sent during the previous 24 hours: 2.0

The domain to this email is verified to, so I stay clueless and will be very grateful for any tips or a solution.

Best Regards

David Kimont

[jroenberg]

Hi David

It looks like your ses-closure is outside of the aws-closure ?

David Kimont wrote

grails {
   plugin {
      aws {
         credentials {
            accessKey = "blabla"
            secretKey = "blublub"
         }
      }
     ses {
            catchall = "[hidden email]"
            from = "[hidden email]"
            enabled = true
      }
   }
}

As examplified here it needs to be within: https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy

[David Kimont]

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[lucastex]

Jimi is right, 

The config structure is hierarchical :)

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[David Kimont]

Hello everybody,

I changed it, but the problem is still there. The documentation says, it is enabled by default.

So I still can' tsend with the same issue.

My new config:

grails {

   plugin {

        aws {

            credentials {

                accessKey = "accessKey"

                secretKey = "secretKey"

            }

            ses {

                catchall = "[hidden email]" 

                from = "[hidden email]"

                enabled = true

            }

      }

   }

}

I tried it without the credential closure with the same result.

Best regards

David

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

Jimi is right, 

The config structure is hierarchical :)

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[lucastex]

David, 

Can you isolate the source code and send me to test it here and find what is happening?

Thanks,

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hello everybody,

I changed it, but the problem is still there. The documentation says, it is enabled by default.

So I still can' tsend with the same issue.

My new config:

grails {

   plugin {

        aws {

            credentials {

                accessKey = "accessKey"

                secretKey = "secretKey"

            }

            ses {

                catchall = "[hidden email]" 

                from = "[hidden email]"

                enabled = true

            }

      }

   }

}

I tried it without the credential closure with the same result.

Best regards

David

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

Jimi is right, 

The config structure is hierarchical :)

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[David Kimont]

Hi Lucas,

very Kind. Meanwhile I uploaded my project repo on the ec2 und made a successfull pingtest from there.

best regards!

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

David, 

Can you isolate the source code and send me to test it here and find what is happening?

Thanks,

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hello everybody,

I changed it, but the problem is still there. The documentation says, it is enabled by default.

So I still can' tsend with the same issue.

My new config:

grails {

   plugin {

        aws {

            credentials {

                accessKey = "accessKey"

                secretKey = "secretKey"

            }

            ses {

                catchall = "[hidden email]" 

                from = "[hidden email]"

                enabled = true

            }

      }

   }

}

I tried it without the credential closure with the same result.

Best regards

David

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

Jimi is right, 

The config structure is hierarchical :)

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[David Kimont]

Hi Thanks a lot for the help.

It was the failure witch the clousure hierarchy. 2nd, I checked to late that the catch all address was very similar to that I was waiting for arrival mails.

David

2012/6/14 David Kimont <[hidden email]>

Hi Lucas,

very Kind. Meanwhile I uploaded my project repo on the ec2 und made a successfull pingtest from there.

best regards!

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

David, 

Can you isolate the source code and send me to test it here and find what is happening?

Thanks,

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hello everybody,

I changed it, but the problem is still there. The documentation says, it is enabled by default.

So I still can' tsend with the same issue.

My new config:

grails {

   plugin {

        aws {

            credentials {

                accessKey = "accessKey"

                secretKey = "secretKey"

            }

            ses {

                catchall = "[hidden email]" 

                from = "[hidden email]"

                enabled = true

            }

      }

   }

}

I tried it without the credential closure with the same result.

Best regards

David

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

Jimi is right, 

The config structure is hierarchical :)

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email

[lucastex]

So, Is it working right now for you?

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Thanks a lot for the help.

It was the failure witch the clousure hierarchy. 2nd, I checked to late that the catch all address was very similar to that I was waiting for arrival mails.

David

2012/6/14 David Kimont <[hidden email]>

Hi Lucas,

very Kind. Meanwhile I uploaded my project repo on the ec2 und made a successfull pingtest from there.

best regards!

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

David, 

Can you isolate the source code and send me to test it here and find what is happening?

Thanks,

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hello everybody,

I changed it, but the problem is still there. The documentation says, it is enabled by default.

So I still can' tsend with the same issue.

My new config:

grails {

   plugin {

        aws {

            credentials {

                accessKey = "accessKey"

                secretKey = "secretKey"

            }

            ses {

                catchall = "[hidden email]" 

                from = "[hidden email]"

                enabled = true

            }

      }

   }

}

I tried it without the credential closure with the same result.

Best regards

David

2012/6/13 Lucas F. A. Teixeira <[hidden email]>

Jimi is right, 

The config structure is hierarchical :)

[]s,

Lucas Teixeira

2012/6/13 David Kimont <[hidden email]>

Hi Jimi,

know I feel foolish, I did that by purpose but never thinkt about it.
Thank you very much :d

Best regards David

2012/6/13 jroenberg <[hidden email]>

Hi David

It looks like your ses-closure is outside of the aws-closure ?


David Kimont wrote

>
> grails {
>    plugin {
>       aws {
>          credentials {
>             accessKey = "blabla"
>             secretKey = "blublub"
>          }
>       }
>      ses {
>             catchall = "info@"

>             from = "info@"
>             enabled = true
>       }
>    }
> }
>

As examplified here it needs to be within:
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy
https://github.com/blanq/grails-aws/blob/master/grails-app/conf/Config.groovy


-----
Jimi
--
View this message in context: http://grails.1312388.n4.nabble.com/amazon-ses-sending-problem-tp4630016p4630018.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email