Re: Outgoing email blocked
- From: "urska" <www.>
- Date: Wed, 4 Oct 2006 14:18:04 +0200
"N. Miller" <anonymous@xxxxxxxxxxxxxxxxx> je napisal v sporocilo
news:ky72un75c4xc.dlg@xxxxxxxxxxxxxxxxx ...
On Sat, 30 Sep 2006 22:44:12 +0100, Bill Ridgeway wrote:
Sorry but I've lost you.
The situation is my Client has an account with BT which blocks email
being
sent out using his email address fred@xxxxxxxxxxxxxxxxx AND so that
recipients see emails as having been received from
fred@xxxxxxxxxxxxxxxxx?
The options seems to be -
1. Do nothing - having a discrete domain is not a good option
2. Change ISP - not a viable option
3. Subscribe to a relay server - will recipients see the email as coming
from fred@xxxxxxxxxxxxxxxxx
4. Any other way?
No.3 may be a runner but only if its satisfies both element of the
requirement.
No.4 who knows what anyone may come up with
Is that summary more -or-less correct?
See my post about consulting with your client's hosting provider. If the
client's hosting provider will allow connection to their SMTP server
through another port than port 25, you just have to configure MSOE for
that other port, and SSL, if requires. Alas, MSOE will only perform
STARTTLS (aka, "TLS") on port 25. Don't confuse SSL and TLS; they _are_
different.
If not, consider the following examples:
Yahoo! Mail 'smtp.mail.yahoo.com:587':
| Return-Path: <%User_ID%@xxxxxxxxx>
| Received: from rly-xb06.mx.aol.com (rly-xb06.mail.aol.com
[172.20.64.52])
| by air-xb01.mail.aol.com (v112_r1.5) with ESMTP id
MAILINXB14-6cb451f465f25d;
| Sun, 01 Oct 2006 00:39:06 -0400
| Received: from smtp104.plus.mail.mud.yahoo.com
(smtp104.plus.mail.mud.yahoo.com [68.142.206.237])
| by rly-xb06.mx.aol.com (v112_r1.5) with ESMTP id
MAILRELAYINXB69-6cb451f465f25d;
| Sun, 01 Oct 2006 00:38:56 -0400
| Received: (qmail 90979 invoked from network); 1 Oct 2006 04:38:55 -0000
| Received: from unknown (HELO ?192.168.102.31?)
(hard2findanamenotused@xxxxxxxxxxxx with login)
| by smtp104.plus.mail.mud.yahoo.com with SMTP; 1 Oct 2006
04:38:54 -0000
| From: "N. Miller" <%User_ID%@xxxxxxxxx>
| Organization: Yahoo! Mail
| To: %User_ID%@xxxxxxx
| Date: Sat, 30 Sep 2006 21:38:45 -0700
| MIME-Version: 1.0
| Subject: [TEST] Using the Yahoo! Mail servers
My Japanese is weak, and I didn't have time to work out how to configure
'smtp.mail.yahoo.co.jp' to accept non-domain email. It can be done, and
should be possible with 'smtp.mail.yahoo.co.uk' as well. It doesn't show
here because I use a Yahoo! Public Profile ID (hard2findanamenotused)
for the log in. With just the email address, it would have shown,
"(%User_ID%@xxxxxxxxx@69.227.43.68 with login)". But you don't see that
email address as the Return-Path, or the sender; those are "@lycos.com"
email addresses.
With 'smtp.mail.yahoo.co.uk', I imagine that your client will have to
configure his email address as an authorized sender. The Yahoo! UK
account should still offer free access to the SMTP server for just
subscribing to Yahoo! Delivers; that is how I got access to
'smtp.mail.yahoo.co.jp'. Port 587 must be used when port 25 is blocked.
GMail 'smtp.gmail.com:587':
| Return-Path: <%User_ID%@xxxxxxxxx>
| Received: from rly-yg04.mx.aol.com (rly-yg04.mail.aol.com
[172.18.180.82])
| by air-yg03.mail.aol.com (v112_r1.5) with ESMTP id
MAILINYG31-289451f47172b4;
| Sun, 01 Oct 2006 00:42:02 -0400
| Received: from wx-out-0506.google.com (wx-out-0506.google.com
[66.249.82.232])
| by rly-yg04.mx.aol.com (v112_r1.5) with ESMTP id
MAILRELAYINYG49-289451f47172b4;
| Sun, 01 Oct 2006 00:41:59 -0400
| Received: by wx-out-0506.google.com with SMTP id s16so1322389wxc
| for <%User_ID%@xxxxxxx>; Sat, 30 Sep 2006 21:41:59 -0700 (PDT)
| DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
| s=beta; d=gmail.com;
|
h=received:from:organization:to:date:mime-version:subject:message-id:priority:x-mailer:content-type:content-transfer-encoding:content-description:sender;
|
b=b4+OsS25QLhyEF8kDtb3XysMWZuGTLgvBSjwT+17CN2s80vvXKn54V5ZdJYmihMJZMU/5tQ5vqtVLvLEJfinPD7R1h8nbp1wZm8J5vNG4TEKxaayqv5Mk2z2Fl4cvAR0TdUrlVthnfa9e1iT0jhVd8wg6a2tmYaZiP4GzxgFseE=
| Received: by 10.70.40.1 with SMTP id n1mr3926152wxn;
| Sat, 30 Sep 2006 21:41:59 -0700 (PDT)
| Received: from gmail.com ( [69.227.43.68])
| by mx.gmail.com with ESMTP id 28sm292375wrl.2006.09.30.21.41.56;
| Sat, 30 Sep 2006 21:41:58 -0700 (PDT)
| From: "N. Miller" <%User_ID%@xxxxxxxxxx>
| Organization: Google Mail System
| To: %User_ID%@xxxxxxx
| Date: Sat, 30 Sep 2006 21:41:46 -0700
| MIME-Version: 1.0
| Subject: [TEST] Using the GMail servers.
Although the Return-Path is the GMail account email address, all the
recipient sees for the sender is the "@aosake.net" email address; as
well, that is the email address to which a reply will be sent.
With MSOE unable to use STARTTLS (TLS) on port 587, your client would
have to configure MSOE to use port 465 with SSL. As with Yahoo! Japan,
GMail also requires configuring a non-GMail domain as an authorized
sender before trying to use it so.
GMail is free, but requires an invitation.
Frankly, getting alternate port access through the hosting service would
be a superior solution. Your client is paying for the service, the
provider should offer the service.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum
.
- Follow-Ups:
- Re: Outgoing email blocked
- From: Mary Taylor
- Re: Outgoing email blocked
- From: WILLI
- Re: Outgoing email blocked
- References:
- Outgoing email blocked
- From: Bill Ridgeway
- Re: Outgoing email blocked
- From: Bill Ridgeway
- Re: Outgoing email blocked
- From: Frank Saunders, MS-MVP OE/WM
- Re: Outgoing email blocked
- From: Bill Ridgeway
- Re: Outgoing email blocked
- From: N. Miller
- Outgoing email blocked
- Prev by Date: Re: Moving OE to a new computer
- Next by Date: Re: No longer possible to manually move email msg. to a new Folder
- Previous by thread: Re: Outgoing email blocked
- Next by thread: Re: Outgoing email blocked
- Index(es):
Relevant Pages
|
