On 2012-09-25, Jeremy Kitchen <kitc...@kitchen.io> wrote:
> On Tue, Sep 25, 2012 at 02:25:22PM +0000, Grant Edwards wrote:
>> On 2012-09-25, Jamie Paul Griffin <ja...@kode5.net> wrote:
>> > [ Ian Barton wrote on Tue 25.Sep'12 at  7:04:39 +0100 ]
>> >
>> >> On 24/09/12 18:52, Jeremy Kitchen wrote:
>> >  
>> >> Thanks for the information. I'll go  back to using the smtp server on my 
>> >> Linode box. The reason I switched was I was having problems delivering 
>> >> to some, but not all, bt.com addresses. There were no errors in my 
>> >> mail.log, but some recipients weren't receiving email. Like you I want 
>> >> to be able to set my From and envelope address without having to perform 
>> >> silly tricks.
>> >
>> > Has your ISP provided a static IP for you? I have that set up with
>> > mine, and just use my local MTA to send messages rather than relaying
>> > them through other smtp servers. If your using a dynamic IP at home
>> > then this could explain why some bt.com addesses have not delivered,
>> > or rather been seen as spam. 
>
> I'd considered doing that, but I'd *already* run into issues with
> sending emails from my local MTA at home, so I just pushed them up to my
> server and called it a day.
>
> I'm really tempted to just go back to hosting my own email,

I think the only way that's going to work these days is to

 1) Get a static IP address that's not in a block used for residential
    customers.

 2) Register a domain and setup appropriate MX records for that
    domain.

Back when I was sending mail directly, I wasn't handling/hosting
inbound mail (I let my ISP do that), but I did have outbound mail
queueing and was sending outbound mail directly to destinations.
    
> but I don't feel like trudging through tons of spam every day.

And there's that.

>> Som recipients not only require a static address, but they require an
>> MX record for the envelope from that matches up with the static address.
>
> that would break nearly every major email provider on the internet. If
> this happens, they're throwing away their own mail.
>
>> Even with a static IP address and an MX record, I still wasn't able to
>> send mail directly to some recipients because the MX record for the
>> domain in the message From: header didn't match up with the static IP.
>
> It's more likely that you were filtered because you're in a residential
> IP block, not just a static IP.

Yep, there were some servers who's error messages seemed to indicate
that they rejected all mail from residential DSL static address
blocks.  There's not much you can do about that.

There also were occasional error messages that complained about
mismatches between MX records, evelope from, message from, message
return-path.

In any case, it became apparent that sending e-mail directly from a
residential IP address (especially when you didn't want to use that IP
for hosting incoming mail) just wasn't going to be practical any
longer.  I had done it without problems for years, but rejections (or
worse, emails that just disappeared into the bit bucket) became
increasingly common.

-- 
Grant Edwards               grant.b.edwards        Yow! Of course, you
                                  at               UNDERSTAND about the PLAIDS
                              gmail.com            in the SPIN CYCLE --

Reply via email to