Thanks for pointing out the USER=0 thing. That seems to have fixed half of my problems. I am able to receive messages now for the echos (and email)
if they are address to @capitolcityonline.net. I am still having issues
with @capcity2.synchro.net bouncing emails. I will have to ask DM about that. :)
Hemo,
Thanks for pointing out the USER=0 thing. That seems to have fixed half of my problems. I am able to receive messages now for the echos (and email)
if they are address to @capitolcityonline.net. I am still having issues
with @capcity2.synchro.net bouncing emails. I will have to ask DM about that. :)
I seem to be having issues receiving email that is routed to a capcity2.synchro.net address. The ISP I am sending them from is returning the error below. It appears that the ISP is generating the error. I have also included the headers on the returned message. I have had 3 or 4 returned, and one of my users was also complaining about sending mail from another email service that was not arriving here.
I thought it might be on this end, but I am able to send/receive emails
using my no-ip reflector address and, thanks to hemo, I am now receiving list traffic also. So my port (587) is open and receiving traffic. I am also able to telnet to 'capcity2.synchro.net 587' and get a response.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
mike.powell@capcity2.synchro.net
host capcity2.synchro.net [67.131.57.133]
retry timeout exceeded
There is no MX entry for capcity2.synchro.net - In your dyndns setup you need to send an MX if you want Vert to relay email to you.
$ dig -t mx eotlbbs.synchro.net +short
0 endofthelinebbs.com.
$ dig -t mx capcity2.synchro.net +short
$
Thanks for pointing out the USER=0 thing. That seems to have fixed half of my problems. I am able to receive messages now for the echos (and email)
if they are address to @capitolcityonline.net. I am still having issues with @capcity2.synchro.net bouncing emails. I will have to ask DM about that. :)
Good morning!
I seem to be having issues receiving email that is routed to a capcity2.synchro.net address. The ISP I am sending them from is returning the error below. It appears that the ISP is generating the error. I have also included the headers on the returned message. I have had 3 or 4 returned, and one of my users was also complaining about sending mail from another email service that was not arriving here.
I thought it might be on this end, but I am able to send/receive emails using my no-ip reflector address and, thanks to hemo, I am now receiving list traffic also. So my port (587) is open and receiving traffic. I am also
able to telnet to 'capcity2.synchro.net 587' and get a response.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
mike.powell@capcity2.synchro.net
host capcity2.synchro.net [67.131.57.133]
retry timeout exceeded
Thanks to Nelgin and some wiki reading, I got this error straightened out. However, I am not getting the following error:
mike.powell@capcity2.synchro.net
host mail.synchro.net [71.95.196.36]
SMTP error from remote mail server after RCPT TO:<mike.powell@capcity2.synchro.net>:
553 Relaying through this server requires authentication. Please authenticate before sending.
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 28 |
Nodes: | 8 (0 / 8) |
Uptime: | 190:48:44 |
Calls: | 2,006 |
Calls today: | 3 |
Files: | 11,114 |
Messages: | 942,286 |