Cannot send email from my SG addresses?

Use this forum to get help.

Cannot send email from my SG addresses?

Postby emoji » Wed Oct 15, 2014 10:28 pm

Seems like every time I try to send an email from one of my Spam Gourmet addresses I get a mail delivery daemon message (from `Mail Delivery Subsystem <mailer-daemon@googlemail.com>`) back saying that the delivery failed.

Specifically, the message says:

Google tried to deliver your message, but it was rejected by the server for the recipient domain ob.0sg.net by ob.0sg.net. [216.75.62.102].

The error that the other server returned was:
550 restricted characters in address


Code: Select all
----- Original message -----

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=OaQvq0W/Kvn7qQKJMsgzsXqKyFuaYbuunqqnpRt3Yms=;
        b=mBBgjQ9b6b+M2jKJZgBnPCWs0Z4VSqZdMfBooM4oGE8pm29EyxIKsfTqwhWnr1JDpa
         IQf82rerrghS4Ax1rKgfTet/RKvA8qUxJoqskY025suaBQJ3J5K9G8pMqsnXiibV36MN
         FWlHZ3ZqRDK442cDts6ccV+mcW473ta7rZHTomoDhjxFOwNoKHm0DDy8ZygSsMFBnQy7
         ybrueQy5JTS56ThKGqYwPM+xq3vX79cvG0mPECOnT7mIFqGAvl+y8t0eGUEBi5/x5y+E
         B18ims8tPw8IkrLQLE/XfjWakd7/yx4vSOAdB4a6tYo2WD3SXAHNVquBVpBi2J3niSDj
         dL6g==
X-Received: by 10.180.205.171 with SMTP id lh11mr8229320wic.66.1413325180088;
 Tue, 14 Oct 2014 15:19:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.120.102 with HTTP; Tue, 14 Oct 2014 15:18:59 -0700 (PDT)
From: <SNIP>
Date: Tue, 14 Oct 2014 23:18:59 +0100
Message-ID: <SNIP>
Subject: <SNIP>
To: <SNIP>
Content-Type: multipart/alternative; boundary=001a11c382704fb3f3050569697a


Is Spam Gourmet having issues, or is Google blocking Spam Gourmet, or is the recipient blocking Spam Gourmet? What's going on?
emoji
 
Posts: 1
Joined: Wed Oct 15, 2014 10:18 pm

Re: Cannot send email from my SG addresses?

Postby josh » Tue Oct 21, 2014 12:56 am

probably a spamgourmet problem - we maybe went overboard on special character restrictions. Were there any special characters in the address?
josh
 
Posts: 1357
Joined: Fri Aug 29, 2003 2:28 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Tue Jul 26, 2016 5:25 pm

I have just hit the same problem. I am sending (or trying to send) an email from one of my disposable addresses, and the email is being rejected by ob.0sg.net:

Google tried to deliver your message, but it was rejected by the server for the recipient domain ob.0sg.net by ob.0sg.net. [216.75.62.102].

The error that the other server returned was:
550 restricted characters in address


Which is a little odd, since ob.0sg.net is a (the?) spamgourmet server.

Even odder - I have used the address without a problem in the past, many times.

And odder still - the last time I successfully used it was Feb 2nd, 2015. Which is some months after emoji's original post above from Oct 14th, 2014.

As to what the character is - it looks like it's a hash #. But a hash created by spamgourmet, not in the original address.

The email address is <snipped_this_bit>info#petplan.com.au@ob.0sg.net, but the delivery failure report lists this as <snipped_this_bit>info%23petplan.com.au@ob.0sg.net (where <snipped_this_bit> is my unique code bit that I'm not posting here for obvious reasons).

By the by - or maybe not - like the original poster, I am also using gmail. And the disposable address I'm using is at antichef.net.

And painfully for me - what I'm trying to send is a cancellation form to my so-called "pet insurance" company who I have realised far too late are basically professional extortionists. And won't accept an email unless it comes from my official address. Which is of course a spamgourmet one.

Which is my problem not yours, 'cos I know you're unsupported, and I think this is the first problem I've encountered in my fifteen or sixteen years of use (can't remember, I'm middle-aged now). So fingers crossed you're still out there reading this somewhere.

Also - if you have a dog and live in Australia, don't bother with pet insurance. Trust me. Or if you don't ("trust me" that is, not "have a dog and live in Australia"), pm me and I'll happily explain why. At length.
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm

Re: Cannot send email from my SG addresses?

Postby josh » Wed Jul 27, 2016 4:35 am

hmmm... I'm looking through the logs and seeing tons of messages go through ob.0sg.net with the # sign.

could it have been a different intermediary server?
josh
 
Posts: 1357
Joined: Fri Aug 29, 2003 2:28 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Wed Jul 27, 2016 11:30 am

Thank you Josh, I didn't expect such a speedy reply.

Playing a bit further and looking through some old emails, I have realised that all messages sent from a spamgourmet disposable address include a # sign, as that replaces the @ sign in the addressee's email address. At least for me.

Sent a few more random emails from other disposable addresses to a couple of my other email addresses, and they all bounce with exactly the same delivery failure report.

Regarding intermediary servers - all previous messages I have sent from a spamgourmet disposable address would I think have been sent from Australia or New Zealand. I'm currently in France. I'd be interested to know where emoji's physical location was if she's still out there.

I'm not entirely sure how to check for intermediary servers though?

This is the header for the original message, as returned (identifying bits replaced with ***):

----- Original message -----

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:from:date:message-id:subject:to:cc;
bh=jiD3f740cbnfWAFqJOqVBkyLivlMAQN3bzRtwCrEfIo=;
b=Pcu8knSsvds8Jzyfee7hUOROm5uohU6IkcFf3QA3QAUKpakVImGDE1hFYA3tJfgFjW
4as8vJyVvq7AdjfMxkJgugHPnKQBQ0sdBczDjxdA0HzEU/7uHukieXV5SrSf85BntrNn
nUqbB9H5QwIqtiXuhxJmpaCvcC1qlBG3rsamMJptWz7hGoLQeqavYLIxMutR/b9X9Thx
Dhgj0RoooTM48NP+09bktB34zrD+zVe6mdG4hZPo9j6D5JyAKBLW+j/kZBAUWhKjdMbE
CK5Ggu6goLCkX6b099azB2TnssOcRgu9byh+rJot/PRkpRd/UF622chYwLJkW+P1hMLg
KR+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc;
bh=jiD3f740cbnfWAFqJOqVBkyLivlMAQN3bzRtwCrEfIo=;
b=YIoZ4Rh0kzPvyJToYJCUmQIjTVA7URzWczG+KZNtqaYWc+ojLhLGuiXRk35x3qgFYw
tEBk/hhv13ZPp12Ijhsvf2Hf2OiV52NjeSrHLoYL3ALZ/siYyEJWpZerqw5QXYSBsW2n
CIM9JM07baE44l0Xj+RqG13xKaTuA3CyNRYX5V10KbvMSaqsZDeDSFCaByOF5fw7RdE+
C/3YqU049A32QJ4KNczRf+1BdWKdv9PDw6/IfR0YIULx62YpglyvlfmNMClDM7RuNfkQ
d+2hrtyTsmJ543DaVWecJPkLVSgWgvWxhoujO2r3dhdBnCTCLwQdysITBMzI5pV+t6D/
B3DA==
X-Gm-Message-State: ALyK8tJtTYwskHei9SyciFKDIBxg09LocXD+ShPw6bJ7YNB8/d+SoGXyLQ9LLpIIkXkFsKV0OY8PgITFr5Yo3w==
X-Received: by 10.36.74.137 with SMTP id k131mr96716707itb.85.1469551447414;
Tue, 26 Jul 2016 09:44:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.36.91.20 with HTTP; Tue, 26 Jul 2016 09:44:06 -0700 (PDT)
From: *** <***@gmail.com>
Date: Tue, 26 Jul 2016 18:44:06 +0200
Message-ID: <CACVRHkAx24au5Rs9qOXbhzDGMPaUonX6rwbHLOxFG-dxixYi0w@mail.gmail.com>
Subject: ***
To: ***info%23petplan.com.au@ob.0sg.net
Content-Type: multipart/mixed; boundary=001a114049e20134bb05388c9cd4


And this is the header for the delivery failure report, in case there's anything useful in there:

Delivered-To: ***@gmail.com
Received: by 10.36.9.21 with SMTP id 21csp1699765itm;
Tue, 26 Jul 2016 09:44:10 -0700 (PDT)
X-Received: by 10.36.43.131 with SMTP id h125mr27544753ita.89.1469551450037;
Tue, 26 Jul 2016 09:44:10 -0700 (PDT)
Return-Path: <>
Received: from mail-it0-f70.google.com (mail-it0-f70.google.com. [209.85.214.70])
by mx.google.com with ESMTPS id x68si19905702itg.11.2016.07.26.09.44.10
for <***@gmail.com>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 26 Jul 2016 09:44:10 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of postmaster@mail-it0-f70.google.com designates 209.85.214.70 as permitted sender) client-ip=209.85.214.70;
Authentication-Results: mx.google.com;
dkim=pass header.i=@googlemail.com;
spf=pass (google.com: best guess record for domain of postmaster@mail-it0-f70.google.com designates 209.85.214.70 as permitted sender) smtp.helo=mail-it0-f70.google.com;
dmarc=pass (p=QUARANTINE dis=NONE) header.from=googlemail.com
Received: by mail-it0-f70.google.com with SMTP id u186so822ita.0
for <***@gmail.com>; Tue, 26 Jul 2016 09:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=20120113;
h=mime-version:from:to:subject:message-id:date;
bh=DxeFD+BdBr9cozDg7U3ZooQihMCySy/ufaP4li84NCk=;
b=b1XuJe74rKSn4i3FAAkVBiLIwJRB1lnn8r8rJSo83lbXi8afaCcNI+1JYglfAldYpx
0URWKKVQ/vK8UZ0DJ8dNgh5N5YaufBov9v7dMx+z9ufKkGwKpDviZ9cxcHeHvBG8SWuj
4FMQzlnm/ISErUiorf5SmIGXqZcu6JaYC3JuygJUOKHd3pnA920wj5Dkqfd8WMsh/o0d
SVNtO0WPKS3UzTLxcXP15Y+o5oc+f7J4sUIKdfoA+tx8WZPbOTNQ5ANuA1TtUEXCGT2n
R+y0TmpwbXX74pLNEZs/y+AriZOVxmIOdceFxITiZFFSUGLPrGovoF48CHTgeikBw7oq
PyBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:from:to:subject:message-id:date;
bh=DxeFD+BdBr9cozDg7U3ZooQihMCySy/ufaP4li84NCk=;
b=VhNlktvY2cJh6tdIdBStCMnqbsWZPTDcP/2lcRdAFP54chul6jl0nsr2ll7mosjgPA
SwWl11NTcuGz6olyNjEsVuQuxlWfQDxY9LSXdt1c5yuB/1+K/AeH4vaDz0eGO3lcmnrO
pz+sJQ0um+21KilW6crL466nqtAHkYd8hLDuDlJaTj4RSV4KgySfVDFMTz9+ueONQ5xl
8uYyAEaMxnGSULLryZisOvA9RfH6jm3y/eztFhUcDfHwGZz44TSZowUJhaQTg8u3/JFp
TuGOVH0yoYaXWB9iQBgV8S4MW7wbLOvUtUdNzDmOV/0l+hvQGdrODvCf/f4FSHq5i74e
hyhg==
X-Gm-Message-State: ALyK8tKZGwJnKRP1bXvncpiibShUCVHi72zYHN6I8s1dxJixYp1U65aRjaXlPb3MXurbVmgXflwoIcfivjs3+md3jTtNk2QiVA==
X-Received: by 10.36.74.137 with SMTP id k131mr96716804itb.85.1469551448602;
Tue, 26 Jul 2016 09:44:08 -0700 (PDT)
MIME-Version: 1.0
Return-Path: <>
Received: by 10.36.74.137 with SMTP id k131mr101919807itb.85; Tue, 26 Jul 2016
09:44:08 -0700 (PDT)
From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
To: ***@gmail.com
Subject: Delivery Status Notification (Failure)
X-Failed-Recipients: ***info%23petplan.com.au@ob.0sg.net
Message-ID: <001a114049e212b51605388c9ce6@google.com>
Date: Tue, 26 Jul 2016 16:44:08 +0000
Content-Type: text/plain; charset=UTF-8


My next steps:

1. I have a VPN client on here which I've used all of once, so I'm going to figure out how it works again and try a test from Australia using that and see if it makes any difference.

2. If not, I'll sign up for a yahoo or hotmail account and try sending a test from there (I have a bunch of email addresses, but they're all gmail).
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Wed Jul 27, 2016 12:06 pm

Okay - (1) worked!

More specifically: I connected through an Australian OpenVPN server, then from gmail sent the same email from the same spamgourmet disposable email address to the same addressee, and it went through fine. No delivery failure report.

So yes, it looks like the issue is with an intermediary server. I'd guess two likely options:

- my ISP here in France is Budget Telecom, so something to do with them
- something to do with the intermediary server used by Google to route gmail messages from France

However, I have no idea how to investigate further.
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Wed Jul 27, 2016 12:50 pm

Update: I did have an idea after all.

Did some tests with gmail, yahoo, with and without VPN. Without going in to all the details, a summary of the results:

- whatever intermediary server gmail is using here in France is converting the # to %23
- whatever intermediary server gmail is using in Australia does not convert the # to %23, but lets it go through as is
- spamgourmet has no problem with a # in an email address, as spamgourmet uses # in all addresses it generates for users to send an email from a spamgourmet address
- but spamgourmet does have a problem with % in an email address. I believe spamgourmet rejects any email with % in the email address, as a restricted character
- so if the email client or intermediary server or whatever converts the # to %23 in an email address, spamgourmet's server will reject the email

How's that?
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm

Re: Cannot send email from my SG addresses?

Postby josh » Wed Jul 27, 2016 12:51 pm

Looks like there's a % involved - in one of the instances above, it looks to be where the # sign originally was.

I believe our server would indeed reject an address containing a % sign - I wonder if an intermediate server in the French route (the "French connection" ha) replaced the # with a %?

Josh


edit --- I posted at about the same time as you, and it sounds like you're ahead of me. Yes - it does look like some URL encoding is going on. Why would someone do that to an email address in a SMTP route?
josh
 
Posts: 1357
Joined: Fri Aug 29, 2003 2:28 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Wed Jul 27, 2016 1:00 pm

Dammit, I was feeling very pleased with myself but you were already there.

We could ask google. But I don't fancy our chances much.

edit: "the French Connection" - very good
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Tue Nov 29, 2016 12:46 am

Update: I've just tried to send another email from a different SG address, from my gmail account, now back in Australia with gmail using intermediary servers in Australia.

And unfortunately it looks like whatever was implemented on the French gmail intermediary server to convert the # to %23 has now been implemented on the Australian gmail intermediary server.

I'll post the delivery failure report below.

I'm pretty sure this is the first email I've tied to send through SG since the message discussed above in July.

Unfortunately I don't think I have the test messages I sent via Australia through my VPN last time round so I can't check if it is the same intermediary server or a different one.

Aside from my immediate difficulties, my concern is that this is something gmail could be implementing globally so would break SG for gmail users everywhere.
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm

Re: Cannot send email from my SG addresses?

Postby lupiac » Tue Nov 29, 2016 12:49 am

Here's the mail header, identifying bits replaced with ***:

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc;
bh=pVAySChe3AilY0Ov1b0Xa9PGSLBHjntBCZh7NgK12Ts=;
b=yenGgZbq6aXeJfKZdmV98YWPXicNtCMdkARaRgDyD8HK+ukZdNFdRA53b2xZVoIrrM
xLMboKSgAMfWgNGZgk/27fcm27dEMshZ/Yzq5PsuQZZUo2J7P4ORBr1M3H6ULAPx3z5U
hyYDcPfqYtzcxCWtQLFMs3dxgAFtw/JKiVmLtmzoR8fgrQBMysl54lLl5qFMBoST5zuZ
ro6ZB3aFkYyLNRDSPgTA2DAFOBfpXZXsl3StzRAgAviswpN8aw13r8/livXlfG9RMc4G
7vABEuDdJMSYODkUAX8GS6j4ZznAKY74NTvvcZJTuuKaziQhQZvVLcGQ3davDQ2SW8n2
5xlQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=pVAySChe3AilY0Ov1b0Xa9PGSLBHjntBCZh7NgK12Ts=;
b=F1XMTQ42I2QjIlqTNay0hCO/UnXjjCbHD/s9YUNl+DNGwIcePRHE8FdqSTvg2HOtWz
3DsC1TaYNsYN1eStAmQPNf0LvGwwvgDENxbiLr3OH1T1ItaS9ryw4U/w7Jz4D0y+GQcM
Gnu9w30L7IkexwVB1T8HbGanTzbCeQi8wVP+ONZgRzMj9+Vq6ATNDJBBR+zKN2/atzKh
dgZLAIPV01sBy2oJXqaNx853eVJgwsiTWAKDkeQa1UU3yqqOKGu1dDje0ZahGXeAN0Qp
vWvql4Rb4h5VRLh6LhoWfNnY1Tl6GRD+GFhc0IsUVWudpeEojxhTST9Zao2pxApAZk7h
xDwA==
X-Gm-Message-State: AKaTC00hPycJ4vpJGlDZQx7/RrwPn62Sz1tJKAVHbyyTq/VeGIVzNOEpQPg6CY4jKJQ9WLtljrqWpNTY+58Ceg==
X-Received: by 10.107.30.69 with SMTP id e66mr19663137ioe.62.1480379102312;
Mon, 28 Nov 2016 16:25:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.36.206.129 with HTTP; Mon, 28 Nov 2016 16:25:01 -0800 (PST)
In-Reply-To: <CACVRHkAzCXAznQRtkda-h-EL-kgAAZ6RLD2jPXW=Dk_Oy-9Z+g@mail.gmail.com>
References: <E1bwZkW-004ALv-Lt@webcloud34.au.syrahost.com> <CACVRHkAzCXAznQRtkda-h-EL-kgAAZ6RLD2jPXW=Dk_Oy-9Z+g@mail.gmail.com>
From: ***
Date: Tue, 29 Nov 2016 11:25:01 +1100
Message-ID: <CACVRHkBYO9wYeY7Z6oA0+eE3d3RtWjULT8NRMcYp69-tNarCNQ@mail.gmail.com>
Subject: Re: Order #1729 (rentatent: message 3 of 20) (trusted: ***)
To: ***info%23rentatent.com.au@ob.0sg.net
Cc: ***
Content-Type: multipart/alternative; boundary=001a1140f33a86c5210542659ec1
lupiac
 
Posts: 7
Joined: Tue Jul 26, 2016 4:57 pm


Return to Support / Hilfe / ayuda / ondersteuning / ...

Who is online

Users browsing this forum: No registered users and 234 guests

cron