[Mailman-Users] Minor Mailman problem

2002-02-12 Thread Bob Sully


I received the monthly reminder from mailman earlier this month 
regarding the two mailing lists that I administer.  I noted an 
error in the message, as follows:

"If you have questions, problems, comments, etc, send them to
[EMAIL PROTECTED]  Thanks!"
  ^

There's no problem with the domain name anywhere else.  Messages 
get through to the lists and the admin stuff is dealt with 
correctly.

I'm running 2.0.8-1 on RedHat Linux 7.2/kernel 2.4.9.

Any help in pinpointing the problem will be appreciated...thanks!

-- Bob --
________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The weather is here - wish you were beautiful." - J. Buffett



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] messages stuck and not going out...

2002-02-15 Thread Bob Sully


Be careful!!  This is an invitation to some significant 
headaches.  A friend of mine found his mail server was being used 
as a relay by most of the People's Republic of China (literally 
about 10,000 messages per hour through his little Pentium-200 
mail server) until he shut this option OFF.

YMMV - Good luck - Bob


On Fri, 15 Feb 2002, aaron wrote:

> The solution to my problem was to make the following changes to sendmail:
> 
> - turn on accept_unresolvable_domains.
> 
> once I did this, mailman released all of the messages it has been holding
> for days...

-- 
________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The weather is here - wish you were beautiful." - J. Buffett



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



[Mailman-Users] Group error message

2002-02-21 Thread Bob Sully


Hey all - could someone tip me off as to the problem here?

[mailman@firefox: ~]$ /var/mailman/bin/check_perms
Traceback (innermost last):
  File "/var/mailman/bin/check_perms", line 50, in ?
MAILMAN_GRPNAME = grp.getgrgid(MAILMAN_GID)[0]
TypeError: illegal argument type for built-in operation

TIA - Bob
-- 
________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The weather is here - wish you were beautiful." - J. Buffett



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] Group error message

2002-02-22 Thread Bob Sully


Thanks, Tim - that fixed it.

On Thu, 21 Feb 2002, tim wrote:

> Yes... you are probably using a crudded up Defaults.py.
> I've found that some RPMs of mailman seem to have MAILMAN_UID = 'mailman',
> and MAILMAN_GID = 'mailman', which clearly breaks the Python code.
> 
> If you open Defaults.py and change them to whatever the numerical value of
> mailman is in your /etc/passwd and /etc/group, it'll work.

-- Bob --
____
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The weather is here - wish you were beautiful." - J. Buffett



--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users



Re: [Mailman-Users] /var/log/mailman files

2002-08-27 Thread Bob Sully


Just out of curiosity...you're not running Mandrake 7.1, are you?  That 
release had a strange bug which caused a lot of directories in /var to 
fill up with files with those sorts of names, many levels deep.  This 
was fixed in 7.2 and newer.
--Bob --


On Tue, 27 Aug 2002, Charles Sebold wrote:

> On 19 Elul 5762, Kenneth Jacker wrote:
> 
> > Looking in my /var/log/mailman directory, I see file names such as:
> > 
> > error
> > error.1
> > error.1.1
> > error.1.1.1
> > error.1.1.1.1
> > error.1.1.1.1.1
> 
> This probably indicates a problem with your logrotate scripts (that's
> what bumps logfiles with numbers, and optionally compresses them).  Not
> sure where they are in RedHat but in Debian they're in /etc/logrotate* .
> 

-- 

Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The weather is here - wish you were beautiful." - J. Buffett



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/



[Mailman-Users] Chaning users' e-mail addy

2003-01-02 Thread Bob Sully

Greetings:

Using 2.0.8 under RedHat Linux 7.3 with no problems.

Is there an easy way to change a user's e-mail address in the database 
without having to unsubscribe/resubscribe them?  Failing that, how can I 
do it while preserving their existing password??   

I have noted the announcement of 2.1.  I'm thinking about updating, 
but don't wish to screw with something that works fine already...!

Thanks for all the good work!

-- Bob -- 
________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The waiting is the hardest part." - T. Petty



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org



[Mailman-Users] Failures after Sendmail upgrade

2003-03-01 Thread Bob Sully

Just upgraded to Mailman 2.0.13 from 2.0.8 a couple of weeks ago.  Last 
week I upgraded Sendmail from 8.12.3 to 8.12.7.  I got a bunch of these 
back today (after the monthly reminders were sent out).  Is this a 
Mailman issue or sendmail?


The original message was received at Sat, 1 Mar 2003 05:00:14 -0800
from cust.64-52-19.058.ip.ebrb.net [64.52.19.58]
with id h21D0E40020264

   - The following addresses had permanent fatal errors -
"| /var/mailman/mail/wrapper mailowner samohi74" 
(reason: Service unavailable)
(expanded from: <[EMAIL PROTECTED]>)

   - Transcript of session follows -
smrsh: "wrapper" not available for sendmail programs (stat failed)
554 5.0.0 Service unavailable


It seems that smrsh is the culprit.

All was working well until these upgrades were done.

Any help with this would be appreciated...


-- Bob -- 
________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The waiting is the hardest part." - T. Petty






--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Failures after Sendmail upgrade

2003-03-01 Thread Bob Sully

Jon:
I upgraded via the 8.12.7 tarball, not rpm; the old 8.12.3 version was 
rpm'd.

Nope...that wasn't it.  There's no directory sm.bin anywhere on the 
server.

I was able to get working by disabling smrsh altogether (removing the 
line enabling it in sendmail.mc, then recreating sendmail.cf); the 
mailing lists are now functioning as they were before.  However, 
I'd like to find a better fix than this, if possible; smrsh does serve 
a security function, I suppose!  Thanks again.

-- Bob --


On 1 Mar 2003, Jon Carnes wrote:

> Depending on how you upgraded, it might be checking the wrong directory
> for smrsh information.  There is a note in the Archives discussing this.
> 
> === From Keith Steward ===
> When CMDDIR is not defined by the OS, then in smrsh.c it defaults to
> /usr/adm/sm.bin/ .  Even though RedHat7.2 already has an /etc/smrsh/
> directory (including a link entry there for slocal), the Sendmail (at
> least the 8.11.6 version I downloaded and installed) was not using that
> directory.  Instead, it was looking for the default /usr/adm/sm.bin/. 
> The /etc/smrsh/ directory was a red herring!  Once I created the
> /usr/adm/sm.bin, and chmod 755 (recommended by the smrsch/README within
> Sendmail), and then set up the symbolic link in there:
> mailman -> /usr/local/mailman/mail/mailman
> the problem disappeared.
> ===
> 
> HtH - Jon Carnes
> 
> On Sat, 2003-03-01 at 20:57, Bob Sully wrote:
> > 
> > Just upgraded to Mailman 2.0.13 from 2.0.8 a couple of weeks ago.  Last 
> > week I upgraded Sendmail from 8.12.3 to 8.12.7.  I got a bunch of these 
> > back today (after the monthly reminders were sent out).  Is this a 
> > Mailman issue or sendmail?
> > 
> > 
> > The original message was received at Sat, 1 Mar 2003 05:00:14 -0800
> > from cust.64-52-19.058.ip.ebrb.net [64.52.19.58]
> > with id h21D0E40020264
> > 
> >- The following addresses had permanent fatal errors -
> > "| /var/mailman/mail/wrapper mailowner samohi74" 
> > (reason: Service unavailable)
> > (expanded from: <[EMAIL PROTECTED]>)
> > 
> >- Transcript of session follows -
> > smrsh: "wrapper" not available for sendmail programs (stat failed)
> > 554 5.0.0 Service unavailable
> > 
> > 
> > It seems that smrsh is the culprit.
> > 
> > All was working well until these upgrades were done.
> > 
> > Any help with this would be appreciated...
-- 

Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The waiting is the hardest part." - T. Petty




--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Failures after Sendmail upgrade

2003-03-01 Thread Bob Sully

Ashley:  Nice thought, but no go.  Plus. /etc/smrsh already contained 
the link.  I followed your steps below; no joy.

[EMAIL PROTECTED]: /etc/mail]$ lsl /etc/smrsh/
total 92
drwxr-xr-x2 root root 1024 Feb  9 18:36 ./
drwxr-xr-x   77 root root 7168 Mar  1 20:00 ../
lrwxrwxrwx1 root root   19 Dec 24  1999 slocal -> 
/usr/lib/nmh/slocal*
-rwxrwxr-x1 mailman  mailman 84127 Jan  4  2002 demime*
lrwxrwxrwx1 root root   30 Feb  9 18:36 wrapper -> 
../../var/mailman/mail/wrapper*

[EMAIL PROTECTED]: /etc/mail]$ lsl /usr/adm/sm.bin/
total 2
drwxrwxr-x2 root root 1024 Mar  1 20:41 ./
drwxrwxr-x3 root root 1024 Mar  1 20:41 ../
lrwxrwxrwx1 root root   25 Mar  1 20:41 wrapper -> 
/var/mailman/mail/wrapper*

-- Bob --


On Sat, 1 Mar 2003, Ashley M. Kirchner wrote:

> Bob Sully wrote:
> 
>  >   - Transcript of session follows -
>  >smrsh: "wrapper" not available for sendmail programs (stat failed)
>  >554 5.0.0 Service unavailable
>  >
>  # mkdir /usr/adm/sm.bin
>  # cd /usr/adm/sm.bin
>  # ln -sf /usr/local/mailman/mail/wrapper ./
>  NOTE: replace the above path with the path of your MM installation
> 
> 
>  smrsh will need to have mailman's wrapper in it's directory and last
> I checked, sendmail (be it rpm or tarball) doesn't create that directory.
> 
> 

-- 

Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The waiting is the hardest part." - T. Petty



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Newbe Headaches

2003-03-12 Thread Bob Sully

Jon:

You've seen the flurry of these over the past couple of weeks.  I firmly 
believe that the problem lies with some mod to smrsh in the latest 
versions of Sendmail.  I had previously been running 2.0.13 with 
Sendmail 8.12.3 without a problem...after upgrading to 8.12.7 I got the 
same message as below; same thing with 8.12.8.  The only way to get 
around this is to disable smrsh in sendmail.mc -> sendmail.cf.  This is 
bothersome, as smrsh does have some (albeit minor?) security value.  I'd 
like to see a fix for this soon.  Perhaps we should alert the Sendmail 
developers.

-- Bob --



On Wed, 12 Mar 2003, Jon Carnes wrote:

> Well, you could disable the Smrsh control from within Sendmail - or - you
> could look up on your system where Smrsh's link directory should be located.
> You may have to create the directory and then create your links to the
> Mailman executables.
> 
> Good Luck - Jon Carnes
> 
> BTW: there are some recent expositions about Smrsh in the Archives that
> contain more info about Smrsh and its default settings.

> >
> >- Transcript of session follows -
> > smrsh: "mailman" not available for sendmail programs (stat failed)
> > 554 5.0.0 Service unavailable

-- 

Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The waiting is the hardest part." - T. Petty



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Newbe Headaches

2003-03-12 Thread Bob Sully

Jon:  I did install from source but paid special attention to the smrsh 
directories.  Everything is where it should be.  Still didn't work.

-- Bob --


On 12 Mar 2003, Jon Carnes wrote:

> Most of these (I think) were from folks upgrading their Sendmail due to
> the recent vulnerability and subsequent update release.  I would hope
> that folks using package management (like rpm or apt-get) would have no
> problems if they used the updated packages for their distributions.
> 
> If folks are installing from source they could easily overlook the
> placement of the smrsh directories...
> 
> On Wed, 2003-03-12 at 13:02, Bob Sully wrote:
> > 
> > Jon:
> > 
> > You've seen the flurry of these over the past couple of weeks.  I firmly 
> > believe that the problem lies with some mod to smrsh in the latest 
> > versions of Sendmail.  I had previously been running 2.0.13 with 
> > Sendmail 8.12.3 without a problem...after upgrading to 8.12.7 I got the 
> > same message as below; same thing with 8.12.8.  The only way to get 
> > around this is to disable smrsh in sendmail.mc -> sendmail.cf.  This is 
> > bothersome, as smrsh does have some (albeit minor?) security value.  I'd 
> > like to see a fix for this soon.  Perhaps we should alert the Sendmail 
> > developers.

-- 

Bob Sully - Simi Valley, California, USA
http://www.malibyte.net

"The waiting is the hardest part." - T. Petty



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Integration with ClamAV

2004-03-27 Thread Bob Sully

Use ClamAV with MimeDefang, and set it up so anything with a virus 
signature gets rejected.  Works wonderfully on my servers.


On Sat, 27 Mar 2004, Brendan Chard wrote:

> I'm running Mailman 2.1.4 on a FreeBSD server using sendmail as my MTA.  I
> have ClamAV already installed and running using the clamd/clamc combo
> 
> What is the best way to integrate ClamAV with Mailman so that viruses posted
> to lists will be nuked?
> 
> 
> Thanks,
> -Brendan
> [EMAIL PROTECTED]

________
Bob Sully - Simi Valley, California, USA
http://www.malibyte.net
http://www.malibyte.com

"The floggings will continue until morale improves."

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/


Re: [Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.

2005-01-28 Thread Bob Sully

Agreed:  I run Fedora Core 2 with Mailman on one of my mail servers, 
using MIMEDefang with SpamAssassin and Clam Antivirus, along with having 
my lists fully moderated.  I've never had even one spam or virus get 
through (lists have been up for several years; started with RedHat 
6.2 or 7.1 and Mailman 2.0.7, as I recall).

Bob



On Fri, 28 Jan 2005, Jeff Groves wrote:

> Maybe you should install a virus scanning feature to your mailer?
> 
> I use mimedefang which has a hook to many different virus scanning products.  
> I use f-prot.
> 
> My platform:
> 
>   Fedora Core 2
>   Sendmail 8.13.1
>   mimedefang 2.48
>   f-prot linux ws 4.4.2
> 
> this configuration discards infected email messages.
> 
> 
> Jeff g.


Bob Sully - Simi Valley, California, USA
http://www.malibyte.net
http://www.malibyte.com

"There will be no white flag above my door."
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/