Tag Info

New answers tagged

0

Take a backup of the existing outlook profile by exporting it into pst file and suggest you to setup new profile with imap settings. Once outlook/email client is setup with new account, please import pst file into this new profile which should then sync with server.


0

Old emails will be deleted once the server comes back online with an empty account. Copy the emails to PST file, then when your server is back online and both accounts are sync copy them back in.


0

You need to change your hosts_require_auth and hosts_require_tls options to the following: hosts_require_auth = <; $host_address hosts_require_tls = <; $host_address The problem will occur when using IPv6 to send. When sending with IPv6, $host_address will be an IPv6 address and will therefore contain colon characters (:). Colon is usually used ...


3

4 - handle the bounce. Generally the best approach is to cause the bounce to go to some sort of bounce-handling process so that persistently bouncing recipient address can ultimately be pruned out of your database. Which could be a .forward for "alice", or adjusting the envelope sender to be a handler process. Whether or not "alice" cares whether the ...


0

What you can do is setup an haproxy on your debian vps, and put a config like: frontend email_fake bind 127.0.0.1:25 default_backend email_remote [...] backend email_remote (all your options here) server x.x.x.x:25 # this is the IP address of your second vps Another option is use postfix's transport to map messages delivery. The configuration is very ...


1

Here the proposed mail-flow-diagram for your case. External mail server | ▲ | | POP3 SMTP | | ▼ | Local mail server First, you need setup working local mail server with postfix and dovecot. The important parameter for postfix is never list your local domain in relay_domains. You can use virtual_mailbox_domains ...


0

If mydestination is empty or does not contain $myhostname then the /etc/aliases will be ignored because postfix thinks the email is not a local delivery and will therefore not apply the local aliases. So, leave mydestination at the default (postconf -d mydestination or remove it from main.cf) and the logs should show the to=<...> as your aliased ...


3

If the second server is only outbound for applications, and Google Mail is for inbound and outbound (i.e. normal usage by users), then there is no need to touch the MX record. Just add the IP of the second server to a SPF Record, which requires access at the DNS level of your domain. There are several wizards online to assist you in the syntax. ...


0

Technet has all the information you could want: Reference Depending on your preference for a GUI or PowerShell you can follow the instructions to create a new discovery search against a mailbox or against the entire organization. You can put the items on in-place hold if needed. With your search results in hand, you can then export the items to a PST or ...


3

If your server has been compromised, the intruder may not be using services that log where you can see those logs. If you're getting complaints from your provider about spam being sent from your server, I would take them seriously and assume that the server has indeed been compromised. To anticipate your next question, see How do I deal with a compromised ...


-1

I have found a solution : Open a cmd on the server type the following commands : set timeout = 55 That's worked for me.


0

Tips to make sure your mail doesn't go to spam: Make sure the plain text and html mail contain the same content Use DKIM Don't use "test" in the body/title (I've noticed from personal experience this does not help your spam score) To test, create a new gmail account and see if the message gets into the spambox Send real messages when testing, short ...


2

I discovered the following documented under ACL return codes: If the ACL for MAIL returns “discard”, all recipients are discarded, and no ACL is run for subsequent RCPT commands.


1

Thanks. Not so familiar yet with the SF Eco System. TMI on SF and on the Internet about trying to achieve what I want and after spending a day or two or three researching and hacking, I have fairly got it all sorted out. \----- virtual_alias_maps [root@gateway1 postfix]# cat main.cf | grep virtual.regexp virtual_alias_maps = ...


0

By reading your previous question thread, I gather that you are using exim. My suggestion then would be to configure it as a "send-only" MTA. I've personally used this guide to quickly configure send-only mail servers on public networks. Basically what it does is refuse external connections to the smtp port. I know it is not the most "standard" way of ...


1

If you are going to send from their mail servers, and have a spare IP address available, I would recommend using an alternate IP address instead. That way, if there is any fallout and you are blacklisted for whatever reason, at least it won't affect the IP address(es) used by their mailservers.


4

While a large number of bounced message can surely raise some concerns by antispam services, typically this is only one of the input used to determine if a server is sending spam. I think that if you spread your massive 100.000+ sending in a reasonable amount of time (48+ hours) and all other things as PTR, SPF and similar are OK you should not have big ...


0

Basically, what the mime_header_checks directive does it to instruct postfix to check an external table (/etc/postfix/blocked_attachments, in your case) for a matching pattern and action. But to correctly use it you should really read the relevant postfix man page


1

In general, I agree that #1 is probably the best solution, you can just discard any returns at the server. Install a .forward that sends messages to /dev/null. It's unlikely your bandwidth bill will hurt. To the wider discussion as to whether you should care about messages not being delivered, I don't really know anyone processing their own returns at any ...


3

Using option #1 is always the better solution. Think of it like paper mail; a functioning return address is mandatory. Email is only getting more restricted (DMARC, etc) due to spamers taking advantage of the open policy. It's really not that hard to automate dealing with replys you don't care about. But likely less than 10% of email servers are that ...


3

One thing that I note is that the delegation (in the org zone) looks like this: avuna.org. 86400 IN NS ns3.avuna.org. avuna.org. 86400 IN NS ns4.avuna.org. avuna.org. 86400 IN NS ns2.avuna.org. avuna.org. 86400 IN NS ns5.avuna.org. avuna.org. ...


0

All the configuration above are correct and also the 2 tutoriels mentionned above are very useful. The problems was caused by the permission in ubuntu. I used "sudo": sudo mail -s "hello" -a /path/file.dat info@domain1.com content of my email is here . cc: Then the script runned.


0

Do you have access to the DNS records for this domain? If so, you need to set up some MX records for domain.de that will point to a mail server capable of handling email for that domain. That mail server could then be configured to forward email to your domain.com address. If there are no MX records for the domain then email won't go anywhere. You can use ...


3

Nginx is being stopped from binding to SELinux pop_port_t ports. It possible is to alter the desired ports to be a type that nginx can bind to, e.g. http_port_t. # for port in {143,993,110,995} ; do semanage port -m -t http_port_t -p tcp $port ; done && semanage port -l -C SELinux Port Type Proto Port Number http_port_t ...


3

Adding some X-Foo: cron header (with the X- prefix!) isn't a problem, you can add them as you like. Edit I forgot about http://tools.ietf.org/html/rfc6648. So scrap the X- part.


0

Set domain.de as alias domain.com if possible on your hosting provider. Set mail-forwarding for domain.de on your Registrar (domain.de) if possible. Use free mail service for domain.de (example pdd.yandex.ru) and forward all messages to domain.com. Use cheap VDS for forward domain.de to domain.com (you need have minimal sysadmin skills).


0

Anvil does logging for postfix , Ive added below to main.cf and seems to work for me #### Prevent server sending excess mail from clients add to /etc/postfix/main.cf #### anvil_rate_time_unit = 60s anvil_status_update_time = 120s smtpd_error_sleep_time = 2s smtpd_soft_error_limit = 10 smtpd_hard_error_limit = 20 smtpd_client_message_rate_limit = #### End ...


0

You can use a proxy SMTP address if the message is sent to Exchange through SMTP - in that case Exchange will not change the sender address and will let one of the proxy addresses to be used (you still cannot use an arbitrary address of course). Proxy Manager (http://www.dimastr.com/proxyman/) does that - it is implemented as an Outlook addin, so to an end ...


1

Do a tail -f on maillog, pipe it into your program and look for delivered statements. Then, you'll not be interfering with the system's spam filtering, and will only get solid hits. You'll also know who received the message - it's in the log file... As for php, well, it's the wrong language for this, but your watching program can launch php to do whatever ...


0

UPDATE ok then this could be compiled in sources: os_maild/sendcustomemail.c:#define FROM "From: OSSEC HIDS <%s>\r\n" os_maild/sendmail.c:#define FROM "From: OSSEC HIDS <%s>\r\n" use your custom name, and then run ./install.sh again, and answer yes -> update.


0

You can use -a switch in order to specify additional headers. And an additional header can be From, so it's just what you need. Example: /some_command.sh | mail -s "Email subject" -a "From:Sender Name <sender@email.com>" recipient@email.com


1

Cronjob for both log & email : Run once a month at midnight of the first day of the month: 0 0 1 * * 0 0 1 * * /home/User/script.sh > /home/User/cronlog/`date +\%Y-\%m-\%d-\%H:\%M:\%S`-cron.log 2>&1 ; mailx -s "CronJob is run successfully" someone@domain.com,someone1@domain.com


2

Looks like your initial goal with header_checks is preserving original sender and replace it with allowed sender of Amazon SES. The problem of your approach above is the From: header become non-standard because of multiple quotes in there. From: " "User" <user@gmail.com>" <root@example.com> Daniel R. Tobias mentioned this issue in his ...


2

Just going to quote from my working Postfix configuration: smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauthenticated_sender_login_mismatch, permit Note that this allows authenticated users to send mail with any FROM address they wish. If you want users to be able to send mail only with ...


2

No, for any zone (a.k.a. mail domain), there is a single set of authoritative servers, as designated by the MX records for that zone. If the mailbox does not exist on those servers, an NDR will be generated and sent back to the sending party.


0

Give the host a proper fully qualified domain name. This is one of the many problems that occur when you name a host with the naked domain name.


1

Sending mail via a smarthost is a standard exim4 configuration. This meets the criteria you specify above. Run dpkg-reconfigure exim4-config. Select the option mail sent by smarthost; no local mail. Then configure the second host as the smarthost.


3

To test an ip in senderbase.org database you have to query their dns server for a txt record with a specially constructed domain name. It should be a sequence of bytes in reverse order representing an IPv4 address, encoded as decimal numbers, separated by dots with the suffix .query.senderbase.org. In your particular case: dig txt ...


0

This link can help you , because is official documentation of Apple. https://ssl.apple.com/business/docs/Autofs.pdf


3

Based on this thread on postfix mailing-list: different transport for all mail introduced via sendmail(1), looks like your case was possible. Unfortunately you can't only rely on two tables sender_dependent_relayhost_maps and smtp_sasl_password_maps. You need modify master.cf. The idea is using header_checks to route email to different transport. Then in ...


1

I think what you're looking for is something like Shared Mailboxes. This link might do what you're looking for--it's about transitioning a mailbox to a shared mailbox when someone leaves, and back to a single mailbox when you get the next person. It's for Office365, and you didn't say which version of Exchange you were using, but it looks like you can do ...


1

Yes, you can't have domain in both mydestination and virtual_mailbox_maps. To overcome this you need set mydestination in main.cf mydestination = localhost.$mydomain, localhost and in /etc/postfix/virtual root@domain1.com root@localhost webmaster@domain1.com webmaster@localhost with this setup, email to root@domain1.com will be redirected ...



Top 50 recent answers are included