New answers tagged

0

This sounds like either an MTU problem or just maybe an in-line application firewall problem. If the packet that the remote end never acks is the first packet above say 1350 octets, then it is very probably an MTU problem. To check, you can try sending a long text without any attachment (several thousand bytes). If there have been same-sized (or even bigger) ...


0

No. A webmail page is just a normal web page. Of course, you could try to scrape the site and find file names and HTML fragments that can be associated with a webmail product, but this not reliable at all. Why do you want to do this anyway?


0

Woah, never though to propose that someday, Lotus Domino ! That fill your need for the address book and calendar. It got webaccess and can run on linux/AIX.


0

we use Zimbra and are quite happy with it, but if your organization really needs using outlook instead of the webaccess, then I would recommend against using anything but Exchange. The outlook connector for zimbra mostly works, but has issues (https://forums.zimbra.org/viewforum.php?f=20&sid=6203d84ecffa9b3c2cc5fd897b0c15c6) which may, or may not, be ...


2

The 3 digit error codes come from the original SMTP specification RFC 821. The dot separated error codes are RFC 3463 compliant which was drafted because those SMTP error codes were deemed insufficient: There is a need for a standard mechanism for the reporting of mail system errors richer than the limited set offered by SMTP and the system ...


0

You also don't even need a "MX" Record, if no MX record is found it will default to your "A" record. So your mail server and domain name can be the same name if you want it to be. Check out Unlock The Inbox, if you're setting up a mail server for the first time, they have a lot of useful information.


3

It doesn't matter. You must only be sure that the record value point to the correct IP, only technical reason to use something like mail.example.com instead of just example.com is because the mailserver and the webserver CAN be a different servers (with different IP).


2

Sendmail assumes that it is "very likely" that the connection came through an open http proxy. It would be "unwise" from spam prevention perspective to send standard "unrecognized command" reply and accept next SMTP commands. [It is implemented in srvrsmtp.c] HTTP proxy server may send/relay valid SMTP commands embedded into HTTP request. Without this ...


3

It's always a surprise to learn that it is obviously not common knowledge how the System Administrator (of an Email Server) and all his C-Level buddies can know about you and your communication going on in your company. GPG as mentioned in detail above is obviously one option - and you are right: your users could be the ones taking care of it. As soon as ...


3

I'm just looking for something that provides some form of smokescreen against careless admins. Short answer: no, you can't. If you dealing with admins the first, last and only one defence is end2end encryption. So GPG is the answer. Who has root access to the server (should) have it because they need it, and probably known how services are configured ...


-1

https://packages.debian.org/sid/dovecot-lmtpd apt-get install dovecot-lmtpd


0

You can use Office 365 Message Encryption. Users have to login with either a Microsoft account or a one-time PIN code to view the message. You can disable the PIN code option to enhance the security. It won't know any recipient details like SSN though.


1

From postfix's main.cf file: The myorigin parameter specifies the domain that locally-posted mail appears to come from. The default is to append $myhostname, which is fine for small sites. If you run a domain with multiple machines, you should (1) change this to $mydomain and (2) set up a domain-wide alias database that aliases each user to ...


2

I haven't personally used the Microsoft Azure Rights Management service, but it should fit into your requirements to protect the data just nicely. IT won't ask for a PIN or code, but it I believe that it's a better solution for ease of use. https://channel9.msdn.com/Series/Information-Protection/Azure-RMS-user-experience ...


2

After a tonne of investigation, I've tracked down the cause. Logwatch processes /usr/share/logwatch/dist.conf/logwatch.conf after processing /usr/share/logwatch/default.conf/logwatch.conf. Inside /usr/share/logwatch/dist.conf/logwatch.conf was three config lines: mailer TmpDir MailFrom It was here that MailFrom was set to root which was causing the ...


0

Might be a bit late now, but I found that I had to specify folders with dots instead of slashes: eg. 'fileinto "Test.default"'.


-1

You can certainly set up a computer with postfix (or any number of other mail servers, for that matter) to send mail. But that is no guarantee that you will not be grey/blacklisted if you are flagged as engaging in behaviour deemed suspicious. There are many ways to minimise this risk, however, in terms of configuring your postfix (or whatever you choose) ...


0

I just started experimenting with this myself, but I believe that in your case you need to replace these lines: protocol imap { mail_plugins = "autocreate" } plugin { autocreate = Trash autocreate2 = Sent autosubscribe = Trash autosubscribe2 = Sent } With: namespace inbox { inbox = yes mailbox Trash { auto = subscribe # autocreate and ...


1

You really shouldn't use the customers email as the "Sender", it's going to cause all kinds of authentication issues. Maybe use it as the "reply-to" field. You can read more about that here: The Contact Us Form Nightmare


0

to resolve this problem: open your php.ini from php example : c:/xampp/php/php.ini add extension=php_com_dotnet.dll to the extensions in php.ini file if you are using this tool to control a microsoft office document make sure that microsoft office is installed in your windows server and don't forget that the COM tools works only on windows servers like ...


1

https://grox.net/doc/postfix/html/faq.html#paranoid warning: xxx.xxx.xxx.xxx: address not listed for hostname yyy.yyy.yyy Postfix uses hostnames in its junk mail and mail relay controls. This means that in theory someone could be motivated to set up bogus DNS information, in order to get past your junk mail or mail relay controls. When Postfix ...


0

In the simplest case, the mail server at mail.example.com would receive The mail server should accept mail to postmaster and abuse for it's domain (or any other), but need not accept any other addresses for that domain. In a simple setup, it is acceptable to receive mail at either domain. It is up to the mail administrator to configure how to handle ...


1

Untrusted TLS connection established to gmail-smtp-in.l.google.com I think you have a certificate chain error here. Make sure you are sending the intermediate certificate along with your certificate.


1

if you type zmprov view quota in your favorite search engine the first hit you find is: https://wiki.zimbra.com/wiki/Getting_All_Users_Quota_Data which to me really does what you need.


1

@Stefan You seem very knowledgeable which is awesome, I looked over your headers, without your domain name it makes it very hard to help troubleshoot. The one thing I did notice in your headers is that you're using "Simple/Simple" to sign your DKIM, you should really switch that over to "Relaxed/Relaxed". A lot of mail servers have trouble with simple. ...


2

That's a good question, based on SSL Stats from Unlock The Inbox, it seems to suggest about 93 percent of all email servers that sent it incoming email support TLS on port 25.



Top 50 recent answers are included