Sponsored Content
Operating Systems Linux Red Hat Zimbra Mail Server Security Issue Post 302865361 by jgt on Friday 18th of October 2013 08:16:00 AM
Old 10-18-2013
You would be far better off to post your question on the Zimbra forum Zimbra :: Forums
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

can not send mail from unix server to company/yahoo mail

hi, Gurus, I need some help with sending mail out from my UNIX server: It is running Solaris 2.6 and the sendmail version is 8.8. Output of :/usr/lib/sendmail -d0.1 -bt < /dev/null Version 8.8.8+Sun Compiled with: LOG MATCHGECOS MIME7TO8 MIME8TO7 NAMED_BIND NDBM NETINET ... (5 Replies)
Discussion started by: b5fnpct
5 Replies

2. Red Hat

not able to Send mail due to Security Issue

Hi All, I am trying to send a mail from my application through SMTP in solaris 9 but unable to send a mail.Same code is able to send mail in Windows. As unix has more security,So as per me,it is due to security reason.. So please let me know what I need to do to send a mail properly. what... (5 Replies)
Discussion started by: smartgupta
5 Replies

3. HP-UX

[Solved] How do I configure Unix Mail Server to use another Mail Exchange Server

We have configured our mail unix server and can send out emails automatically from applications running on unix to different people in our company as well as outside our company. However there is an outside client who is not receiving these emails because the settings on their mail server cannot... (4 Replies)
Discussion started by: Tenyhwa
4 Replies

4. UNIX for Advanced & Expert Users

need to configure mail setting to send mail to outlook mail server

i have sun machines having solaris 9 & 10 OS . Now i need to send mail from the machines to my outlook account . I have the ip adress of OUTLOOK mail server. Now what are the setting i need to do in solaris machines so that i can use mailx or sendmail. actually i am trying to automate the high... (2 Replies)
Discussion started by: amitranjansahu
2 Replies

5. Solaris

Server Mail Issue

Solaris server does not receive email from other servers any more. For example, If we send mail from server A to server B, mail is not reaching server B and there is no message or warning about failure of sending mail in server A. What may be the issue of this? Thankyou in advance!! (1 Reply)
Discussion started by: learner46
1 Replies

6. UNIX Desktop Questions & Answers

Outlook Mail Rule issue- not reaching the unix server

Hi All, I' m having a pretty strange issue, when I sent an outlook email that is forwarded by rule for example (email sent every day at certain time) to the server is not going through, i cant see it arriving at the Maildir or i have also a procmail rule log that also not reaching... could... (0 Replies)
Discussion started by: Skyline88
0 Replies

7. UNIX for Advanced & Expert Users

Fetchmail multidrop mode to work with Zimbra server

Hi, We want to setup a multidrop configuration with our Zimbra server. Please help us to setup a .fetchmailrc file. We are using Fetmail 6.3.9 version. Single mails are fetching without any problems. What are the things to take care while setting up a multidrop? POP server: mail.company.com... (0 Replies)
Discussion started by: brittocj
0 Replies

8. UNIX for Dummies Questions & Answers

Minimal Mail Server Setup for Local Mail Transfer

I am trying to get stored mail out of an old mail client. I figured that the easiest way to do it is with IMAP by logging in with both clients. I can copy the mail to the server from the old mail client, and back down into the new mail client. Rather than using a real mail account on the... (2 Replies)
Discussion started by: nixie
2 Replies

9. Solaris

OutBound SMTP Server Mail issue

Hi all I have a Live SMTP server for outbound mails ( Mail being sent from my organization to outside domains). A large chunk of mails are not being sent and reside in /var/spool/mqueue directory. The header of there mails are: From: Mail Delivery Subsystem <MAILER-DAEMON> How can I... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies
Mail::Transport::Receive(3pm)				User Contributed Perl Documentation			     Mail::Transport::Receive(3pm)

NAME
Mail::Transport::Receive - receive messages INHERITANCE
Mail::Transport::Receive is a Mail::Transport is a Mail::Reporter Mail::Transport::Receive is extended by Mail::Transport::IMAP4 Mail::Transport::POP3 SYNOPSIS
my $receiver = Mail::Transport::POP3->new(...); my $message = $receiver->receive($id); DESCRIPTION
Each object which extends Mail::Transport::Receive implement a protocol which can get messages into your application. The internals of each implementation can differ quite a lot, so have a look at each separate manual page as well. Current message receivers: o Mail::Transport::POP3 Implements the POP3 protocol. See also Mail::Box::POP3. METHODS
Constructors Mail::Transport::Receive->new(OPTIONS) See "METHODS" in Mail::Transport Receiving mail $obj->receive([UNIQUE-MESSAGE-ID]) Receive one message from the remote server. Some receivers will provide the next message automatically, other are random access and use the specified ID. Server connection $obj->findBinary(NAME [, DIRECTORIES]) See "Server connection" in Mail::Transport $obj->remoteHost() See "Server connection" in Mail::Transport $obj->retry() See "Server connection" in Mail::Transport Error handling $obj->AUTOLOAD() See "Error handling" in Mail::Reporter $obj->addReport(OBJECT) See "Error handling" in Mail::Reporter $obj->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK]) Mail::Transport::Receive->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK]) See "Error handling" in Mail::Reporter $obj->errors() See "Error handling" in Mail::Reporter $obj->log([LEVEL [,STRINGS]]) Mail::Transport::Receive->log([LEVEL [,STRINGS]]) See "Error handling" in Mail::Reporter $obj->logPriority(LEVEL) Mail::Transport::Receive->logPriority(LEVEL) See "Error handling" in Mail::Reporter $obj->logSettings() See "Error handling" in Mail::Reporter $obj->notImplemented() See "Error handling" in Mail::Reporter $obj->report([LEVEL]) See "Error handling" in Mail::Reporter $obj->reportAll([LEVEL]) See "Error handling" in Mail::Reporter $obj->trace([LEVEL]) See "Error handling" in Mail::Reporter $obj->warnings() See "Error handling" in Mail::Reporter Cleanup $obj->DESTROY() See "Cleanup" in Mail::Reporter $obj->inGlobalDestruction() See "Cleanup" in Mail::Reporter DIAGNOSTICS
Warning: Avoid program abuse: specify an absolute path for $exec. Specifying explicit locations for executables of email transfer agents should only be done with absolute file names, to avoid various pontential security problems. Warning: Executable $exec does not exist. The explicitly indicated mail transfer agent does not exists. The normal settings are used to find the correct location. Error: Package $package does not implement $method. Fatal error: the specific package (or one of its superclasses) does not implement this method where it should. This message means that some other related classes do implement this method however the class at hand does not. Probably you should investigate this and probably inform the author of the package. SEE ALSO
This module is part of Mail-Box distribution version 2.105, built on May 07, 2012. Website: http://perl.overmeer.net/mailbox/ LICENSE
Copyrights 2001-2012 by [Mark Overmeer]. For other contributors see ChangeLog. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html perl v5.14.2 2012-05-07 Mail::Transport::Receive(3pm)
All times are GMT -4. The time now is 11:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy