Hi,
the problem is solved and of course it wasn't me :)
after a few debugging sessions with christoph Viethen is it offical I
behave like I should or at least my mx. Turns out the other side had a
firewall that basically blocked the traffic to my server (yeah even
whitelisting me in the
Hi Craig,
yeah my server is fine in general but maybe the other adin just has some
sort of own ways to blacklist so I might be on there list. I'll check
this too but it seems it could be a routing problem to since the other
mx sometimes talk and sometimes not (checked from other location to
Hi Markus,
On 2016-04-06 Wed 09:29 AM |, Markus Rosjat wrote:
> Okay with some help from Christoph Viethen I did some testing and connfirmed
> a few things
>
> - sendmail -bt gave me the right order of the mx to talk to
> - I couldn't connect to the server with nc
> - I couldn't ping the server
Okay with some help from Christoph Viethen I did some testing and
connfirmed a few things
- sendmail -bt gave me the right order of the mx to talk to
- I couldn't connect to the server with nc
- I couldn't ping the server
- nslookup gave me the correct IP to the server
what really confuses me,
> so the real smtp has the lower number but higher priority but like I said my
> sendmail always ends up with shit.example.not.nz.
What does "sendmail always ends up with shit.example.not.nz." mean?
Of course sendmail tries the secondary MX after trying the main MX.
Still no real
Hi Markus,
On 2016-04-05 Tue 16:39 PM |, Markus Rosjat wrote:
>
> no the real setup is the other way arround
>
5 smtp.example.not.nz. # <<--- real server
10 shit.example.not.nz. # <<--- always defering server
Their setup is fine then, a classic highlisting arrangement.
>
> so the real smtp
hi there,
no the real setup is the other way arround
1 shit.example.not.nz. 10 # <<--- always defering server
2 smtp.example.not.nz. 5 # <<--- real server
so the real smtp has the lower number but higher priority but like I
said my sendmail always ends up with shit.example.not.nz.
On Tue, Apr 05, 2016, Craig Skinner wrote:
> 1 shit.example.not.nz. # <<--- always defering server
> 2 smtp.example.not.nz. # <<--- real server
> Your server connects to 'shit.example.not.nz', which defers the mail,
> telling your server to try again later. So,. your server tries again
>
Hi Markus,
On 2016-04-05 Tue 14:22 PM |, Markus Rosjat wrote:
>
> yeah my server does retries but always ends up on the mailserver with the
> lower priority :(
>
That is the correct behaviour.
Without the domain name, I'm guessing with English words what you mean;-
Pretending their broken
Hi peter,
yeah my server does retries but always ends up on the mailserver with
the lower priority :(
Am 05.04.2016 um 12:44 schrieb Peter N. M. Hansteen:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/05/16 11:55, Markus Rosjat wrote:
I have a mail to deliver to a domain that has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/05/16 11:55, Markus Rosjat wrote:
> I have a mail to deliver to a domain that has two mx record but the
> 2nd record isn't really a mx (so I got told but the need to keep
> that for some reasons).
I would question their competence right
Hi there,
this more a mail about confirming the problem isn't on my site here.
So that's the case:
I have a mail to deliver to a domain that has two mx record but the 2nd
record isn't really a mx (so I got told but the need to keep that for
some reasons). So far so good the priority on the
12 matches
Mail list logo
