HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: sendmail errors
Operating System - Linux
1827635
Members
3847
Online
109966
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 04:19 AM
03-06-2007 04:19 AM
Hi Everyone,
One of our support guys has requested I look at a filesystem capacity issue (/var). Having a look through to see why maillog is huge I have noticed the following errors
Mar 4 04:56:51 windomav sendmail[16926]: l218uop1022148: Warning: program /bin/bellmail unsafe: No such file or directory
Mar 4 04:56:51 windomav sendmail[16926]: l218uop1022148: SYSERR(root): Cannot exec /bin/bellmail: No such file or directory
Mar 4 04:56:51 windomav sendmail[16918]: l218uop1022148: to=, delay=2+20:00:00, xdelay=00:00:00, mailer=local, pri=6153182, dsn=4.0.0, stat=Operating system error
I can sendmail without a problem from this server to a server we use for alerting.
/bin/bellmail doesn't exist, there is however the following entry in sendmail.cf
sendmail.cf:Mlocal, P=/bin/bellmail, F=lsDFMAw5:/|@qmn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL,
Has anyone seen anything like this before and know the reason why ?
TIA
Steve
One of our support guys has requested I look at a filesystem capacity issue (/var). Having a look through to see why maillog is huge I have noticed the following errors
Mar 4 04:56:51 windomav sendmail[16926]: l218uop1022148: Warning: program /bin/bellmail unsafe: No such file or directory
Mar 4 04:56:51 windomav sendmail[16926]: l218uop1022148: SYSERR(root): Cannot exec /bin/bellmail: No such file or directory
Mar 4 04:56:51 windomav sendmail[16918]: l218uop1022148: to=
I can sendmail without a problem from this server to a server we use for alerting.
/bin/bellmail doesn't exist, there is however the following entry in sendmail.cf
sendmail.cf:Mlocal, P=/bin/bellmail, F=lsDFMAw5:/|@qmn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL,
Has anyone seen anything like this before and know the reason why ?
TIA
Steve
take your time and think things through
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 05:02 AM
03-06-2007 05:02 AM
Solution
It seems that bellmail is used in some old distributions to deliver mail to users mailboxes.
See:
http://www.securiteam.com/exploits/5FP0D2KFQQ.html
Probably, your configuration file was migrated from version to version and retained this legacy rule. Nowdays procmail is used.
See:
http://www.securiteam.com/exploits/5FP0D2KFQQ.html
Probably, your configuration file was migrated from version to version and retained this legacy rule. Nowdays procmail is used.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-06-2007 07:37 AM
03-06-2007 07:37 AM
Re: sendmail errors
Shalom,
maillog is huge for various reasons.
log level is turned above the default 9 in sendmail.cf or sendmail.mc which generates sendmail.cf
logrotate is not used and the darned thing grows and grows and iis never trimmed.
There appears to be some customization to sendmail.cf or sendmail.mc macro file that is causing this bellmail program which is not on your OS to be run instead of the regular mail processing programs that ship with sendmail.
Perhaps you sendmail configuration was copied in from another system.
SEP
maillog is huge for various reasons.
log level is turned above the default 9 in sendmail.cf or sendmail.mc which generates sendmail.cf
logrotate is not used and the darned thing grows and grows and iis never trimmed.
There appears to be some customization to sendmail.cf or sendmail.mc macro file that is causing this bellmail program which is not on your OS to be run instead of the regular mail processing programs that ship with sendmail.
Perhaps you sendmail configuration was copied in from another system.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP