From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: gmail smtp overwrites the sender
Date: Thu, 15 Mar 2012 10:51:10 -0400 [thread overview]
Message-ID: <CA+czFiBU-OURmvA=A2OwTJPzfjFUdRnypKswx28Lu1F+orx-0A@mail.gmail.com> (raw)
In-Reply-To: <jjsucn$gvm$1@dough.gmane.org>
On Thu, Mar 15, 2012 at 10:29 AM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2012-03-14, Mick <michaelkintzios@gmail.com> wrote:
>> On Monday 12 Mar 2012 18:34:37 Grant Edwards wrote:
>>> On 2012-03-12, Stroller <stroller@stellar.eclipse.co.uk> wrote:
>>>
>>>> No, I simply meant that if you use Postfix you don't have to use
>>>> anyone else's SMTP server,
>>>
>>> If you've got a static IP address, a domain, an MX record, and
>>> whatever other requirements a lot of sites are now placing upon
>>> senders of mail.
>>>
>>> I used to use my own SMTP server, 10 years ago it worked fine. More
>>> recently, too many destinations wouldn't accept mail from me -- so I
>>> had to start using mail relays.
>>
>> Perhaps your mail address was blacklisted? Many ISPs IP address
>> blocks are blacklisted these days.
>
> I know that was sometimes the case from the rejection message sent by
> the destination SMTP server. Even though I had a static IP address
> and an valid MX entry for the sending machine's hostname, some sites
> wouldn't accept mail because my static IP addres was in a block used
> for DSL customers (of which I was one).
Yeah, I can't even send email to my gmail account from my Comcast
public IPv4 address.
>
>> Also some ISPs are blocking ports (like 25 and 2525) to minimise spam
>> sent out of compromised boxen. They would typically allow you to
>> relay through their mailservers though.
>
> I've never run into that, but I know people who have.
>
> In either case, I wouldn't advise anybody to try using their own SMTP
> server to deliver mail directly to destinations unless they have their
> own domain, their own IP block, and the time+skills require to fight
> with the problems. Anybody with the requisite resources and skills
> probably wouldn't be asking questions here about how to use Gmail's
> SMTP server.
My workaround involved relaying my network's outgoing email through my
VPS node's email server. (My VPS provider, prgmr.com, doesn't seem to
be on any blocklists, etc.)
--
:wq
next prev parent reply other threads:[~2012-03-15 14:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 20:56 [gentoo-user] gmail smtp overwrites the sender András Csányi
2012-03-11 12:49 ` Stroller
2012-03-11 13:22 ` András Csányi
2012-03-12 14:59 ` felix
2012-03-12 16:52 ` Stroller
2012-03-12 18:34 ` [gentoo-user] " Grant Edwards
2012-03-14 23:02 ` Mick
2012-03-15 14:29 ` Grant Edwards
2012-03-15 14:51 ` Michael Mol [this message]
2012-03-15 19:54 ` Mick
2012-03-15 20:07 ` Michael Mol
2012-03-15 21:13 ` Mick
2012-03-15 21:20 ` Michael Mol
2012-03-11 13:21 ` Nikos Chantziaras
2012-03-11 14:41 ` Grant Edwards
2012-03-11 14:59 ` Nikos Chantziaras
2012-03-11 14:49 ` [gentoo-user] " Pandu Poluan
2012-03-11 15:00 ` [gentoo-user] " Nikos Chantziaras
2012-03-11 15:18 ` Pandu Poluan
2012-03-11 16:07 ` Nikos Chantziaras
2012-03-11 16:14 ` Grant Edwards
2012-03-11 16:45 ` Nikos Chantziaras
2012-03-11 17:54 ` Grant Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+czFiBU-OURmvA=A2OwTJPzfjFUdRnypKswx28Lu1F+orx-0A@mail.gmail.com' \
--to=mikemol@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox