At 08:14 AM 1/14/2008, you wrote:
Ahh... your quoting seems to be working now... now I can at least
make sense of your replies without straining...
Next we'll address the top-posting problem... ;)
The top posting problem was temporary until I could get the quoting
working right. I figured
Success! :-D
It seems I owe you another adult beverage of your choice. Thanks.
Just out of curiosity, where is that parameter kept such that it did
not get restored from the backup yet all the list archives and members did?
At 09:44 PM 1/12/2008, you wrote:
These will affect list
Dennis Putnam wrote:
Success! :-D
It seems I owe you another adult beverage of your choice. Thanks.
Just out of curiosity, where is that parameter kept such that it did
not get restored from the backup yet all the list archives and members did?
host_name is in the list's config.pck file
Thanks for the reply. I have a guess as to what is wrong but I don't
know how to fix it in mailman. Here are the syslog entries for a
non-mailman email:
Jan 12 10:55:10 dap002 postfix/qmgr[2345]: 47CD185063:
from=[EMAIL PROTECTED], size=435, nrcpt=1 (queue active)
Jan 12 10:55:16 dap002
On 1/12/08, Dennis Putnam wrote:
Thanks for the reply. I have a guess as to what is wrong but I don't
know how to fix it in mailman. Here are the syslog entries for a
non-mailman email:
Jan 12 10:55:10 dap002 postfix/qmgr[2345]: 47CD185063:
from=[EMAIL PROTECTED], size=435, nrcpt=1
At 05:58 PM 1/12/2008, you wrote:
Well, if the hostname really was home.bellsouth.net, that would map
to IP address 216.77.188.41, but the reverse DNS for this IP address
points back to dsl.bellsouth.net, which does map correctly back to
the same IP address. So, I would not be surprised to
Dennis Putnam wrote:
Here the from hostname is 'dap002.bellsouth.net' instead of
'home.bellsouth.net', that is not to say I know this is the problem
but its all I can see as different. Obviously mailman is somehow
overriding the normal from hostname and building its own. The name
'dap002' is
Dennis Putnam writes:
Keep in mind this was a working system that started giving me trouble
after a restore.
Unfortunately, that's not really possible. People who do not have
access to your system can only match symptoms to cases they've seen in
the past. This particular symptom is
On 1/12/08, Dennis Putnam wrote:
Certainly, the name dap002.bellsouth.net does not exist in the DNS.
If this is what your system is trying to use to identify itself to
the outside world, that would be a problem.
Only mailman is trying to use that name.
Not true. Check your own syslog
Dennis Putnam wrote:
550 [PERMFAIL] bellsouth.net requires valid sender domain (in reply to
RCPT TO command))
I should have paid more attention, sorry. Is not the RCPT TO command
itself but the reply to it and I believe it is referring to my
mailman/SMTP server.
I think it is refering to the
Dennis Putnam wrote:
I'll give that a try. In the mean time maybe it is not what I thought
based on your explanation. The specific error from my ISP complains
about a missing DNS entry for RCPT TO. How do I set mailman to place
the correct RCPT TO information in the headers for my SMTP server. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the reply.
No. I do not have a static IP or a registered domain, which is why all
mail from this server has to go through my ISP's server. However,
non-mailman mail is sent just fine. If it is indeed the MAIL FROM
then why would my changes
Dennis Putnam wrote:
No. I do not have a static IP or a registered domain, which is why all
mail from this server has to go through my ISP's server. However,
non-mailman mail is sent just fine. If it is indeed the MAIL FROM
then why would my changes in mm_cfg.py, not have fixed it? On the
other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm beginning to think it would have been easier to just start all
over if I didn't care about my users getting upset. Anyway I still
seem to have a problem that I didn't have before the restore.
Since I don't know what is supposed to happen during
Dennis Putnam wrote:
Since I don't know what is supposed to happen during processing I
guess all I can do is guess. When I send a request to one on my lists
(list name-request) the smtp log shows an error. The request gets
processed at least is it piped tp the mailman request command, and
then
15 matches
Mail list logo
