cant get email into my mailbox but can send

[#1]

im not having trouble logging into webmail im having trouble getting email sent into my email on my computer. i was using metronet co.uk for email and then last weds 29th june its stopped working. i went to try and get to the metronet webmail homepage and that had gone!! I rang up and the guy told me how to get webmail via plusnet. and talked me around to get mail working again by changing settings. None of them worked. I rang again on monday and on tuesday. tried every port configaration on IN and OUT going mail. Im using a macbook using OSX 10.6.8 running - apple mail 4.6. The only thing that has changed was that you stopped metronets server working. Now i can send mail but only get a boing sound when try to recieve ie its not accessing the mail server. This is probably due to a missing password as it ask me :

Enter the password for user “xxxxxxxxxx @metronet.co.uk” on POP server “mail.plus.net”

I dont however have a password for plusnet except for the one given to get in here and my webmail password and none of those work!! Please supply me with a password as i need my email for work and for regularly checking email as my mum is on a possible waiting list fro her stroke treatment and i need to know immediately if she has to get to hospital. NB the problem is at YOUR END NOT MINE

Yours sincerely

Andy Howard

[#2]

THis is an open forum and I recommend you remove your emails from your post

[#3]

thanks done

[#4]

---

@andyhoward wrote:

@Enter the password for user “xxxxxxxxxx @metronet.co.uk” on POP server “mail.plus.net”

---

When setting up your email client you should still be using mail.metronet.co.uk with port 110 for POP3 mail collection along with your Metronet account password. SSL/TLS must not be selected.

Was it access to that service that stopped working for you on 29th June?

Does it respond if you run ping mail.metronet.co.uk from a command prompt?

I'm wondering if your problem is similar to that mentioned in topic Can not connect to email server though in that topic sending also did not work. Plusnet fixed this problem by tweaking account settings.

[#5]

hi david,  Thanks. Yes it was access to that service that stopped. I have just tried those setting s again with all the passwords i have to no avail again it just boings  back. Did ping and came back:

ping: cannot resolve mail.metronet.co.uk: Unknown host ?? plus net tried to fix and now changed all settings with them loads of  times !!

[#6]

@andyhoward, can you please try opening a terminal window and try tracing to the incoming and outgoing Metronet mail servers? e.g.

traceroute -I mail.metronet.co.uk
traceroute to mail.metronet.co.uk (212.159.8.85), 30 hops max, 60 byte packets
 1  192.168.1.254 (192.168.1.254)  11.902 ms  11.740 ms *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * te9-4.ptn-gw01.plus.net (195.166.129.33)  18.378 ms  17.791 ms
 7  gi5-1.peh-cr02.plus.net (84.93.232.61)  28.282 ms  28.206 ms  33.658 ms
 8  po5.peh-cr01.plus.net (84.93.232.16)  33.478 ms  30.044 ms  31.604 ms
 9  vlan2657.peh-elb01.plus.net (84.93.232.44)  29.771 ms  31.238 ms  35.086 ms
10  pop.metronet.co.uk (212.159.8.85)  32.677 ms  32.602 ms  37.341 ms

traceroute -I relay.metronet.co.uk
traceroute to relay.metronet.co.uk (212.159.8.108), 30 hops max, 60 byte packets
 1  192.168.1.254 (192.168.1.254)  9.290 ms  9.127 ms *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * gi5-1.peh-cr02.plus.net (84.93.232.61)  28.133 ms  29.430 ms
 7  po5.peh-cr01.plus.net (84.93.232.16)  27.369 ms  27.295 ms  29.043 ms
 8  vlan2657.peh-elb01.plus.net (84.93.232.44)  28.881 ms  34.520 ms  32.742 ms
 9  relay.metronet.co.uk (212.159.8.108)  34.258 ms  32.524 ms  32.406 ms 

[#7]

Hi Bob, Thanks for help

Done that in the terminal window  and this is what came back : hope this help id problem?

Last login: Wed Jul 6 14:32:49 on ttys000
(null):~ andys$ traceroute -I mail.metronet.co.uk
traceroute to mail.metronet.co.uk (212.159.8.85), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 11.902 ms 11.740 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * te9-4.ptn-gw01.plus.net (195.166.129.33) 18.378 ms 17.791 ms
7 gi5-1.peh-cr02.plus.net (84.93.232.61) 28.282 ms 28.206 ms 33.658 ms
8 po5.peh-cr01.plus.net (84.93.232.16) 33.478 ms 30.044 ms 31.604 ms
9 vlan2657.peh-elb01.plus.net (84.93.232.44) 29.771 ms 31.238 ms 35.086 ms
10 pop.metronet.co.uk (212.159.8.85) 32.677 ms 32.602 ms 37.341 ms

traceroute -I relay.metronet.co.uk
traceroute to relay.metronet.co.uk (212.159.8.108), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 9.290 ms 9.127 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * gi5-1.peh-cr02.plus.net (84.93.232.61) 28.133 ms 29.430 ms
7 po5.peh-cr01.plus.net (84.93.232.16) 27.369 ms 27.295 ms 29.043 ms
8 vlan2657.peh-elb01.plus.net (84.93.232.44) 28.881 ms 34.520 ms 32.742 ms
9 relay.metronet.cotraceroute: unknown host mail.metronet.co.uk
(null):~ andys$ traceroute to mail.metronet.co.uk (212.159.8.85), 30 hops max, 60 byte packets
-bash: syntax error near unexpected token `('
(null):~ andys$ 1 192.168.1.254 (192.168.1.254) 11.902 ms 11.740 ms *
-bash: syntax error near unexpected token `('
(null):~ andys$ 2 * * *
-bash: 2: command not found
(null):~ andys$ 3 * * *
-bash: 3: command not found
(null):~ andys$ 4 * * *
-bash: 4: command not found
(null):~ andys$ 5 * * *
-bash: 5: command not found
(null):~ andys$ 6 * te9-4.ptn-gw01.plus.net (195.166.129.33) 18.378 ms 17.791 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 7 gi5-1.peh-cr02.plus.net (84.93.232.61) 28.282 ms 28.206 ms 33.658 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 8 po5.peh-cr01.plus.net (84.93.232.16) 33.478 ms 30.044 ms 31.604 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 9 vlan2657.peh-elb01.plus.net (84.93.232.44) 29.771 ms 31.238 ms 35.086 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 10 pop.metronet.co.uk (212.159.8.85) 32.677 ms 32.602 ms 37.341 ms
-bash: syntax error near unexpected token `('
(null):~ andys$
(null):~ andys$ traceroute -I relay.metronet.co.uk
traceroute to relay.metronet.co.uk (212.159.8.108), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 9.290 ms 9.127 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * gi5-1.peh-cr02.plus.net (84.93.232.61) 28.133 ms 29.430 ms
7 po5.peh-cr01.plus.net (84.93.232.16) 27.369 ms 27.295 ms 29.043 ms
8 vlan2657.peh-elb01.plus.net (84.93.232.44) 28.881 ms 34.520 ms 32.742 ms
9 relay.metronet.co.uk (212.159.8.108) 34.258 ms 32.524 ms 32.406 ms traceroute: unknown host relay.metronet.co.uk
(null):~ andys$ traceroute to relay.metronet.co.uk (212.159.8.108), 30 hops max, 60 byte packets
-bash: syntax error near unexpected token `('
(null):~ andys$ 1 192.168.1.254 (192.168.1.254) 9.290 ms 9.127 ms *
-bash: syntax error near unexpected token `('
(null):~ andys$ 2 * * *
-bash: 2: command not found
(null):~ andys$ 3 * * *
-bash: 3: command not found
(null):~ andys$ 4 * * *
-bash: 4: command not found
(null):~ andys$ 5 * * *
-bash: 5: command not found
(null):~ andys$ 6 * gi5-1.peh-cr02.plus.net (84.93.232.61) 28.133 ms 29.430 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 7 po5.peh-cr01.plus.net (84.93.232.16) 27.369 ms 27.295 ms 29.043 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 8 vlan2657.peh-elb01.plus.net (84.93.232.44) 28.881 ms 34.520 ms 32.742 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ 9 relay.metronet.co.uk (212.159.8.108) 34.258 ms 32.524 ms 32.406 ms
-bash: syntax error near unexpected token `('
(null):~ andys$ (

[#8]

Thanks. We've an internal incident raised and our engineers are looking into it (ref: 93082)

Edit: This issue was fixed w/c 18/07.