I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Bob Goodwin
At 2:14 PM -0400 6/28/07, Bob Goodwin - W2BOD wrote:
I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Send some small test mail that way.
[]$ mail -s 'test' bobgoodwin@wildblue.net test 1 <Ctl-D>CC: []$
Try tar'ing the dir up as a .tgz and see if that gets through.
Inspect the mail settings the ISP provides; turn off their spamassasin if you can.
Tony Nelson wrote:
At 2:14 PM -0400 6/28/07, Bob Goodwin - W2BOD wrote:
I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Send some small test mail that way.
[]$ mail -s 'test' bobgoodwin@wildblue.net test 1 <Ctl-D>CC: []$
Nothing I try gets through ...
Try tar'ing the dir up as a .tgz and see if that gets through.
I tried sending an existing ".tgz" file, no different.
Inspect the mail settings the ISP provides; turn off their spamassasin if you can.
I am not aware of any way to do that. In fact they don't mention processing mail for spam although they may do so. I don't see anything listed under events in Firestarter so it looks like it's not blocked there.
I just haven't been able to find anything but I would like to see the message that is supposed to be sent. Don't know how to get that?
Bob Goodwin
Bob Goodwin - W2BOD wrote:
Tony Nelson wrote:
At 2:14 PM -0400 6/28/07, Bob Goodwin - W2BOD wrote:
I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Have you looked in /var/log/maillog for an error message? It is possible in the changes you mentioned, your ISP now requires authentication before accepting mail. Another possibility is that your ISP now requires that the there be a reverse DNS for the hostname of the mail server that is sending it a message.
Mikkel
Mikkel L. Ellertson wrote:
Bob Goodwin - W2BOD wrote:
Tony Nelson wrote:
At 2:14 PM -0400 6/28/07, Bob Goodwin - W2BOD wrote:
I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Have you looked in /var/log/maillog for an error message? It is possible in the changes you mentioned, your ISP now requires authentication before accepting mail. Another possibility is that your ISP now requires that the there be a reverse DNS for the hostname of the mail server that is sending it a message.
Mikkel
"reverse DNS?" Wireshark displayed a number of lines about DNS which I did not understand. I hate to admit it but what's a reverse DNS? Guess I need to look that up ...
Bob Goodwin
Bob Goodwin - W2BOD wrote:
Mikkel L. Ellertson wrote:
Bob Goodwin - W2BOD wrote:
Tony Nelson wrote:
At 2:14 PM -0400 6/28/07, Bob Goodwin - W2BOD wrote:
I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Have you looked in /var/log/maillog for an error message? It is possible in the changes you mentioned, your ISP now requires authentication before accepting mail. Another possibility is that your ISP now requires that the there be a reverse DNS for the hostname of the mail server that is sending it a message.
Mikkel
"reverse DNS?" Wireshark displayed a number of lines about DNS which I did not understand. I hate to admit it but what's a reverse DNS? Guess I need to look that up ...
Bob Goodwin
Ok, I see reverse DNS is simply reversing the process, not sure how that affects me?
The maillog does show some cryptic [to me] errors:
Jun 28 16:36:55 box6 sendmail[1091]: l5SKaLF4001091: to=bobgoodwin@wildblue.net, ctladdr=root (0/0), delay=00:00:34, xdelay=00:00:30, mailer=relay, pri=989592, relay=[127.0.0.1] [127.0.0.1], dsn=5.6.0, stat=Data format error Jun 28 16:36:55 box6 sendmail[1091]: l5SKaLF4001091: l5SKaLF5001091: DSN: Data format error
Perhaps someone can tell me what this means?
Maybe I should just wait until I've installed Fedora 7. It may be different then.
Bob Goodwin
<snip />
The maillog does show some cryptic [to me] errors:
Jun 28 16:36:55 box6 sendmail[1091]: l5SKaLF4001091: to=bobgoodwin@wildblue.net, ctladdr=root (0/0), delay=00:00:34, xdelay=00:00:30, mailer=relay, pri=989592, relay=[127.0.0.1] [127.0.0.1], dsn=5.6.0, stat=Data format error Jun 28 16:36:55 box6 sendmail[1091]: l5SKaLF4001091: l5SKaLF5001091: DSN: Data format error
Perhaps someone can tell me what this means?
DSN = delivery status notification
Found this on google:
if your sending machine does not have it's own name/IPaddress in its /etc/hosts file, it will cause the upstream target/relay host to reject the message with something which means: "I don't know who you are". The sending MTA sendmail then issues the error in the maillog "...dsn=5.6.0 stat=Data Format Error". The fix for this is to have a correct /etc/hosts;
The advice to fix your dns seems to be spot on.
:m)
Bob Goodwin - W2BOD wrote:
Mikkel L. Ellertson wrote:
Have you looked in /var/log/maillog for an error message? It is possible in the changes you mentioned, your ISP now requires authentication before accepting mail. Another possibility is that your ISP now requires that the there be a reverse DNS for the hostname of the mail server that is sending it a message.
Mikkel
"reverse DNS?" Wireshark displayed a number of lines about DNS which I did not understand. I hate to admit it but what's a reverse DNS? Guess I need to look that up ...
Bob Goodwin
That is where they take your IP address, and look up the hostname that goes with it. There is an option to reject mail if they do not match. It is not usually a good rule to use.
Another check that is sometime done is to check for a MX record for the domain the message is coming from. It stops mail from fake domains. But not all domains have a MX record...
Mikkel
Bob Goodwin - W2BOD wrote:
Tony Nelson wrote:
At 2:14 PM -0400 6/28/07, Bob Goodwin - W2BOD wrote:
I had been using Mail -s "msg-logs" bobgoodwin@wildblue.net < /var/spool/mail/bobg until about three weeks ago when it quit working.
I am beginning to think that my ISP has done something to cause these messages not to go through since it appeared to me that they were making changes that created a lot of disruption in the mail server operation at that time.
I have been trying to send other files such as:
Mail -s "msg-logs" bobgoodwin@wildblue.net < /home/bobg/ootext/FAP.txt
with no success, nothing comes back? Normally these are filtered into a Thunderbird directory "msg-logs" The filter set up looks ok. I haven't changed anything there and if it didn't work I would hope the mail would just show up in Inbox.
Is there a way I could see the outgoing message to be sure it is actually being sent?
Can someone suggest a logical way to troubleshoot this problem? I've been putting this problem off but it's an annoyance that needs fixing!
Send some small test mail that way.
[]$ mail -s 'test' bobgoodwin@wildblue.net test 1 <Ctl-D>CC: []$
Nothing I try gets through ...
Try tar'ing the dir up as a .tgz and see if that gets through.
I tried sending an existing ".tgz" file, no different.
Inspect the mail settings the ISP provides; turn off their spamassasin if you can.
I am not aware of any way to do that. In fact they don't mention processing mail for spam although they may do so. I don't see anything listed under events in Firestarter so it looks like it's not blocked there.
I just haven't been able to find anything but I would like to see the message that is supposed to be sent. Don't know how to get that?
Bob Goodwin
Hi Bob, the head of the IP dept at NMSU used mail because he got several hundred emails daily back then. I just played around with mail and read all my root mail which I normally use pine to deal with.
But then it occurs to me that you have at least a couple of users on your Linux. You can check if mail is working properly between these users on your own computer. If not then you know where to start. I will try to get my mail to work as well. This is old time stuff.
Karl