• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

postfix db files

pentabase

Basic Pleskian
I've finally found why email sent to some email adresses keep ending up at *@localhost.localdomain. My postfix db files (virtual.db) are completely filled with all kind of addresses like that.

Can someone tell me how to edit them? in a safe way? It's really annoying to see that some email doesn't reach their destiny.

with regards,

Henk
 
i've already found the way how to on a debian machine. Just copy the virtual.db file from /var/spool/postfix/plesk/virtual.db to a safe spot. Then go to the safe spot and enter the command:

postmap virtual.db > virtual

make a backup of the virtual.db file (like: mv virtual.db virtual.db.backup)

edit the virtual file.

when done, save the file and enter the command

postmap virtual (there will be a new virtual.db file in the directory)

copy the newly created virtual.db to /var/spool/postfix/plesk

restart postfix with the command /etc/init.d/postfix reload

regards
 
dosnt work on my System i just get this errors
postmap: warning: virtual.db, line 78: expected format: key whitespace value
postmap: warning: virtual.db.db: duplicate entry: "?"
 
Hi,

I've figured out how to do this on my debian server:

postmap -s /var/spool/postfix/plesk/virtual > virtual

And then you can edit the newly created virtual file.

I've noticed though that there are a lot of addresses pointing to their @localhost.localdomain equivalent but I don't know if I should change all those addresses or not?
For every domain there are support@, info@, root@, ... addresses, do I have to check all of these email addresses whether they are used or not to know wheter I should change them or can I change them all?

Kind regards
 
Hi Brujo,

Did you happen to get this error fixed? or do you need some help?

thanks got it almost fixed, after cleaning as you described and some days ongoing i have once more entrys like [email protected] [email protected]ldomain this means there is a major bug somewhere.

BTW I found out that localhost.localdomain is related to almost all mailman aliases, postmaster, abuse, info, root, support and so on and that have all domains in common

just to bad all this issues around Postfix

BTW do you have mailinglists running? because my one dosent work

kind regards
Brujo
 
Yeah, at my other work i really enjoy working with postfix. but this upgrade really made me feel like a newbie again. So much trouble.

But i haven't worked with mailinglists in this new version. I will give it a try after christmas.

Hope you can enjoy your holiday. Best wishes from Holland
 
How looks your main.cf?

mydestination = localhost.$mydomain, localhost, localhost.localdomain

thats the only place i found the ocalhost.localdomain stuff


Hope you can enjoy your holiday. Best wishes from Holland

sure i will enjoy anyway, also best wishes from germany

Brujo
 
Mine is exactly the same.

mydestination = localhost, localhost.localdomain

But did you check the virtual.db file? there should be some references to localhost.localdomain.
 
I just created a new domain to play around and right after creating without asigning Mailboxes the entrys in the virtual.db looks like:


so i try to find out where the localhost.localdomain comes from, and even if they are correct, will this addresses redirectet elswhere because there is still no Mailbox?


Brujo
 
Well i guess that plesk or postfix uses a kind of template.

When i have the time i will search for those entries on my server. Just to see if they are hard-coded into a file of in the PSA database of plesk.

but anyways, this story will continue.

Henk
 
after upgrade with hotfix4 all the @localhost.localdomain are back in the virtual.db :-(

therefore you are right this story will continue.

Brujo
 
Thanks for the info. Then I won't install the hotfix. because I don't want the entries back again. I just removed all of them. And i even tried to forward all the @localhost.localdomain to my own address. but it didn't work.

keep me posted. Maybe we can keep in touch by email/msn or something?
 
solution available?

Hi, under Plesk 9.2 I have still an issue with non-working info@... addresses. I get an undelivery report like the one below:

This is the mail system at host <myhostname>.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<[email protected]> (expanded from <info@<realhostname.com>>): host
127.0.0.1[127.0.0.1] said: 550 5.1.1 <[email protected]>:
Recipient address rejected: User unknown in local recipient table (in reply
to RCPT TO command)

Is there any solution/bugfix available related to this issue?

Thanks and Regards
Daniel
 
solution available?

Hi guys,

anyone found a solution related to this issue? Even under 9.2.1 I have suddenly the issue that some [email protected] addresses are no longer working and the sender of the email gets an undeliverable report. This seems to affect mainly [email protected] addresses (also if just a catch all is defined for a domain).

Is there a solution available related to this issue?

Many thanks

This is the mail system at host <myhostname.com>.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<[email protected]> (expanded from <info@<realhostname.com>>): host
127.0.0.1[127.0.0.1] said: 550 5.1.1 <[email protected]>:
Recipient address rejected: User unknown in local recipient table (in reply
to RCPT TO command)
 
Back
Top