> Hey all,

> due to the way our mail system was setup the server entered in fr-
> config.groovy cannot send mail external to our organization, and
> returns a SMTP 530 relayed mail error.

> FR did not handle this very well and now it would appear that I have 2
> organizations that attempted to register that are now in limbo, as no
> work flow notifications were sent.

> I don't see any UI options to remove the defunct orgs so that they may
> re register setting the process in motion.

> I can find the data in the DB back end but am not skillful enough to
> craft the required select to roll back the entry, nether do I have any
> skill with Groovy so I can't just fire the work flow.

> Any one got any suggestions short of turfing the DB?

> Hi,
> This is actually due to an underlying library that FR relies on for mail distribution. I've discussed this with the authors in the past and they believe it isn't the libraries job to perform queuing which is true to a point. My best recommendation in this space if you have unreliable upstream relays is to install a local queue.

> FR 1.2 also does a little bit more to make this process more robust but it does still expect mail to be available 24/7.

> That being said have a look at the scripts in:https://github.com/ausaccessfed/federationregistrymaster/tree/master/...

> There is one there you can run in the console to delete organisations.

> Bradley

> Bradley Beddoes | Technical Architect | Australian Access Federation
> Mob: 0413768802 | Email: bradleybedd...@aaf.edu.au | Web:http://www.aaf.edu.au/
> Twitter:http://twitter.com/ausaccessfedFacebook:http://facebook.com/ausaccessfed

> PRIVILEGED – PRIVATE AND CONFIDENTIAL

> This email and any files transmitted with it are intended solely for the use of the addressee(s) and may contain information which is confidential or privileged.  If you receive this email and you are not the addressee(s) [or responsible for delivery of the email to the addressee(s)], please disregard the contents of the email, delete the email and notify the author immediately

> On 17/08/2011, at 5:40 AM, murray Martin wrote:

> > Hey all,

> > due to the way our mail system was setup the server entered in fr-
> > config.groovy cannot send mail external to our organization, and
> > returns a SMTP 530 relayed mail error.

> > FR did not handle this very well and now it would appear that I have 2
> > organizations that attempted to register that are now in limbo, as no
> > work flow notifications were sent.

> > I don't see any UI options to remove the defunct orgs so that they may
> > re register setting the process in motion.

> > I can find the data in the DB back end but am not skillful enough to
> > craft the required select to roll back the entry, nether do I have any
> > skill with Groovy so I can't just fire the work flow.

> > Any one got any suggestions short of turfing the DB?