On Sat, 24 Oct 2009, Daniel Spannbauer wrote:
> virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
>
> My script mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf:
>
> user = mailuser
> password = somepassword
> hosts = 127.0.0.1
> dbname = mailserver
> query = SELECT 1 FR
t;
> --
>
> Best regards,
>
> Charles
>
>
> __ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version
> 4539 (20091024) __
>
> E-Mail wurde geprüft mit ESET NOD32 Antivirus.
>
> http://www.eset.com
>
__ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4539
(20091024) __
E-Mail wurde geprüft mit ESET NOD32 Antivirus.
http://www.eset.com
On 10/24/2009, Daniel Spannbauer (dspannba...@web.de) wrote:
> when I do a postmap -q domain.com
> mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
>
> I get back the ID of my Domain-Entry in the Mysql-DB. So I think the domain
> is found.
Please don't make claims, post proof...
Copy/paste th
static:5000
> >
> > My script mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf:
> >
> > user = mailuser
> > password = somepassword
> > hosts = 127.0.0.1
> > dbname = mailserver
> > query = SELECT 1 FROM virtual_domains WHERE name='%s'
ything seems to be ok, but when I
> send a mail from a MDA over smtp, I get the Mail back with the messages that
> it loops back to the server.
>
> Can anybody help me to find the error? I search for a week now and can't
> find it.
>
> Regards
>
> Daniel
>
>
>
> __ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4538
> (20091024) __
>
> E-Mail wurde gepruft mit ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
___ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4538
(20091024) __
E-Mail wurde gepruft mit ESET NOD32 Antivirus.
http://www.eset.com
The Postfix LMTP server does not perform final delivery. You are
welcome to provide pointers to the email RFCs that say that Postfix
is nevertheless responsible for adding final delivery message
headers.
The lmtp_assume_final feature does not make Postfix responsible
for final delivery. It modifie
> return-path is added upon final delivery.
>
> Wietse
Thank you for the answer. So do you think it should be done by LDA (dspam,
or dovecot deliver)? Or is there any point to change postfix daemon's
behavior by option like "lmtp_assume_final=yes"?
Alex.
return-path is added upon final delivery.
Wietse
Hello everyone.
I have tired to googling this, but didn't found anything userful.
I have next configuration:
postfix (2.6.5). dspam 3.80. dovecot 1.2.
/etc/postfix/main.cf:
virtual_transport = lmtp:unix:/var/run/dspam/dspam.sock
dspam is daemon mode, listen this socket and after checks use dove
ram:
> delay=180, delays=0.11/0/0.1/180, dsn=4.4.2, status=deferred
> (conversation with 202.162.240.2[202.162.240.2] timed out while sending
> message body)
Wietse:
> > You have set your SMTP client timeouts TOO LOW.
> > A timeout of 180s for DATA/END_OF_DATA is insane.
>
> No I have kept them a
Le 24/10/09 à 10:41, Noel Jones a écrit :
> You probably need to add permit_mynetworks to the other
> smtpd_*_restrictions sections you have defined.
Thanks, it was smtpd_sender_restrictions
> If you need more help, show "postconf -n" output as requested
> in the list welcome message.
Sorry,
On 10/24/2009 10:26 AM, Daniel Caillibaud wrote:
I have a pb with some mails (with unknown domains) injected into postfix
locally by fetchmail.
postfix reject smtp transaction when sender domain name is not found, which is
wanted exepted when it's a fetched mail.
I don't want fetchmail send d
On 10/24/2009 8:03 AM, ram wrote:
On Sat, 2009-10-24 at 08:49 -0400, Wietse Venema wrote:
ram:
delay=180, delays=0.11/0/0.1/180, dsn=4.4.2, status=deferred
(conversation with 202.162.240.2[202.162.240.2] timed out while sending
message body)
You have set your SMTP client timeouts TOO LOW.
A
Daniel Caillibaud wrote:
I have a pb with some mails (with unknown domains) injected into postfix
locally by fetchmail.
postfix reject smtp transaction when sender domain name is not found, which is
wanted exepted when it's a fetched mail.
I don't want fetchmail send directly to delivery agen
I have a pb with some mails (with unknown domains) injected into postfix
locally by fetchmail.
postfix reject smtp transaction when sender domain name is not found, which is
wanted exepted when it's a fetched mail.
I don't want fetchmail send directly to delivery agent because I want
spamassas
On Sat, 2009-10-24 at 08:49 -0400, Wietse Venema wrote:
> ram:
> > delay=180, delays=0.11/0/0.1/180, dsn=4.4.2, status=deferred
> > (conversation with 202.162.240.2[202.162.240.2] timed out while sending
> > message body)
>
> You have set your SMTP client timeouts TOO LOW.
> A timeout of 180s for
ram:
> delay=180, delays=0.11/0/0.1/180, dsn=4.4.2, status=deferred
> (conversation with 202.162.240.2[202.162.240.2] timed out while sending
> message body)
You have set your SMTP client timeouts TOO LOW.
A timeout of 180s for DATA/END_OF_DATA is insane.
Wietse
Stan Hoeppner:
> the time, Ford Motor company wasn't so lucky. They had upgraded all
> their SLES9 VMware guests to SLES10 and discovered this bug in
> production. Ouch!
That seems to be an operations problem. I may be old-fashioned,
but I let a new OS or HW run through its paces for some time
We use postfix to accept mails at our MX servers and relay it to
scanning servers for spam & virus checking
The problem is last week , I had the smtp service on MX servers hanging
while trying to relay some messages. Both sending and receiving servers
run postfix 2.5.1
Oct 24
20 matches
Mail list logo
