mail issues on SCO_SV 5.0.6


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers mail issues on SCO_SV 5.0.6
# 1  
Old 06-17-2004
mail issues on SCO_SV 5.0.6

I am very new to unix and I am trying to get a Sco Server setup to send outgoing email. I know that SCO uses MMDF and i have configured it to use TCP/IP and UUCP, but I never receive any of the emails I send to my exchange server. I don't have this problem on any of the Linux systems I use. Anyone know of something I might be missing? Maybe something about configuring UUCP? The documentation I've found for UUCP wasn't very clear, so I don't know if something needs to be configured in that respect. Thanks for your help.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Mail Format Issues

Hi All, I 'm trying to find a way to send my contents of a file as a body of email in the format shown below. However, the format of the contents are messed up when I receive the email. ---------------------------------------------------------------------------------------------------------... (2 Replies)
Discussion started by: shash
2 Replies

2. UNIX for Dummies Questions & Answers

Issues in sending mail with attachements

Hi I am using the below command to send mail from unix with body as well as attachment. But the attachment is in encoded form in the body itself. I am not receiving as attachment: (cat body_success.txt;uuencode Log.txt Log.txt)| mailx -s "success" $ToID I am receiving... (5 Replies)
Discussion started by: pandeesh
5 Replies

3. UNIX for Dummies Questions & Answers

issues in sending mail

Hi, i am trying the below script for sending mail. if then count=`cat $sfile|wc -l` echo "There are $count abends.Please take care " > body.txt (cat body.txt;uuencode $sfile $sfile) | mailx -s "Alert:there are failures" pandeesh@gmail.com fi In the mail, i am getting like: ... (4 Replies)
Discussion started by: pandeesh
4 Replies

4. AIX

/var/spool/mail/ issues

Hi My box is running with AIX 6100-06 and Im the root user of this box My /var gets filled up often to 100% When I investigate I find that it is the below file which increases rapidly /var/spool/mail/pdgadmin I dont know why this file is growing up. Can any one assist me on this.... (2 Replies)
Discussion started by: samsungsamsung
2 Replies

5. SCO

Mounting a USB DRIVE- SCO_SV

I wish to mount a USB pen drive to allow me copy files from the pc to the pen drive. when I insert the dirve I get a message umass Attached: Kingston DataTraveler 2.0, rev 2.0, usb_id 2 The version of unix is SCO_SV. I cannot see any new file in the /dev folder. I was looking for... (5 Replies)
Discussion started by: ralph2010
5 Replies

6. UNIX for Dummies Questions & Answers

Line Count & MAil Issues

Please help...I forgot how to do a linecount in Solaris. I'm list a report & I'm trying to count how many instances. Also, I need to read & clean up mail for root. What directory is that again. Thanks (3 Replies)
Discussion started by: Remi
3 Replies

7. UNIX for Dummies Questions & Answers

netscape mail issues

Don't know if this is too in-depth for the ".. Dummies .." forum, but I figured I'd try this one first. I have a file from a client that I need to save to our UNIX server. If the file is sent as an email attachment from UNIX (via command line or Twiggi Mail), the following occurs: if the... (0 Replies)
Discussion started by: jumpinfallout
0 Replies
Login or Register to Ask a Question
Jifty::Notification(3pm)				User Contributed Perl Documentation				  Jifty::Notification(3pm)

NAME
Jifty::Notification - Send emails from Jifty USAGE
It is recommended that you subclass Jifty::Notification and override "body", "html_body", "subject", "recipients", and "from" for each message. (You may want a base class to provide "from", "preface" and "footer" for example.) This lets you keep all of your notifications in the same place. However, if you really want to make a notification type in code without subclassing, you can create a "Jifty::Notification" and call the "set_body", "set_subject", and so on methods on it. METHODS
new [KEY1 => VAL1, ...] Creates a new Jifty::Notification. Any keyword args given are used to call set accessors of the same name. Then it calls "setup". setup Your subclass should override this to set the various field values. send_one_message Delivers the notification, using the Email::Send mailer defined in the "Mailer" and "MailerArgs" configuration arguments. Returns true if mail was actually sent. Note errors are not the only cause of mail not being sent -- for example, the recipients list could be empty. If you wish to send HTML mail, set "html_body". If this is not set (for backwards compatibility) a plain-text email is sent. If "html_body" and "body" are both set, a multipart mail is sent. See Email::MIME::CreateHTML for how this is done. Be aware that if you haven't set "recipients", this will fail silently and return without doing anything useful. set_headers MESSAGE Takes a Email::MIME object "MESSAGE", and modifies it as necessary before sending it out. As the method name implies, this is usually used to add or modify headers. By default, does nothing; this method is meant to be overridden. body [BODY] Gets or sets the body of the notification, as a string. subject [SUBJECT] Gets or sets the subject of the notification, as a string. from [FROM] Gets or sets the from address of the notification, as a string. recipients [RECIPIENT, ...] Gets or sets the addresses of the recipients of the notification, as a list of strings (not a reference). email_from OBJECT Returns the email address from the given object. This defaults to calling an 'email' method on the object. This method will be called by "send" to get email addresses (for "to") out of the list of "recipients". to_list [OBJECT, OBJECT...] Gets or sets the list of objects that the message will be sent to. Each one is sent a separate copy of the email. If passed no parameters, returns the objects that have been set. This also suppresses duplicates. send Sends an individual email to every user in "to_list"; it does this by setting "to" and "recipient" to the first user in "to_list" calling Jifty::Notification's "send" method, and progressing down the list. Additionally, if "to" was set elsewhere, sends an email to that person, as well. to Of the list of users that "to" provided, returns the one which mail is currently being sent to. This is set by the "send" method, such that it is available to all of the methods that Jifty::Notification's "send" method calls. preface Print a header for the message. You want to override this to print a message. Returns the message as a scalar. footer Print a footer for the message. You want to override this to print a message. Returns the message as a scalar. full_body The main, plain-text part of the message. This is the preface, body, and footer joined by newlines. full_html Same as full_body, but with HTML. parts The parts of the message. You want to override this if you want to send multi-part mail. By default, this method returns a single part consisting of the result of calling "$self->full_body". Returns the parts as an array reference. magic_letme_token_for PATH Returns a Jifty::LetMe token which allows the current user to access a path on the site. perl v5.14.2 2011-01-26 Jifty::Notification(3pm)