cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED
  • The questioner has marked this post as solved.
  • Closed

emails from domain eergeneve.ch don't come to @bluewin.ch

Highlighted
Novice
1 of 6

Hello,

I have a problem: emails from domain eergeneve.ch don't come to @bluewin.ch. Mail server bluewin doesn't receive our emails.

Could somebody help resolve us this problem?

 

Here is headers with error description:

    SMTP error from remote mail server after end of data:
    host mxbw.bluewin.ch [195.186.99.50]: 554 FROM:
    <eer> (46.14.162.42) Not spooled, transaction failed.

Thanks!

MOST HELPFUL ANSWER

Accepted Solutions
Expert
4 of 6

Hi

 

First thing I recognise is that you do not use the same mailserver (Diffrent IP Address).

However, that shouldn't be a problem as it is a loadbalanced service.

 

My test gave me the same result if I used "helo err" but if I use a FQDN like "helo host.domain.ch" it works.

I'm actually not sure why it works from your first server but not from your second one.

Maybe the first one is on a whitelist or something....

 

Try to configure your server to use a FQDN in the helo command.

The FQDN does not have to exist as far as I can see but it needs to be a FQDN.

 

Hope that helps...

Edited
5 Comments
Expert
2 of 6

Hello it.corela

 

You have specified as the sender only "eer". This is not valid and therefore the E-mail will not be accepted. There should be at least an @ and  .tld. in FROM. Something like myaddress@mydomain.tld.
 
Best regards
Swisscom
Matthias

 

Meine Spezialgebiete:
Customer Care Support (Mobile & Fixnet)
Social Media Communities ...
Novice
3 of 6

Hello, 

 

Unfortunately it didn't help me.

 

We have tried to send email via telnet from our servers and once it happend with success, but all other attempt was unsuccessful. Here is logs from servers:

 

sending from our server (IP 46.14.162.40)
[root@webservices log]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr BC:AE:C5:2E:BA:D2
inet adr:46.14.162.40 Bcast:46.14.162.47 Masque:255.255.255.240
adr inet6: fe80::beae:c5ff:fe2e:bad2/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70711826 errors:0 dropped:0 overruns:0 frame:0
TX packets:82187918 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:30991779942 (28.8 GiB) TX bytes:87059341519 (81.0 GiB)
Interruption:169 Mémoire:fbde0000-fbe00000

determining addresses of bluewin mail servers
[root@webservices log]# dig bluewin.ch -t MX

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> bluewin.ch -t MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 3

;; QUESTION SECTION:
;bluewin.ch. IN MX

;; ANSWER SECTION:
bluewin.ch. 92 IN MX 42 mxzhb.bluewin.ch.
bluewin.ch. 92 IN MX 10 mxbw.bluewin.ch.
bluewin.ch. 92 IN MX 42 mxzhh.bluewin.ch.

;; ADDITIONAL SECTION:
mxbw.bluewin.ch. 6 IN A 195.186.99.50
mxzhh.bluewin.ch. 326 IN A 195.186.227.50
mxzhb.bluewin.ch. 423 IN A 195.186.99.50

;; Query time: 51 msec
;; SERVER: 195.186.1.162#53(195.186.1.162)
;; WHEN: Mon Feb 17 10:49:58 2014
;; MSG SIZE rcvd: 141


selecting the one mxbw.bluewin.ch with highest priority and sending a email in manual mode using telnet connection to port 25 of mxbw.bluewin.ch.

from: admin@eergeneve.ch
to: it.corela@bluewin.ch (our mailbox at bluewin mail service)
[root@webservices log]# telnet mxbw.bluewin.ch 25
Trying 195.186.227.50...
Connected to mxbw.bluewin.ch (195.186.227.50).
Escape character is '^]'.
220 zhhdzmsp-mxin30.bluewin.ch ESMTP Service (Swisscom Schweiz AG) ready
helo eer
250 zhhdzmsp-mxin30 says HELO to 46.14.162.40:46758
mail from: admin@eergeneve.ch
250 MAIL FROM accepted
rcpt to: it.corela@bluewin.ch
250 RCPT TO accepted
data
354 continue. finished with "\r\n.\r\n"
asd;fgkljsdfg;lksdfjg
adsg;flkdjsfg;sdlfkgj
ad;flgkjsdf;glksdfjg
.
250 <C1/27-03568-96BD1035@zhhdzmsp-mxin30.bluewin.ch> Mail accepted
quit
221 zhhdzmsp-mxin30 closing connection
Connection closed by foreign host.
as you see, message was accepted (and we really received it to our mailbox it.corela@bluewin.ch)


=================================================================================================

now sending from eergeneve.ch server (IP 46.14.162.42) using the same way
root@eer:/var/log/exim4# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 54:04:a6:68:0c:ba
inet addr:46.14.162.42 Bcast:46.14.162.47 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:102905636 errors:0 dropped:0 overruns:0 frame:0
TX packets:107634860 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13499925625 (12.5 GiB) TX bytes:117991720597 (109.8 GiB)
Interrupt:17 Memory:fbde0000-fbe00000

root@eer:/var/log/exim4# telnet mxbw.bluewin.ch 25
Trying 195.186.99.50...
Connected to mxbw.bluewin.ch.
Escape character is '^]'.
220 zhbdzmsp-mxin21.bluewin.ch ESMTP Service (Swisscom Schweiz AG) ready
helo eer
250 zhbdzmsp-mxin21 says HELO to 46.14.162.42:46818
mail from: admin@eergeneve.ch
250 MAIL FROM accepted
rcpt to: it.corela@bluewin.ch
250 RCPT TO accepted
data
354 continue. finished with "\r\n.\r\n"
this is a test message
.
554 FROM: <eer> (46.14.162.42) Not spooled, transaction failed.
quit
221 zhbdzmsp-mxin21 closing connection
Connection closed by foreign host.
as you see, message hasn't been accepted (and we received delivery failure notification to admin@eergeneve.ch)

 

Thanks.

Expert
4 of 6

Hi

 

First thing I recognise is that you do not use the same mailserver (Diffrent IP Address).

However, that shouldn't be a problem as it is a loadbalanced service.

 

My test gave me the same result if I used "helo err" but if I use a FQDN like "helo host.domain.ch" it works.

I'm actually not sure why it works from your first server but not from your second one.

Maybe the first one is on a whitelist or something....

 

Try to configure your server to use a FQDN in the helo command.

The FQDN does not have to exist as far as I can see but it needs to be a FQDN.

 

Hope that helps...

Edited
Expert
5 of 6

Hi it.corela

The initial HELO string has to be a valid fqdn (full qualified domain name). The reason your mail got accepted on one instance was a misconfiguration on that instance.

Liebe Grüsse

PascalW

Meine Spezialgebiete:
Customer Care Support (Mobile & Fixnet)
Social Media Communities
Novice
6 of 6

Hello.

 

Thanks! It really works!

We changed config of our server to pass fqdn-like name with helo and it works well.

Too strange to have such mandatory condition, but in general that's not a problem. 😉

 

About sending email from different servers. You're right. It's the same server but different IPs. Our first IP was 46.14.162.47, but we changed it recently to find out what is the cause of mail rejection from bluewin (we assumed blacklisted IP or subnet). Now it's 46.14.162.42 (the same subnet of our IP-pool). But anyway we have SPF record configured, so different IPs isn't a problem if recipient supports SPF check. And BTW a question, do your mail servers support SPF check?

 

Thanks again for your support.