Search results

thankyou!

Hi there... When I track mail on our proxmox some mail shows as queued/accepted with the following logs: This doesn't seem to show the mail being delivered or attempted to be delivered to the server. Whats the difference between this and accepted delivered?

Hi there.. major issue at the moment where I have put a couple of subdomains : egh.blahblah.com cull.blahblah.com etc into the Relaying list. I've then added them into the transports pane.. But for some reason - any mail to the subdomains tries to go to the default relay. Any ideas?

we have a few customers that get a lot of marketing crap that they want to get rid of. they get about 12 e-mails per day that they have to manually blacklist.. Is there any plans or options available to make it easier & more user friendly to allow the user to get e-mails blacklisted. A lot...

yeah - the subjects are encoding fine. When I send the mail directly - bypassing the proxmox I don't get the issue.

sorry for the delay - it's only in the subject - the main body is unaffected.

We have a weird issue with an irish language client that uses characters like áéíóú. They have an issue where inbound mail coming in through the proxmox the characters are garbled like this : á, é, í, ó ú For internal mail this isn't an issue - for outbound mail that doesn't go...

Now after no changes - back to normal.

Physical Memory (1008MB/878MB) config sent & build : proxmox-mailgateway/2.6/4540

it's unusually high... we had the same load on a physical box and it idled along at 2/3%. Now it's spiking to 90/100%. Version of VMware is vSphere 4 FC with SAS HDD - SAN storage, very very quick.

Now got this when navigating the web interface: Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, postmaster@mox.******** and inform them of the time the error occurred, and...

See the attached screenshot below - my CPU usage is very high. Box is running like a dog :( Any ideas on this - or the error above?

that 'could not connect' error is a secondary issue that I can't really confirm... my main issue is the error: /etc/cron.daily/logrotate: (98)Address already in use: make_sock: could not bind to address [::]:443 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443 no...

Morning! I got this alert yesterday morning and found out this morning that https traffic wasn't working. /etc/cron.daily/logrotate: (98)Address already in use: make_sock: could not bind to address [::]:443 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443 no...

I have a user that isn't getting the daily spam report. The quarantine archive shows she is definitely getting plenty of stuff into the quarantine. She did accidently put the sender address of the spam report into her blacklist- but I have since removed this - but the report mail is still not...

great, thanks! starting the service did the trick...

Getting this tagged in every mail when I look in message tracking: Connection refused /var/spool/proxmox/active/ABC6A24BE7FDFA2B625: No files scanned : ERROR at /usr/share/perl5/Proxmox/Utils.pm line 1601. any ideas?

sorry for my ignorance, but how do I export the syslogs? the error appeared every minute or so, for about an hour. I was having issues with a large amount of spam mail queued trying to go out from inside. Hence my other question, is there a way of deleting mail sitting in outbound queue...

any ideas?

no, OCR is not enabled.