Page 3 of 3

PostPosted: Fri Dec 14, 2007 1:20 am
by lwc
Please report such a thing next time.

Anyway, just got a message from December 5th (the "received" headers still reflect just today).

SysKoll, PM me.

PostPosted: Fri Dec 14, 2007 3:03 am
by SysKoll
I'm really sorry, guys. Our machine is doing its best to keep up with the onslaught.

PostPosted: Sun Dec 16, 2007 10:13 am
by HerbSolo
Hello,

Sorry for my "hit and run" kind of post, my Windows Box is having some strange BSOD-troubles, which is keeping me busy.

Anyway, posting and then not coming back for so long is not a good way to say "thank you" to people who offer free support for a free service. I apologize.

BTW - i'm getting a "localhost.localdomain" certificate displayed when i access spamgourmet now. (Some time ago There was a "news" post on spamgourmet about this, but i haven't had this popup for some time now) - i've made a screenshot:

http://www.oerwg.com/files/screenshot.png

PostPosted: Sun Dec 16, 2007 4:54 pm
by SysKoll
HerbSolo wrote:BTW - i'm getting a "localhost.localdomain" certificate displayed when i access spamgourmet now. (Some time ago There was a "news" post on spamgourmet about this, but i haven't had this popup for some time now) - i've made a screenshot:

http://www.oerwg.com/files/screenshot.png


Are you talking about the https://www.spamgourmet.com site?
Something is wrong. Our certificate is signed by GoDaddy and is valid until 2009. The one you show has expired long along.

PostPosted: Sun Dec 16, 2007 6:36 pm
by HerbSolo
I tried it now, and it works again (godaddy certificate is shown again for https://www.spamgourmet.com) I couldn't reach the page for about an hour (after i got the wrong certificate)

All the delayed mails are here now too.

PostPosted: Mon Dec 17, 2007 11:23 am
by josh
Maybe you caught the web server in the process of initialization, and it didn't know which cert to send (or which site you should be looking at, etc.).

PostPosted: Fri Dec 21, 2007 5:10 am
by thehimalayas
SysKoll wrote:I'm really sorry, guys. Our machine is doing its best to keep up with the onslaught.


Thanks SysKoll. Here is another transcript, in case it helps. This is from an external address trying to send email to my a-bc.net address:

Code: Select all
 **********************************************
** THIS IS A WARNING MESSAGE ONLY **
** YOU DO NOT NEED TO RESEND YOUR MESSAGE **
**********************************************

The original message was received at Wed, 19 Dec 2007 16:19:12 -0500
from support.hrnoc.net [127.0.0.1]

----- Transcript of session follows -----
451 4.4.1 reply: read error from gourmet.spamgourmet.com.
... Deferred: Connection timed out with gourmet.spamgourmet.com.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old
Reporting-MTA: dns; support.hrnoc.net
Arrival-Date: Wed, 19 Dec 2007 16:19:12 -0500

Final-Recipient: RFC822; xxx.yyy@a-bc.net
Action: delayed
Status: 4.4.2
Last-Attempt-Date: Wed, 19 Dec 2007 20:46:45 -0500
Will-Retry-Until: Mon, 24 Dec 2007 16:19:12 -0500

PostPosted: Thu Jan 10, 2008 11:05 pm
by lwc
Note the 4 hours' wait from today:

...Received...
Received: by ...google.com with SMTP id z3so529796nzf.41
for <my spamgourmet address>; Thu, 10 Jan 2008 14:58:54 -0800 (PST)
Received: by (IP address) with SMTP id a1mr2612794waf.135.1199991418271;
Thu, 10 Jan 2008 10:56:58 -0800 (PST)

PostPosted: Wed Mar 05, 2008 8:40 pm
by lwc
Is there an attack again?

It takes hours (if not a day) for some of my messages to arrive, and people complain to me about getting delivery delays' messages.

PostPosted: Sun Mar 09, 2008 11:05 am
by xavierg2
I have also big issues with the delivery time.

Any problem?

Xavier

PostPosted: Sun Mar 09, 2008 9:29 pm
by SysKoll
Yes, we have problems. We seem to be a victim of a DoS attack. The machine is not happy and we have to babysit it. I won't give details in case this forum is read by malevolents, but I have to admit that whatever they are doing is working.

PostPosted: Thu Mar 13, 2008 6:49 am
by nick4mony
SysKoll wrote:Yes, we have problems. We seem to be a victim of a DoS attack.


I'll add my voice to the mess as well. I'm seeing these symptoms:

1. A few senders are getting DNS errors when they send to ...@dfgh.net addresses,

2. Other emails are coming through to me after a delay (several SG addresses),

3. I'm also trying to send-from-SG-address (xSGwordx.20.xSGacctx.at.recursor.net), from a Yahoo account, and getting a Connected to 216.75.35.164 but connection died. (#4.4.2) error.

3a. I've got that send-from-SG-address problem, for a different SG address I have (xSGword2x.xSGacctx.at.dfgh.net)


The bounce message I got is below, with the following substitutions:
  • xSGwordx - is the (obscufated) word I chose for the address
  • xSGacctx - is my (obscufated) username at SG
  • xCSOmonkeyx - is part of their (obscufated) email address (as in xCSOmonkeyx@virginmobile.com.au)
  • xProtectedx - is part of my (obscufated) real email address (as in xProtectedx@yahoo.com.au)
  • George Bush - is my (false) name
  • 0411000212 - this is real. It's a public automated service; no need for obscufation.
  • Most of the actual content has been chopped where indicated


Code: Select all
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following
 addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<+xSGwordx+xSGacctx+25112eebc7.xCSOmonkeyx#virginmobile.com.au@spamgourmet.com>:
Connected to 216.75.35.164 but connection died. (#4.4.2)
I'm not going to try again; this message has been in the queue too
 long.

--- Below this line is a copy of the message.

Return-Path: <xProtectedx@yahoo.com.au>
Received: (qmail 84057 invoked by uid 60001); 11 Mar 2008 05:55:45
 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com.au;

  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;

  b=cU0OBpsbQxxG+6+5xkfllD4ukp1/RrfZX9qzwAYW0wKIOiHrwh1A2b08AY4vFJJAa1IU7qdWKbwwIMD7+atB8HwbRpjJtC2Kccj1X+jLEMwHTnyPaLxQFljlqaPRIOmSmz8O2t9B2kdlpRbP4Qn0h1K1aobemDRTeXDV0hzUsz8=;
X-YMail-OSG:
 zya7XzsVM1m2se17YddRdOnLdCyeASYdOO2spBpITZ1ZOb1mmV5egqXzsiOp2mJRSQkKIbJrLs_wanoH.0Wo0UDw7XCJVp3BbY14HMKCdQn2uK_NHR94pr66n9VRaQ--
Received: from [121.91.16.87] by web65602.mail.ac4.yahoo.com via HTTP;
 Tue, 11 Mar 2008 16:55:45 EST
Date: Tue, 11 Mar 2008 16:55:45 +1100 (EST)
From: George Bush <xProtectedx@yahoo.com.au>
Subject: RE: Cannot use 0411000212 to leave a message
To:
 +xSGwordx+xSGacctx+25112eebc7.xCSOmonkeyx#virginmobile.com.au@spamgourmet.com
In-Reply-To:
 <629D6A5A1CEFFA4781B115C456E1590A096C6872@vmsydex001.virginmobile.com.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <247656.82887.qm@web65602.mail.ac4.yahoo.com>

Hi there,

I've never received an email reply for this issue, but it looks
like it's been fixed.  Thanks.

( a lot more message, portion below left for humour )
>
>
*******************************************************************
> Everything about this email and its attachments, including
> potentially confidential components, is only for the eyes and
> ears of the persons to whom it has been addressed (i.e. the
> persons whose names appear in the "To" section of the email;
> however, those listed in sections "CC" and "BCC" may also
> consider themselves included in the group whose eyes and ears
> this email is for.). In the event that no physical, emotional
> or spiritual resemblance can be made between you and the
> intended recipients, you have been mistakenly or deliberately
> omitted from the email, someone has given it to you, or you
> have nicked it. If you're not supposed to have access to this
> email, please delete it, destroy it and deprive others from
> it. Oh, and let us know when you are done.
>
*******************************************************************
>
>
>



      Get the name you always wanted with the new y7mail email address.
www.yahoo7.com.au/y7mail

PostPosted: Thu Mar 13, 2008 1:47 pm
by SysKoll
I'm not surprised. As I said, we are under heavy DoS attack right now. Some messages are bound to be lost while we are in this situation.