Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Sendmail - issue within DMZ for some servers but not all Post 303032658 by bakunin on Thursday 21st of March 2019 10:54:30 AM
Old 03-21-2019
Quote:
Originally Posted by dakelly
I have updated the sendmail.cf to point to the mail server
Code:
define(`SMART_HOST',`MailServer.domain')dnl

Just to make sure: you do have compiled the sendmail.cf afterwards, yes? Sendmail only uses the compiled form of its configuration file, not the cleartext file itself.

And, while you are at it: can you post the version of sendmail you use? I have no idea which one is included in Ubuntu...

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Linux mail servers benchmarks (Qmail, Sendmail,Postfix)

New Linux mail servers benchmarks website. Check out http://benchmarks.dmz.ro . (0 Replies)
Discussion started by: cipango
0 Replies

2. Linux

Sendmail issue

Hi gurus! I need help to make sendmail to accept unknown user mail. That is if the user does not exist sendmail keep on processing the mail and store it in a some mailbox ... Thanks for any idea! (5 Replies)
Discussion started by: andryk
5 Replies

3. Solaris

sendmail issue

Hi, yesterday I had issues, sendmail was not responding quickly while sending email and users did not receive any email, This happened with sendmail on solaris 10 and also with sendmail on a linux box. Found it is something to do with DNS blacklists, following lists did not work for me,... (2 Replies)
Discussion started by: upengan78
2 Replies

4. UNIX for Dummies Questions & Answers

Issue with sendmail

Hi Team, I have a script written to sendmail along with attachment in html format. The code is export MAILFROM="abc@abc.com" export MAILTO="abc@abc.com" export CONTENT="./GRP_SPI_ERR.html" export SUBJECT="TEST EMAIL: TESTING HTML" { print - "From: $MAILFROM" print - "To: ${MAILTO}"... (3 Replies)
Discussion started by: Vinaykumar1
3 Replies

5. Solaris

Sendmail Issue

Hi, Guru i had configure in my two server to send out the email. One of the server able to send in the reasonable timing. but another not, it delay almost one day or two days but mostly not send at all. below is the syslog when i try to send out the mail. GOOD Server Dec 28 11:29:39... (5 Replies)
Discussion started by: SmartAntz
5 Replies

6. Solaris

Sendmail issue

Hi all, we are using solaris 10. we need to increase every users mail boxes size as all users mail boxes got filled..Please help..its urgent.. Thanks in advance.. (1 Reply)
Discussion started by: bpsunadm
1 Replies

7. Red Hat

Sendmail Issue.

Hi Gurus, I have been tampering around with sendmail for the past one week and seem to make little progress. Given below is an abstract of the issue. I have a Fedora 12 server(A VM on vitual Box bridged with a Windows XP host) which has to act as a SMTP server and have accordingly put up the... (8 Replies)
Discussion started by: Hari_Ganesh
8 Replies

8. Red Hat

Sendmail issue

Hi Every One, one of our server configuration on sendmail config we are using SMAR_HOST ### define(`SMART_HOST', 'mail.xxx.com') and /etc/sysconfig/sednmail DAEMON is setted to NO so let me know why sendmail is not working for this server any this else u need please do let me know (0 Replies)
Discussion started by: venikathir
0 Replies

9. Emergency UNIX and Linux Support

Sendmail issue

Hi, I'm using sendmail version 8.13.8-8.1.el5_7. I'm pretty new to it. The servera are running RHEL 5.8. My question basically is that I would want to know is there a way to change the from address. I would be able to change it using the return address in mailx command. However I would like to... (3 Replies)
Discussion started by: maverick_here
3 Replies

10. Red Hat

Sendmail issue

Dear All , I have some problem in Sendmail , where it was sending mails perfectly fine with the Ip address of the client machine. But suddenly there was an issue , the SMTP takes the IP of the bond1 interface. So the IP could not get validated in the relay server. So how should i send... (1 Reply)
Discussion started by: jegaraman
1 Replies
PBUILDER-DIST(1)					      General Commands Manual						  PBUILDER-DIST(1)

NAME
pbuilder-dist, cowbuilder-dist - multi-distribution pbuilder/cowbuilder wrapper SYNOPSIS
pbuilder-dist distribution [architecture] operation [options] [...] cowbuilder-dist distribution [architecture] operation [options] [...] DESCRIPTION
pbuilder-dist is a wrapper that makes it easy to use pbuilder with many different versions of Ubuntu and/or Debian. It is common to symlink this script in order to give it many names in the form of pbuilder-distribution or pbuilder-distribution-architec- ture, like for example pbuilder-feisty, pbuilder-sid, pbuilder-gutsy-i386, etc. The same applies to cowbuilder-dist, which uses cowbuilder. The main difference between both is that pbuilder compresses the created chroot as a a tarball, thus using less disc space but needing to uncompress (and possibly compress) its contents again on each run, and cowbuilder doesn't do this. USAGE
There are many arguments listed on the synopsis; each of them, if used, has to be used exactly in the same order as it appears there. In case you renamed the script to pbuilder-distribution, do not use the distribution parameter; same with i386 / amd64 if the name also con- tains -architecture. distribution Replace this with the codename of the version of Ubuntu or Debian you want to use. architecture This optional parameter will attempt to construct a chroot in a foreign architecture. For some architecture pairs (e.g. i386 on an amd64 install), the chroot will be created natively. For others (e.g. armel on an i386 install), qemu-user-static will be used. Note that some combinations (e.g. amd64 on an i386 install) require special separate kernel handling, and may break in unexpected ways. operation Replace this with the action you want pbuilder to do (create, update, build, clean, login or execute). If you don't specify any action, but the next argument is a .dsc file, it will assume that it should build. Check its manpage for more details. [...] Replace this with other parameters, if needed. For example, if build is the option, you will need to also specify a .dsc file. As a special feature, if you specify a .dsc file you can skip the build option and this script will automatically assume that building is the action you want to do. OPTIONS
--main-only (deprecated: mainonly) If you specify this option, only packages from the main (in Debian) or main and restricted (in Ubuntu) components will be used. By default, all official components are enabled. This only has effect when creating a new environment. --debug-echo The generated pbuilder/cowbuilder command will be printed to the standard output instead of being executed. This is useful for debugging. --buildresult DIRECTORY (pbuilder-dist only) If this option is specified, the resultant files of the pbuilder build are placed in DIRECTORY. --release-only Only use the release pocket. Default for development releases. --security-only Only use the release and security pockets. Suitable environment for preparing security updates. --updates-only Only use the release, security, and updates pocket. Not the proposed-updates pocket. EXAMPLES
pbuilder-dist gutsy create Creates a pbuilder environment for Ubuntu Gutsy, with all components enabled. pbuilder-sid --main-only create Creates a pbuilder environment for Debian Sid, with only the main component. pbuilder-feisty build ./sample_1.0-0ubuntu1.dsc Builds the specified package on an already existing Ubuntu Feisty environment. pbuilder-dist feisty withlog build ./sample_1.0-0ubuntu1.dsc Same as above, but stores pbuilder's output on a file. pbuilder-etch i386 update Updates an existing i386-architecture Debian Etch environment on an amd64 system. cowbuilder-experimental create Creates a cowbuilder environment for Debian Experimental. FILES AND ENVIRONMENT VARIABLES
By default, pbuilder-dist will store all the files it generates in ~/pbuilder/. This can be changed by setting the PBUILDFOLDER environment variable. If the directory doesn't exist, it will be created on the run. A file with the log of the last operation, called last_operation.log, will be saved in the results subdirectory of each build environment. The default authentication method is sudo. You can change this by setting the PBUILDAUTH variable. By default, pbuilder-dist use the master Debian and Ubuntu mirrors. The pbuilder MIRRORSITE and OTHERMIRROR variables are supported, as are the standard ubuntu-dev-tools variables: UBUNTUTOOLS_DEBIAN_MIRROR, PBUILDER_DIST_DEBIAN_MIRROR, UBUNTUTOOLS_DEBSEC_MIRROR, PBUILDER_DIST_DEBSEC_MIRROR, UBUNTUTOOLS_UBUNTU_MIRROR, PBUILDER_DIST_UBUNTU, UBUNTUTOOLS_UBUNTU_PORTS_MIRROR, and PBUILDER_DIST_UBUNTU_PORTS_MIRROR. See ubuntu-dev-tools (5) for details. You may also want to know that pbuilder-dist exports DIST and ARCH environment variables to the invoked process, containing the name of the distribution and the architecture targeted by the current build. You can make use of them, for example, in pbuilderrc. BUGS
If you experience any problem with this script contact me on rainct@ubuntu.com or file a bug at https://bugs.launch- pad.net/ubuntu/+source/ubuntu-dev-tools. Please ensure first that the problem is really this script and not an issue with pbuilder or cowbuilder themselves. SEE ALSO
pbuilder(1), pbuilderrc(5), cowbuilder(1), ubuntu-dev-tools(5). AUTHORS
pbuilder-dist and this manual page were written by Siegfried-A. Gevatter <rainct@ubuntu.com>, with contributions from Iain Lane <iain@orangesquash.org.uk>, Emmet Hikory <persia@ubuntu.com> and others. pbuilder-dist is released under the GNU General Public License, version 2 or later. ubuntu-dev-tools January 10, 2008 PBUILDER-DIST(1)
All times are GMT -4. The time now is 05:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy