Page 1 of 1

Problem with "send from SG address"

PostPosted: Wed May 27, 2009 12:03 am
by anon090526
I've used this feature before without any problems, including to the same recipient.
BTW, thanks for SG's existence.

Today I'm getting the mail bounced (two attempts).
One time I clicked on the generated address which opened my Mail.app, the econd time I copy/pasted it into the To: box. Same results.
Is this a temporary problem at SG, or is my ISP doing this, or something else? Any ideas?

Bounce message says (I've replaced specifics with "..."):
=========
Reporting-MTA: dns; fed1rmmtao103.cox.net
Arrival-Date: Tue, 26 May 2009 16:30:44 -0400
Received-From-MTA: dns; fed1rmimpo02.cox.net (70.169.32.72)

Final-Recipient: RFC822; < ... @spamgourmet.com>
Action: failed
Status: 5.2.0
Remote-MTA: dns; gourmet7.spamgourmet.com (216.75.35.164)
Diagnostic-Code: smtp; 554 5.7.1 address disabled

=======
'address disabled' by who? Cox has decided to block this?
BTW, receiving mail through SG still works fine.

Thanks for any help.

PostPosted: Wed May 27, 2009 2:18 am
by elseesea
I am having the same problem using the "send message from one of your spamgourmet addresses" feature to different domains including, but not limited to, aol.com and mchsi.com. I am sending from my gmail account to email address at the various domains, and I'm getting this message back from google:

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

+six40pm+sebalds+52872dfbf6.darcystever ... ourmet.com

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 554 554 5.7.1 address disabled (state 14).


anyone having the same problem?

Me Too

PostPosted: Wed May 27, 2009 7:04 pm
by TheBashar1
Yes, I'm having the same trouble as well.

PostPosted: Thu May 28, 2009 11:49 am
by hwk
And me too. Since yesterday. Still having the same issue today.