On July 28, 2021 2:58:21 PM UTC, Viktor Dukhovni
wrote:
>If the postfix-files file does not reflect the content delivered by
>the package, you would typically see errors running "postfix check".
>Either the package should deliver all the files expected upstream,
>or the "postfix-files" file sh
If the postfix-files file does not reflect the content delivered by
the package, you would typically see errors running "postfix check".
Either the package should deliver all the files expected upstream,
or the "postfix-files" file should be updated to match the package
content.
--
Viktor.
On 2021-07-26 12:11:16 -0400, Viktor Dukhovni wrote:
[...]
> At which point the only files in /etc/postfix that are updated with
> each package release are:
>
> $config_directory/LICENSE:f:root:-:644:1
> $config_directory/TLS_LICENSE:f:root:-:644:1
> $config_directory/bounce.cf.default
On Mon, Jul 26, 2021 at 12:18:01PM +, Scott Kitterman wrote:
> >(it is listed in the postfix 3.6.1 tarball in conf/postfix-files:
> >"$meta_directory/makedefs.out:f:root:-:644"
>
> The Debian package management system tracks system induced changes in
> /etc and notifies users about them durin
On 2021-07-26 12:18:01 +, Scott Kitterman wrote:
[makedefs.out location]
> The Debian package management system tracks system induced changes in /etc
> and notifies users about them during package upgrade. Before I moved the
> file to /usr/share/postfix, there were alerts during package upgr
On July 26, 2021 8:59:00 AM UTC, Vincent Lefevre wrote:
>On 2021-07-24 09:29:04 +1000, raf wrote:
>> On Fri, Jul 23, 2021 at 04:13:00PM +0200, Jean-François Bachelet
>> wrote:
>>
>> > Hello ^^)
>> >
>> > I found that error in mail.log, at each start postfix issue that error :
>> >
>> > 'Ju
On 2021-07-24 09:29:04 +1000, raf wrote:
> On Fri, Jul 23, 2021 at 04:13:00PM +0200, Jean-François Bachelet
> wrote:
>
> > Hello ^^)
> >
> > I found that error in mail.log, at each start postfix issue that error :
> >
> > 'Jul 23 15:36:57 discovery postfix/postfix-script[1170]: warning: symlin
On Fri, Jul 23, 2021 at 04:13:00PM +0200, Jean-François Bachelet
wrote:
> Hello ^^)
>
> I found that error in mail.log, at each start postfix issue that error :
>
> 'Jul 23 15:36:57 discovery postfix/postfix-script[1170]: warning: symlink
> leaves directory: /etc/postfix/./makedefs.out'
>
> i
Jean-Fran?ois Bachelet:
> Hello ^^)
>
>
> I found that error in mail.log, at each start postfix issue that error :
>
>
> 'Jul 23 15:36:57 discovery postfix/postfix-script[1170]: warning:
> symlink leaves directory: /etc/postfix/./makedefs.out'
>
>
> is that warning harmless or not ?
As a ma
Hello ^^)
I found that error in mail.log, at each start postfix issue that error :
'Jul 23 15:36:57 discovery postfix/postfix-script[1170]: warning:
symlink leaves directory: /etc/postfix/./makedefs.out'
is that warning harmless or not ?
Jeff
On 13.06.20 23:42, olivier wrote:
I'm trying to configure postfix as internet site. The vm (centos) is
under proxmox, and behind pfsense (fw). tcp/587 ; tcp/25 are reachable
from the internet. When I try to send an email from outside to a user
on this server, the /var/log/maillog shows the error
* olivier:
> Can you help ?
See http://www.postfix.org/DEBUG_README.html , in particular the
"Reporting problems" section.
-Ralph
Hello,
I'm trying to configure postfix as internet site. The vm (centos) is
under proxmox, and behind pfsense (fw). tcp/587 ; tcp/25 are reachable
from the internet. When I try to send an email from outside to a user
on this server, the /var/log/maillog shows the error :
"mail for mail.mydomain.fr
On 14.05.20 09:07, SysAdmin EM wrote:
I have two servers running on Postfix, one of which runs version 2.10.1 and
the other server runs version 3.4.7.
On the server where I am running verion 3.4.7, I receive "501 5.5.4 Invalid
domain name" errors in emails sent to different servers. Rhe mail is
On Thu, May 14, 2020 at 09:07:29AM -0300, SysAdmin EM wrote:
> postfix-out/smtp[12931]: E30639204ED: to=,
> relay=hotmail-com.olc.protection.outlook.com[104.47.124.33]:25,
> delay=1.4, delays=0.08/0/1.4/0, dsn=5.5.4, status=bounced
> (host hotmail-com.olc.protection.outlook.com[104.47.124.33]
> re
Hello,
I have two servers running on Postfix, one of which runs version 2.10.1 and
the other server runs version 3.4.7.
On the server where I am running verion 3.4.7, I receive "501 5.5.4 Invalid
domain name" errors in emails sent to different servers. Rhe mail is sent
to postfix through exim fro
On 14 Jul 2019, at 20:49, Viktor Dukhovni wrote:
> On Sun, Jul 14, 2019 at 07:51:11PM -0600, @lbutlr wrote:
>>-o smtpd_milters=
>>-o milter_connect_macros=
>>-o milter_macro_daemon_name=ORIGINATING
>>
>> That is likely where you are going to run into the most issues.
>
> No. DKIM si
On Sun, Jul 14, 2019 at 07:51:11PM -0600, @lbutlr wrote:
> You should not have permit_mynetworks anywhere, reject_non_fqdn_sender
> should do absolutely nothing if your system is setup properly. I have
> opinions on reject_sender_login_mismatch, but I don’t know that it would
> be a problem here.
> On 14 Jul 2019, at 17:25, David Mehler wrote:
>
> Hello Viktor,
>
> Thanks for your reply. Is my configuration overdoing it?
>
> Here's my submission snipet:
> submission inet n - n - - smtpd
> -o syslog_name=postfix/submission
> -o smtpd_tls_security_level=en
On Sun, Jul 14, 2019 at 07:25:05PM -0400, David Mehler wrote:
> Thanks for your reply. Is my configuration overdoing it?
No, on the contrary, you're still missing some overrides:
> Here's my submission snipet:
> submission inet n - n - - smtpd
> -o syslog_name=post
Hello Viktor,
Thanks for your reply. Is my configuration overdoing it?
Here's my submission snipet:
submission inet n - n - - smtpd
-o syslog_name=postfix/submission
-o smtpd_tls_security_level=encrypt
-o smtpd_sasl_auth_enable=yes
-o smtpd_sasl_type=doveco
On Sun, Jul 14, 2019 at 05:41:14PM -0400, David Mehler wrote:
> I've got a postfix virtual domain setup in a freebsd jail. A separate
> jail holds the webmail server. This is version 3.4.5 of Postfix. I've
> got spf, and am trying to send out a test email. This is what I'm
> getting:
>
> Jul 14 1
Hello,
I've got a postfix virtual domain setup in a freebsd jail. A separate
jail holds the webmail server. This is version 3.4.5 of Postfix. I've
got spf, and am trying to send out a test email. This is what I'm
getting:
Jul 14 17:28:04 mail postfix/submission/smtpd[6855]: connect from
webserver
Emanuel:
[ Charset windows-1252 converted... ]
> Hello, i see this error:
>
> Apr 16 13:13:51 host02 postfix/smtpd[32761]: warning: problem talking to
> server 127.0.0.1:20040: Connection timed out
> Apr 16 13:13:52 host02 postfix/smtpd[32491]: warning: problem talking to
> server 127.0.0.1:2004
Hello, i see this error:
Apr 16 13:13:51 host02 postfix/smtpd[32761]: warning: problem talking to
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:52 host02 postfix/smtpd[32491]: warning: problem talking to
server 127.0.0.1:20040: Connection timed out
Apr 16 13:13:53 host02 postfix/smt
s delivering messages to user
> inboxes with this message:
>
> Jun 8 19:37:05 mx01 postfix/error[22985]: 7B867836338F:
> to=, relay=none, delay=295,
> delays=0.49/294/0/0.05, dsn=4.4.2, status=deferred (delivery
> temporarily suspended: conversation with 127.0.0.1[127.0.0.1] timed
>
19:37:05 mx01 postfix/error[22985]: 7B867836338F:
to=, relay=none, delay=295, delays=0.49/294/0/0.05,
dsn=4.4.2, status=deferred (delivery temporarily suspended: conversation
with 127.0.0.1[127.0.0.1] timed out while receiving the initial server
greeting)
For whatever reason it appears that
On 10.04.2017 18:33, James B. Byrne wrote:
>
> On Mon, April 10, 2017 11:29, Wietse Venema wrote:
>> James B. Byrne:
>>> The issue seems to be some sort of time-out with the Amavis proxy.
>>> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
>>> timeout talking to proxy 127.0.0.1
James B. Byrne:
[ Charset ISO-8859-1 converted... ]
>
> On Mon, April 10, 2017 11:29, Wietse Venema wrote:
> > James B. Byrne:
> >> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
> >> timeout talking to proxy 127.0.0.1:10024
> >> 67 Apr 8 10:50:27 inet08 postfix-p25/smtpd[
On Mon, April 10, 2017 11:29, Wietse Venema wrote:
> James B. Byrne:
>> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
>> timeout talking to proxy 127.0.0.1:10024
>> 67 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]:
>> proxy-reject:
>> END-OF-MESSAGE: 451 4.3.0 Error: que
James B. Byrne:
> 66 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: warning:
> timeout talking to proxy 127.0.0.1:10024
> 67 Apr 8 10:50:27 inet08 postfix-p25/smtpd[18374]: proxy-reject:
> END-OF-MESSAGE: 451 4.3.0 Error: queue file write error; from=
> to= proto=ESMTP helo=
The spam
We continue to receive messages addressed to Postmaster from our MX
host. All appear to be related to a single original transmission.
The issue seems to be some sort of time-out with the Amavis proxy.
Is there some way of determining exactly what is wrong with this
specific sender's message?
T
On 5 May 2016, at 22:24, Bill Cole wrote:
[ blah blah blah ]
OR: I was entirely wrong about the broken SPF records being the cause of
that rejection.
Noel & Christian were right in pointing you at the access maps. You
MIGHT also run into the SPF issue after exempting that sender from the
sh
On Thu, May 05, 2016 at 10:24:49PM -0400, Bill Cole wrote:
> >I discovered this issue in their DNS with respect to SPF:
> >
> >;; ANSWER SECTION:
> >lymanworldwide.com. 1800IN TXT "v=spf1
> >include:netcore.co.in -all"
> >lymanworldwide.com. 1800IN TXT "v=spf1
> >
On 5 May 2016, at 11:57, James B. Byrne wrote:
On Thu, May 5, 2016 11:34, James B. Byrne wrote:
Can anyone clue me in on what configuration issue might be causing
this and whose configuration it is, mine or theirs?
postfix-p25/smtpd[18149]: NOQUEUE: reject: RCPT from
smout-245174.nsmailserv.co
On Thu, May 5, 2016 12:37, Christian Kivalo wrote:
>
> There it is: lymanworldwide.com uses nameservices provided by
> name-services.com
>
Thanks, that is it. I suppose we will just have to explicitly permit
them in. Not that I approve of their choice of registrars (enom).
Thanks for the help.
Am 5. Mai 2016 18:30:40 MESZ, schrieb "James B. Byrne" :
>
>On Thu, May 5, 2016 12:11, Christian Kivalo wrote:
>>
>>
>> Am 5. Mai 2016 17:34:36 MESZ, schrieb "James B. Byrne"
>> :
>>>Can anyone clue me in on what configuration issue might be causing
>>>this and whose configuration it is, mine or
On Thu, May 5, 2016 12:11, Christian Kivalo wrote:
>
>
> Am 5. Mai 2016 17:34:36 MESZ, schrieb "James B. Byrne"
> :
>>Can anyone clue me in on what configuration issue might be causing
>>this and whose configuration it is, mine or theirs?
>>
>>postfix-p25/smtpd[18149]: NOQUEUE: reject: RCPT from
>
On 5/5/2016 10:34 AM, James B. Byrne wrote:
> Can anyone clue me in on what configuration issue might be causing
> this and whose configuration it is, mine or theirs?
>
> postfix-p25/smtpd[18149]: NOQUEUE: reject: RCPT from
> smout-245174.nsmailserv.com[202.162.245.174]: 450 4.7.1
> : Sender addre
Am 5. Mai 2016 17:34:36 MESZ, schrieb "James B. Byrne" :
>Can anyone clue me in on what configuration issue might be causing
>this and whose configuration it is, mine or theirs?
>
>postfix-p25/smtpd[18149]: NOQUEUE: reject: RCPT from
>smout-245174.nsmailserv.com[202.162.245.174]: 450 4.7.1
>: Sen
try use "~all" instead of "-all" in your SPF txt record.
On 16-05-05 08:57 AM, James B. Byrne wrote:
On Thu, May 5, 2016 11:34, James B. Byrne wrote:
Can anyone clue me in on what configuration issue might be causing
this and whose configuration it is, mine or theirs?
postfix-p25/smtpd[18149
On Thu, May 5, 2016 12:01, Gao wrote:
> try use "~all" instead of "-all" in your SPF txt record.
>
We are not the sender. We are the recipient. Our SPF record does not
bear on this issue insofar as I can see. In any case, our SPF TXT RR
already includes ~all, not -all.
--
*** e-Mail
On Thu, May 5, 2016 11:34, James B. Byrne wrote:
> Can anyone clue me in on what configuration issue might be causing
> this and whose configuration it is, mine or theirs?
>
> postfix-p25/smtpd[18149]: NOQUEUE: reject: RCPT from
> smout-245174.nsmailserv.com[202.162.245.174]: 450 4.7.1
> : Sender
Can anyone clue me in on what configuration issue might be causing
this and whose configuration it is, mine or theirs?
postfix-p25/smtpd[18149]: NOQUEUE: reject: RCPT from
smout-245174.nsmailserv.com[202.162.245.174]: 450 4.7.1
: Sender address rejected: Access denied;
from= to=
proto=ESMTP helo=
Austin Einter:
> > Used netstat -tap and the output is
> > tcp0 0 *:9876 *:*
> > LISTEN 9306/mysqld
That is port 9876. What TCP port did you configure POSTFIX connect to?
Wietse
Looks resolved, need to verify though...
port= line not required
hosts=127.0.0.1:9876 , this is what working looks...
Any idea whats the difference between these 2 config styles.
If I want to send a test mail from terminal.., how can I do that ..., any
simple command or link to follow pls share
Seems you're using non-standard port for mysql (9306).
If I'm not wrong, mysql use port 3306...
$ cat /etc/services|grep 3306
mysql 3306/tcp
mysql 3306/udp
> Hi Paul
> Thanks.
>
> Used netstat -tap and the output is
> tcp0 0 *:9876 *:*
> LISTEN
Hi Paul
Thanks.
Used netstat -tap and the output is
tcp0 0 *:9876 *:*
LISTEN 9306/mysqld
>From ps -ef | grep mysql
mysql 9306 1 0 03:22 ?00:00:00 /usr/sbin/mysqld
More over, same mysql server I am using for web server purpose, and my site
is up
On Mon, Oct 20, 2014 at 12:38:25PM +0530, Austin Einter wrote:
> The final error I am getting when I start postfix is as below
>
> postfix/cleanup[8682]: warning: connect to mysql server 127.0.0.1: Can't
> connect to MySQL server on '127.0.0.1' (111)
>
> So it looks as a permission issue.
I woul
The final error I am getting when I start postfix is as below
postfix/cleanup[8682]: warning: connect to mysql server 127.0.0.1: Can't
connect to MySQL server on '127.0.0.1' (111)
So it looks as a permission issue.
I hope, postfix uses DB user/password given in alias-maps (in my case
/etc/postf
Hi Benny.
Thanks for help.
I modified below stuff.
1. In /etc/mysql/my.cnf , I had bind-address = 0.0.0.0 and changed it to
127.0.0.1
2. In postfix maps files, I did put socket = /var/run/mysqld/mysqld.sock
Then I restarted postfix.
Similar error, given below.
128250 Oct 20 01:50:50 Austin post
On October 20, 2014 5:08:08 AM Austin Einter wrote:
I did chorrt modification , no luck
Next I modified in maps config files , I changed the line
hosts = localhost
to
hosts = 127.0.0.1
Check my.cnf, your mysql only binds to socket not inet pr default
#skip-networking
bind-address = 127.
I did chorrt modification , no luck
Next I modified in maps config files , I changed the line
hosts = localhost
to
hosts = 127.0.0.1
After that I find below error
Oct 19 23:03:24 Kamal postfix/master[2336]: daemon started -- version
2.9.6, configuration /etc/postfix
Oct 19 23:03:24 Kamal pos
Austin Einter:
> 29617 Oct 19 13:33:37 Austin postfix/cleanup[2139]: warning: connect to
> mysql server localhost: Can't connect to local MySQL server through
> socke t '/var/run/mysqld/mysqld.sock' (2)
Error 2 means "No such file or directory".
As someone already posted here, is the MyqSQL
Can anybody help me in this pls ?
-- Forwarded message --
From: Austin Einter
Date: Sun, Oct 19, 2014 at 11:10 PM
Subject: Postfix Error in Ubuntu 12.04
To: postfix-users@postfix.org
Dear All
I am trying to setup postfix/dovecot in an Ubuntu 12.04 system.
Though I have
On 10/19/2014 12:41 PM, Austin Einter wrote:
> I have referred all the steps from
> https://www.digitalocean.com/community/tutorials/how-to-configure-a-mail-server-using-postfix-dovecot-mysql-and-spamassasin
>
> Thanks
> kamal
>
> On Sun, Oct 19, 2014 at 11:10 PM, Austin Einter
> mailto:austin.ein
I have referred all the steps from
https://www.digitalocean.com/community/tutorials/how-to-configure-a-mail-server-using-postfix-dovecot-mysql-and-spamassasin
Thanks
kamal
On Sun, Oct 19, 2014 at 11:10 PM, Austin Einter
wrote:
> Dear All
> I am trying to setup postfix/dovecot in an Ubuntu 12.04
Dear All
I am trying to setup postfix/dovecot in an Ubuntu 12.04 system.
Though I have installed postfix, dovecot and spamassin (with complete
configurations), when I start service postfix, in terminal it shows
everything fine.
In /var/log/mail.log and syslog I see below errors.
29615 Oct 19 13:
Johan Andersson
Cc: Postfix users
Subject: Re: SV: SV: Strange Postfix error
Johan Andersson:
> The problem was solved with a full server reboot (rebooting the
> zone where Postfix is running did not help).
> Strangebut I'm happy for now.
I found a similar problem with Linux on some
>
> -Ursprungligt meddelande-
> Fr?n: owner-postfix-us...@postfix.org
> [mailto:owner-postfix-us...@postfix.org] F?r Johan Andersson
> Skickat: den 20 januari 2012 16:05
> Till: Postfix users
> ?mne: SV: SV: Strange Postfix error
>
> Hi.
>
> The binari
ickat: den 20 januari 2012 16:05
Till: Postfix users
Ämne: SV: SV: Strange Postfix error
Hi.
The binaries used are compiled on a Solaris server and have been in use since
September 21st last year without any problems until yesterday when they
suddenly stopped working. I replaced them with the exact
Wietse Venema:
> Your symptoms indicate a mis-match between the IN-MEMORY master
> daemon process, and the ON-DISK executable files for smtpd, cleanup,
> etc.
Famous last words. This may be the result of a Linux "misfeature"
where a pipe inode number goes over 32bit:
http://bugs.debian.org/cgi-bi
Your symptoms indicate a mis-match between the IN-MEMORY master
daemon process, and the ON-DISK executable files for smtpd, cleanup,
etc.
To fix, see the suggestion at the end of my first reply. This is
my final response.
Wietse
stfix users
Ämne: Re: SV: Strange Postfix error
Johan Andersson:
> Hi
>
> Thanks for your answer.
>
> I don't think that's the answerbecause i haven't replaced anything
> really (well, apart from replacing the binaries with a copy of the
> ones that were a
Johan Andersson:
> Hi
>
> Thanks for your answer.
>
> I don't think that's the answerbecause i haven't replaced
> anything really (well, apart from replacing the binaries with a
> copy of the ones that were already running).
My reply was 100% about the consequences of replacing Postfix binar
s ?
I will try 2.8.7 compiled the same way as the present 2.8.5 to see if that
changes anything.
Br
Johan
-Ursprungligt meddelande-
Från: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
För Wietse Venema
Skickat: den 20 januari 2012 14:59
Till: Postfix users
Ä
Johan Andersson:
> Jan 19 23:56:21 servername postfix/cleanup[29089]: [ID 947731 mail.crit]
> fatal: fstat flow pipe write descriptor: Value too large for defined data type
The logging comes from this code fragment:
ssize_t mail_flow_get(ssize_t len)
{
const char *myname = "mail_
Le 14/09/2011 09:33, n3mesi83 a écrit :
>
> Hello everyone,
>
> I have a java web application that uses JavaMail to send messages with
> attached documents (spreadsheets). On the server (Ubuntu 10.4 64-bit) I
> installed postfix to send email. The server has a static address and I
> connect to it
> mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128 192.168.0.0/24
Your java app will only allowed to send via this postfix instance from
these IP ranges.
> When I configured postfix, in system mail name I specified
> mail.mydomain.comand as smtp in my java app I use
> mail.mydomain.com, s
Thank you for the answer!
this is may postconf:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
inet_interfaces = all
inet_protocols = all
mailbox_size_limit = 0
mydestination = Ubuntu-1004-lucid-64-minimal, local
* Ralf Hildebrandt :
> * n3mesi83 :
> >
> > Hello everyone,
> >
> > I have a java web application that uses JavaMail to send messages with
> > attached documents (spreadsheets). On the server (Ubuntu 10.4 64-bit) I
> > installed postfix to send email. The server has a static address and I
> > con
* n3mesi83 :
>
> Hello everyone,
>
> I have a java web application that uses JavaMail to send messages with
> attached documents (spreadsheets). On the server (Ubuntu 10.4 64-bit) I
> installed postfix to send email. The server has a static address and I
> connect to it via ssh. Apparently I thou
this message in context:
http://old.nabble.com/Postfix---error-sending-emails-to-some-domains-tp32446527p32446527.html
Sent from the Postfix mailing list archive at Nabble.com.
On Fri, Jul 22, 2011 at 03:35:41PM -0400, Zhou, Yan wrote:
> I am seeing my Postfix 2.3.3 having following error.
This is 5+ years out of date.
> It may appears to
> be problem connecting to LDAP (which uses TLS extension),
LDAP over TLS is best attempted with a modern software stack.
> but I
Hi there,
I am seeing my Postfix 2.3.3 having following error. It may appears to
be problem connecting to LDAP (which uses TLS extension), but I tried
running postmap and the output shows that it is successfully lookup
domain from LDAP. There are other Postfix servers successfully
connecting to
On 9/2/2009 12:43 PM, Postfix wrote:
Hi,
It seems when a mail box file gets to about 49MB, postfix will start
giving the error:
"can't create user output file" when trying to send mail to that account.
Is there a setting for this somewhere in postfix? I can't seem to find
one in the main.cf file
Hi,
It seems when a mail box file gets to about 49MB, postfix will start giving the
error:
"can't create user output file" when trying to send mail to that account.
Is there a setting for this somewhere in postfix? I can't seem to find one in
the main.cf file about it.
I didn't have a problem w
* Carl A jeptha :
> Sorry Mr. Tandon,
> That uid belongs to amavis and I followed the Postfix setup on the
> Ubuntu network.
>
> So a little more understanding please, as I have been thrown in the deep
> end with this problem, I do RF for a living, not setting up Postfix
> mailservers with sp
Sorry Mr. Tandon,
That uid belongs to amavis and I followed the Postfix setup on the
Ubuntu network.
So a little more understanding please, as I have been thrown in the deep
end with this problem, I do RF for a living, not setting up Postfix
mailservers with spamassassin and clamav.
You hav
On Mon, 20 Jul 2009, Carl A jeptha wrote:
> Here is the error:
>
> Jul 20 11:39:38 mail amavis[14802]: (14802-01) (!)WARN: DSPAM problem, exit
> 1, result=
> Jul 20 11:39:45 mail dspam[14849]: Option --user requires special
> privileges when user does not match current user, e.g.. root or Trusted
Hi,
Thank you for the support over the weekend, server is working fine, but
am still having a problem with the spam settings:
Here is the error:
Jul 20 11:39:38 mail amavis[14802]: (14802-01) (!)WARN: DSPAM problem, exit 1,
result=
Jul 20 11:39:45 mail dspam[14849]: Option --user requires spec
Thank you, thank you, thank you !
Uninstalled 'sendmail', 'sendmail-cf' packages. Restarted the 'postfix' and
every thing works now.
Wasn't paying attention to the 'sendmail' keyword in the logs. Don't know
why ... I had Postfix working for a while and quit working after some config
changes, may
On Fri, 06 Feb 2009, mantra UNIX wrote:
> # mailx -s "test email" test-...@test.domain
> # tail /var/log/maillog
> ...
> Feb 6 17:09:53 abc-host sendmail[11601]: n16N9rC7011601: from=root,
> size=48, class=0, nrcpts=1, msgid=<
> 200902062309.n16n9rc7011...@abc-host.localdomain>, relay=r...@loc
mantra UNIX:
> Feb 6 17:09:53 abc-host sendmail[11601]: n16N9rC7011601: from=root,
That is NOT POSTFIX.
Wietse
Hi,
Problem:
==
Unable to send outbound mail using 'postfix'.
Error Message:
===
Feb 6 17:09:53 abc-host sendmail[11601]: n16N9rC7011601: from=root,
size=48, class=0, nrcpts=1, msgid=<
200902062309.n16n9rc7011...@abc-host.localdomain>, relay=r...@localhost
Feb 6 1
85 matches
Mail list logo
