bbs.spamgourmet.com

Hello

I'm not receiving any of my messages from www.livejournal.com. When I log into advanced mode, it shows that the messages have been forwarded (9 of them to be exact), but none of them ever seem to make it to my inbox. It's been about a day or so, but I'm not sure how much of a delay is normal with Spamgourmet, since all of the other emails have been almost instantaneous. I've switched my protected address between a gmail and an sbcglobal account, with similar results for each one.

Any and all help is greatly appreciated.

I am having the same problem with emails coming from crushcalculator.com. It says 6 emails have been forwarded from that address since February 8th. I have not received one of them. All of my other ones have been coming through fine, so I'm not sure what is up with this. The emails are sent almost immediately to spamgourmet and the count forwarded is incremented, but then I never get them. I've checked my inbox and bulk folders but nothing has appeared.


P.S. my email provider is yahoo.

Once the message counter has been incremented, the message is out of the spamgourmet code and on its way -- from there, our mail server tries to deliver it to the forwarding address (and this normally happens right away). So far, the delivery problems we've seen have to do with downstream spam filters, at times controlled by service providers rather than users. Could that be the case here? If you're still getting mail on other disposable addresses, then the providers probably haven't blacklisted the spamgourmet server itself (that has happened before, unfortunately), but rather have filters that catch some aspect of the affected mail.

That might be the case, the address in question begins with "orz" as that's part of the username in question. It's not making its way to any of the addresses I've tried forwarding to, so what you're describing makes sense. Any ways to intercept it or whatnot? Livejournal insists on sending me my password notification and confirmation notification to that email address, so I'm pretty much FUBARed right now, it seems.

Either way, thanks for the help. That sheds a bit of light on the situation.

I have the same problem, and I've forgotten my Livejournal password, so I'm in rather of a pinch..

Here's what happens:

the forwarding email in question is livejournal.20.thecyclops@samgourmet.com (there's plenty of remaining emails)

*if I send an email from either gmail or my own private email to that spamgourmet address, it goes through fine.

*If I request a password change from livejournal, it sends an email (the counters go down), but I never receive it, regardless of where I have spamgourmet forward the emails (gmail or my private email).

*if I make a new livejournal account and use a gmail account as my email address, the message goes through fine

So, the following communication channels work (note: spamgourmet referes to livejournal.20.thecyclops@samgourmet.com):
Livejournal to gmail
PrivateEmail to spamgourmet to gmail
gmail to spamgourmet to privateemail

But this fails:
Livejoural to spamgourmet to gmail
livejournal to spamgourmet to privateemail

As far as I have noticed, all my other disposable addresses forward fine. So if this is a junkmail filter downstream of spamgourmet, it should either block emails directly from livejournal, or block the other spamgourmet emails, but that is not the case.

Since the spamgourmet counters decrement properly, it looks like it is receiving the livejournal emails. My guess is that there is something on the outgoing spamgourmet mail server that is blocking these emails.

Thanks for doing all that research. If you can show me the headers from one of the emails that made it -- eg, livejournal -> gmail, that may help.

josh wrote:Thanks for doing all that research. If you can show me the headers from one of the emails that made it -- eg, livejournal -> gmail, that may help.

Sure! I hope it help...

Here is livejournal->gmail

Code: Select all

Delivered-To: <removed>@gmail.com
Received: by 10.48.212.13 with SMTP id k13cs879423nfg;
        Wed, 27 Dec 2006 10:37:29 -0800 (PST)
Received: by 10.64.241.3 with SMTP id o3mr7735676qbh.1167244649135;
        Wed, 27 Dec 2006 10:37:29 -0800 (PST)
Return-Path: <webmaster@livejournal.com>
Received: from livejournal.com (livejournal.com [204.9.177.18])
        by mx.google.com with ESMTP id e18si10648480qbe.2006.12.27.10.37.28;
        Wed, 27 Dec 2006 10:37:29 -0800 (PST)
Received-SPF: pass (google.com: domain of webmaster@livejournal.com designates 204.9.177.18 as permitted sender)
Received: from localhost (theschwartz [127.0.0.1])
   by livejournal.com (TheSchwartzMTA) with ESMTP id a5456099cdcb710552e97f4b6493163f00898545842;
   Wed, 27 Dec 2006 18:37:28 +0000 (UTC)
Message-ID: <sch-a5456099cdcb710552e97f4b6493163f-898545842@livejournal.com>
Content-Disposition: inline
Content-Length: 305
Content-Transfer-Encoding: binary
Content-Type: text/plain
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.72; A1.62; B3.04; Q3.03)
Date: Wed, 27 Dec 2006 18:37:28 UT
From: webmaster@livejournal.com (LiveJournal.com)
To: <removed>@gmail.com
Subject: Lost Username

This is your requested username reminder from LiveJournal.com.  Below are the usernames you have registered for the email address <removed>@gmail.com:

          <removed>

This information was requested on the website from  (66.186.116.126).

Regards,
LiveJournal.com Team

http://www.livejournal.com/

here is gmail->spamgourmet->privateemail

Code: Select all

Content-Type:      multipart/alternative; boundary="----=_Part_176026_26470749.1167238310120"
Date:     Wed, 27 Dec 2006 11:51:50 -0500 [12/27/2006 11:51:50 AM EST]
Delivered-To:  <removed>

DomainKey-Signature:     a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=gv4hbfh/ZYY/tZYSR2acPEvSxhk0Tr90B1d+4eQuYYIdNQZlQYHqYUARgFjn9mqxSGkjJm2aKkE2rhFLeeJ1ZiGs7hQdGu/wvUwWMszK2QkeKsIL1nN5Ybl62NGIoDpmkJkehfJ7xs+IEiUALMJu6PH8b3DBPYrP56t7p6kKHbo=
From:     "<removed>@gmail.com" <+livejournal+thecyclops+8861f3a428.removed#gmail.com@spamgourmet.com>
MIME-Version:     1.0
Message-ID:     <ba79991c0612270851p2f40c38q1d5cd9beb9a0fcdb@mail.gmail.com>
Received:     

    * (qmail 22068 invoked by uid 399); 27 Dec 2006 16:29:50 -0000
    * (qmail 22058 invoked by uid 399); 27 Dec 2006 16:29:50 -0000
    * from unknown (HELO gourmet.spamgourmet.com) (216.75.35.164) by mail.existhost.com with SMTP; 27 Dec 2006 16:29:50 -0000
    * from gourmet.spamgourmet.com (localhost.localdomain [127.0.0.1]) by gourmet.spamgourmet.com (8.13.7/8.13.7) with ESMTP id kBRGpYm5013038 for <removed>; Wed, 27 Dec 2006 08:51:34 -0800
    * (from jqh1@localhost) by gourmet.spamgourmet.com (8.13.7/8.13.7/Submit) id kBRGpXZn013016 for <removed>; Wed, 27 Dec 2006 08:51:34 -0800
    * from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.237]) by gourmet.spamgourmet.com (8.13.7/8.13.7) with ESMTP id kBRGpWcV012965 for <livejournal.20.thecyclops@spamgourmet.com>; Wed, 27 Dec 2006 08:51:33 -0800
    * by wr-out-0506.google.com with SMTP id i21so1569305wra for <livejournal.20.thecyclops@spamgourmet.com>; Wed, 27 Dec 2006 08:51:50 -0800 (PST)
    * by 10.90.79.6 with SMTP id c6mr11600950agb.1167238310143; Wed, 27 Dec 2006 08:51:50 -0800 (PST)
    * by 10.90.65.2 with HTTP; Wed, 27 Dec 2006 08:51:50 -0800 (PST)

Received-SPF:     none (mail.existhost.com: domain at spamgourmet.com does not designate permitted sender hosts) identity=mailfrom; client-ip=216.75.35.164; envelope-from=<+livejournal+thecyclops+8861f3a428.removed#gmail.com@spamgourmet.com>;
Return-Path:     <+livejournal+thecyclops+8861f3a428.removed#gmail.com@spamgourmet.com>
Subject:     gmail test (livejournal: message 1 of 20)
To:     livejournal.20.thecyclops@spamgourmet.com

OK, thanks. The problem was that the way they display their email address:

From: webmaster@livejournal.com (LiveJournal.com)

did not work well with reply address masking. I went ahead and rewrote the method that was parsing out addresses, because it kind of sucked anyway, and things appear to be working now.

Let me add that this way of writing a From field breaks all RFCs. They should have written:
"LiveJournal.com" <webmaster@livejournal.com>
in order to be SMTP-compatible.

I'm sure they break other mail services too.

Dunno it might break current rfc's. But if you see usenet postings back from 17 years a go, you'll see that majority of addresses are in that format. So it's very familiar format for everyone for sure.

In 1998 most of messages still got that old format. In 2000 most are using new format. Dunno if rfc have been changed. But it can't break "all the rfc's".