I think the battle is nearly ending, less this one particular issue that seems
to be holding it back.
I can receive mail in, and it gets pushed into the relevent groupserver group.
However, outbound mail doesn't get sent.
Now, I found the wget command in the docs and ran it. Then, I get a bunch of
these in the mail.log;
Oct 16 05:35:56 four postfix/smtpd[65491]: connect from localhost[127.0.0.1]
Oct 16 05:35:56 four postfix/smtpd[65491]: lost connection after RSET from
localhost[127.0.0.1]
Oct 16 05:35:56 four postfix/smtpd[65491]: disconnect from localhost[127.0.0.1]
and it doesn't send the mail. The messages sit in the /tmp/mailboxer...
directory, so each time the cron URL is requested, these messages in mail.log
re-appear, and it doesn't actually send them.
Any ideas?
As a side note, wget doesn't seem to like the "204 no content" header, as it
sits around waiting for content, regardless of the header, and eventually ends
up gathing wget processes waiting for content it'll never get. I find curl
behaves better;
curl -s http://{host}:{port}/groupserver/ListManager/processSpool > /dev/null
I'd like to confirm that I ran across errors with wget -O also. In my case, I
setup a cron job as recommended in the install guide and was confident I had
the host and port correct but still did not see proper mail functions. There
were several issues but I later discovered that I had hundreds of these wget -O
processes running and it was a "yikes" moment.
Note to Devel: It would be helpful to recommend in the install guide that the
installer run appropriate command(s) from the command line so that they assure
they have the proper hostname and port and observe that the command runs
properly on their system before they commit it to a cron.
The wget -O part one would run manually is:
wget -O/dev/null http://{host}:{zope_port}/groupserver/ListManager/processSpool
I did this and observed wget saying: "HTTP request sent, awaiting response...
204 No Content". It just kept waiting and waiting forever. I pressed Ctrl + C
to cancel from the command line -- this will not happen when it runs from cron.
If you are having the 204 error with wget -O the alternative to install curl on
your system (apt-get install curl) does work.
Dan: I did not find any reason for using the "> /dev/null" you added. I have
not seen any output when using the -s option that makes curl silent (doesn't
display progress or errors). So far I have not seen it produce any output.
The curl -s part one would run manually is:
curl -s http://{host}:{zope_port}/groupserver/ListManager/processSpool
yes, you're quite right. ">/dev/null" is irrelevant here. i think what i did
was simply substitute "wget -O /dev/null" for "curl -s". i always put a 2>&1
/dev/null at the end of all my cron scripts, incase certain applications end up
with a habit of filling the root mail file with random crap.
maybe it's because i'm currently dealing with hosting *very* bad code right
now, and it's just become a force of habit.
Hi Dan,
Thanks for the tip. I have seen some apps that fill up mail accounts as you
say.
Rest of post
Ross
-----Original Message-----
From: <email obscured> <email obscured>] On
Behalf Of dan
Sent: Monday, October 24, 2011 1:45 PM
To: <email obscured>
Subject: Re: [groupserver development] No mail notifications
yes, you're quite right. ">/dev/null" is irrelevant here. i think what i did
was simply substitute "wget -O /dev/null" for "curl -s". i always put a 2>&1
/dev/null at the end of all my cron scripts, incase certain applications end
up with a habit of filling the root mail file with random crap.
maybe it's because i'm currently dealing with hosting *very* bad code right
now, and it's just become a force of habit.
-----------------------------------------
Full text of this topic in GroupServer Development:
http://groupserver.org/r/topic/1d2F43J2MURbfOljzeejLi
To leave GroupServer Development, email
<email obscured>?Subject=unsubscribe
Start your own free groups and site with OnlineGroups.Net
http://onlinegroups.net
Host your own online groups site with
GroupServer http://groupserver.org
Hi Ross,
I would like to add a script to the install process that checks to test
the email-settings. The same script could also check to see if the
host-names are correct. In many ways this will be better than adding to
the documentation: longer documentation is harder to read, the system
will never skip running the test, and the system can suggest a solution
so we do not have to ☺
