HP-UX sendmail won't start

if unable to start sendmail and get the following error messages in syslog, the fix is at the bottom:

Nov 19 15:13:06 HOSTNAME /sbin/init.d/sendmail[11536]: Unable to start Sendmail.
Nov 19 15:13:06 HOSTNAME /sbin/init.d/sendmail[11536]:
Nov 19 15:13:06 HOSTNAME /sbin/init.d/sendmail[11536]: The sendmail.cf file is configured for send_only feature.
Nov 19 15:13:06 HOSTNAME /sbin/init.d/sendmail[11536]: Modify the /etc/rc.config.d/mailservs file with the send_only feature.
Nov 19 15:13:07 HOSTNAME /sbin/init.d/sendmail[11536]: To disable the send_only feature:
Nov 19 15:13:07 HOSTNAME /sbin/init.d/sendmail[11536]: - Run the gen_cf file to generate the sendmail.cf file.
Nov 19 15:13:07 HOSTNAME /sbin/init.d/sendmail[11536]: - Merge your site-specific customizations with the /usr/newconfig/etc/mail/cf/cf/sendmail.cf.gen file.
Nov 19 15:13:06 HOSTNAME /sbin/init.d/sendmail[11536]:
Nov 19 15:13:07 HOSTNAME /sbin/init.d/sendmail[11536]: - Copy the /usr/newconfig/etc/mail/cf/cf/sendmail.cf.gen file as /etc/mail/sendmail.cf.
Nov 19 15:13:07 HOSTNAME /sbin/init.d/sendmail[11536]: - Change the /etc/rc.config.d/mailservs file accordingly.
Nov 19 15:13:07 HOSTNAME /sbin/init.d/sendmail[11536]: - Restart Sendmail.


in /etc/mail/sendmail.cf change the following (or similar line)

from:
O DaemonPortOptions=Port=smtp,Addr=127.0.0.1,Name=MTA

to:
O DaemonPortOptions=Name=MTA

then restart sendmail:   /sbin/init.d/sendmail start     it should start fine.

Alltel and Sprint mobile broadband

Windows XP
Pantech PX-500

to get on alltel evdo from certain areas, I needed to choose the following settings:

mode: EVDO
roaming: AUTO  unchecking Roam guard
important:  eject and plug card at least once

It seems important to eject/reinsert the card to get it to connect.  It also took a long time (20+ seconds) when opening connection manager after inserting the card for the first time; searching for service, connecting/disconnecting automatically until it connected to an EVDO signal on the alltel network.

HP-UX 11.23 to 11.31 update

some of my notes:
agile:
ioscan option -m (mapping)
-m hwpath -H $hw_path  -- shows hardware paths
-m lun  -H $hw_path   -- show agile addressing
-m dsf $device_file  -- maps legacy to agile


upgrading from v2 to v3 will leave legacy references in lvmtab, etc.. to fix:
vgscan -N  or  vgdsf
NOT necessary, but optional:
rmsf -L  insf -L   --  removes or installs legacy device files from box


iofind command scans ascii files and converts legacy to agile addresses

use motorola phone as tethered modem on verizon network

motorola vu204 drivers

download motorola drivers at http://motorola.com

create DUN connection using only PAP for security

username:  10_digit_phone_number@vzw3g.com

password:  vzw

domain:  blank

number to dial:#777

might need reboot phone first.

Backtick grave accent ` iPhone

The backtick (grave accent) ` character is missing from the iPhone and iPod touch normal keyboard layouts. ( as of OS 3.0 ) To use it, go into the mail app and in the email to/cc/bcc fields you should see the backtick in the upper left on the symbols virtual keyboard. Then just copy and paste it wherever you need it.

It might be helpful if a bunch of us complained about this missing key on the iPhone and iPod touch keyboards - leave feedback about the missing backtick/grave accent character at: http://www.apple.com/feedback/iphone.html

Really stupid for them to have it on the email address fields even though it's an invalid char for email addresses.

password aging field

http://www.tech-faq.com/password-aging.shtml
http://www.cse.ohio-state.edu/~mamrak/CIS762/unix_encryption_tut.html


On non-trusted systems password aging is stored as part of the encrypted password each user's account in the system's password file.  The password field, which is the second field is divided in two by a comma.  The first portion, characters 1-13, is the encrypted password.  The second portion, after the comma (characters 15-18), is the password aging field for that account.
password aging field (characters 15-18) breakdown:
character 1: max weeks password is valid before expiration
character 2: min weeks password before password can change
remaining characters: last password change (in number of weeks since 1/1/1970)

the characters are Base-64, so it's kind of tricky.  See the above links for a conversion table for Base64.

calculate:
,N/TT

N = 25 weeks, 175 days max password lifetime
/ = 1 week, 7 days miniumum password before changing
S = 30
T = 31
31 * 64 = 1984
1984 + 31 = 2050 weeks since January 1, 1970 = 08/07/08