Re: James 3.4.0 do not receive e-mail at all

Hi David,

unfortunately yours and Ahmets descriptions weren't very clear, so I 
just repeated a list of what I had done many years ago (I used a 
different solution, but as it got stuck in some never-fixed issue I 
looked for another and that's I got into James) as I also struggled to 
get it up and running. I also got a lot of help from the devs so I'm 
able to also provide some now.
May Ahmet also respond to this, but may I ask: What exactly is the issue 
you're dealing with? Is it that you can't receive mails from others send 
to your James, or sending mails from your James to others, or maybe both?
Receive mails from other services is usual very easy: Your domain 
requires at least one MX record pointing to at least an A record and the 
server James is running on has to have port 25 on TCP open to the public 
so it can actually receive mails. For this to work on a unix systems 
it's required to shutdown any other mail service, as at least some basic 
always has to run - that's just how unix work. The easiest way is to use 
sendmail as "nullclient" (the sendmail doc can give some advice) so the 
system still can rely on local sendmail and you can run your James (this 
requires some manual tweak in sendmails main startup script - this 
differs a bit from one distribution to the next). After that you only 
have to start up James (after setting all the required configs), add 
your domain and the user accounts and all should be good to go for at 
least receiving e-mails from others.
Making it work to also successfully send mails to others without getting 
them marked as spam is a bit more complicated as it requires additional 
things to met before fully working. In the end this comes down to have 
James running on a server which IP is static and not in a "dial-up 
block" (dial-up IP ranges are all those known to be assigned to ISPs for 
use for their customers - if you try to send mails from such an IP it 
almost always get's blocked as spam). In addition it helps to setup at 
least an SPF record wich explicit allows your mail server to send mails 
for your domain.
When you all got this up it either works or you get error logs wich help 
to resolve the issue (often it's a DNS issue, but sometimes it's just a 
fault on the other end).

Just right us up (also you Ahmet - would like to hear from you too) with 
your issues and anyone on this list able to help surely will do so. I 
guess we can get you both up and running before weekend.

Hope it helps you both and may you find some time to have a look at it.

Matt

Am 04.03.2020 um 09:19 schrieb [email protected]:
> hi Matt
>
> Not got to grips with it yet. I definitely had James 3.4.0 running at some point and spooling mail (yet never delivering it). I briefly looked at it again yesterday and didn't even get it to run!
>
> I'll backtrack over what I did myself a couple of months ago and then look at your suggestions and report back.
>
> Thanks for your interest
>
> --
> David Matthews
> [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>