Tag Info

New answers tagged

1

That's a bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796488 Wait for it to be fixed and use the package from jessie in the meantime.


0

This happens because Google recently implemented a policy change, which in their own words, is one in a series of changes to strengthen email authentication, and end any practices by Google products which break authentication. There are many options being suggested such as to change the ports for the smtp server, to enable "allow less secure apps" option ...


1

You didn't mention the other email client you're trying to use, but since you have some SRV records, I'll assume it supports auto discovery. It looks like there's a little bit of confusion with some of your records. This one is fine, although some might frown upon using a CNAME, for non-autodiscovery (i.e. you manually enter pop.my_domain in your email ...


2

It is telling you your license isn't valid. (LAK = License Activation Key) You'll need to take that one up with PowerMTA support.


3

These are not error messages but debug messages and are clearly marked as these. Unless you need verbose_ssl to debug a problem you should just switch it off. More background: it is showing every state it is going through when doing an SSL handshake. To display the description of the state it is using the function SSL_state_string_long from OpenSSL. This ...


0

Brian, Without knowing any details at all, here's what I would do to test. Assumptions: DNS: example.com in mx mx.example.com ;(we'll say spam filter that forwards to smtp.example.com) mx.example.com. in A 10.0.0.125 example.com. in TXT "v=spf1 10.0.0.0/24 ~all" mx.example.com. in TXT "v=spf1 a -all" idrac.example.com. in TXT "v=spf1 a -all" ...


2

You might be able to do an strace to dump all running Apache processes to a file and then once the spam goes out, see if you can track down what was going on (such as by saving frequent dumps of server-status using mod_status if it's not obvious from the strace by looking at file paths). You could try something like the following - though note it may be ...


2

I overcome this issue after a long time. In routers section wrote my own custom router that will deliver email to my desired php script. In transport section wrote my own custom transport that will ensure delivery to the desired script using curl. Just wrote the following configurations in my /etc/exim.cnf file: ############ROUTERS runscript: driver ...


0

You have to create two routers where first should have unseen verb. That first router have to pipe message to the script while the second have to perform usual delivery to the user's mailbox. Sorry for brief answer, I'm posting from phone.


0

Simple. Was looking for the same and it dawned on me. Use another smtp server to drop the eml files into its queue by telling it to send to a non existing smtp relay. Have a bat process or what have you pick them up deleting the failed delivery log and then process them and place into the working smtp servers pickup folder. Done.:)


0

Faced same issue, bugzilla was showing that it sent the email but nothing was received fixed by setting: use_mailer_queue to "off"


2

As I expected, the solution to this was tremendously simple: /etc/dovecot/conf.d/10-auth.conf includes two files: auth-system.conf.ext for system users, and auth-mydomain.conf.ext for virtual users. The order these files are included is important important, system users lookup after virtual users is easily performed by swapping both lines: [...] !include ...


5

In the general case, it is not possible to do what you are asking for. It is also explicitly discouraged in the standard governing Internet email. It might be possible in some specific scenarios, but those will be highly specific. (Likely depending on specific software in used, software configuration, etc.) The reason for this is that the email message ...


0

On your receive connector be sure to check that right: ms-Exch-SMTP-Accept-Any-Recipient Removing that right will make your server answer an 550 5.7.1 Unable to relay error to remote host that want to send to a email not in your enterprise. Some admin do make multiple receive connector, and open that right to allow some device to send to external address, ...


0

You have to add some outer IPs to the dc_local_interfaces. Now exim hasn't legal way to communicate with other MTAs.


-1

blat is a really simple solution. Works for me on Windows SBS 2011. Here is what I used to send daily report about the server harddisk status: blat status.txt -to recipient@domain.com -subject "HP Server Status" -server smtp.server.com -f sender@domain.com -u user@ourdomain.com -pw mypassword Legend: status.txt - body of an email message -f - "from", ...


-2

It seems that the issue is still there in current versions of postfix. To avoid any trouble with postfix, don't use service postfix start nor /etc/init.d/postfix start to launch it. Instead, use postfix start ; postfix stop ; and postfix status which provide the same functionnalities but actually work.


0

grepmail -hH ^Date: /path/folder | grep ^Date: | tail -1 grepmail -hH ^Date: /path/folder: -h requires the match be in the header, -H prints only the headers of matching emails (ie, all of them)... | grep ^Date:: from those headers, extract only the Date: lines... | tail -1: and print only the last of those.


1

I saw this behavior several times. Usually it's related to Outlook local cache that contain an invalid entry. You can remove it following this steps : open outlook compose a new email type in the "to:" field the first letter of the email address or name, until it show you the record you are looking for click the cross right to the name You can also ...


0

As a starting point you could do something like this to find the From line at the start of the last mail. tac "$MAIL" | grep -m1 '^From ' A line starting with From indicates the starting point of a mail within the mbox file. It also contains the time at which it was received, which is usually more reliable than any other timestamp found within the mail ...


0

Since you need something that understands the actual mbox format the canonical mail client mail or the customary more capable replacement mailx come to mind. mailx -f /path/to/mbox -H Since new messages are appended that should list your messages in order of reception.


1

Currently your email is going to mx0.123-reg.co.uk and mx1.123-reg.co.uk as indicated by the MX records in your DNS zone. If you want your email to go to the host named mail.yourdomain.com (as represented by the A record in your DNS zone) then you need to change the MX record(s) to reflect that. The MX record is used to designate the host or hosts that ...


0

The procedure also applies to Exchange 2013. just in case here is also the link for Exchange 2013: https://technet.microsoft.com/en-us/library/bb125177%28v=exchg.150%29.aspx In this article it is also explained on how to move the mail.que fail to an alternate location.


3

You can execute spamassassin with debugging/tracking dns queries. It will track dnsbl (and dnswl) queries. spamassassin -D dns < mail_message_file


0

olRuleActionDefer is not Supported when creating new rules programmatically, As a workaround, try to create a new olRuleSend type rule and Apply the olRuleActionDefer to it, I have not tested it but i think it's possible Creating Outlook rules through Powershell is explained and exemplified by The Scripting Guy here.


2

Okay, so maybe I was a little hasty in posting this question. It turns out, this works great: /usr/sbin/sendmail -i -t -f postmaster@example.org So, the real solution is then to use the mail.force_extra_parameters flag, and set it to -fpostmaster@example.org Just make sure you don't test using the cli php.ini, expecting the apache php.ini to work. ...


2

The first line of the dovecot error indicates it doesn't have permission write to /var/mail/. This indicates the dovecot is running under an account without permission to write to the folder. /var/mail/ is owned by root:mail (UID/GID 0:8), giving full read/write/execute permissions to both root and the group mail. Dovecot is running under nicolai to access ...


3

The security of your current setup against interception, and consequently possible disclosure and modification, of your mails on their way from your server to the destination mailbox, depends on the security of your server's DNS resolution. If an attacker is able to forge DNS replies to your server she can divert your mails to her own TLS-enabled SMTP ...


1

I believe I've solved this problem, and hoping that this will serve as help for others who encounter this issue. A little disappointed that there wasn't a lot of help here, but I guess the act of writing it out may have helped. Anyway: In main.cf, the myorigin and mydestination variables need to be set to localhost. So: myorigin = localhost mydestination = ...


-1

Sounds like you were basically running an open relay and after a while, some spam bot found it and started launching emails through it. Theres a couple of Postfix settings to close your server down. One is the permitted networks option. I usually only permit local 'known' networks and then add any other network ranges to the local list that I need. The ...


3

Since you have dovecot you can do that with doveadm(1). For example deleting mail saved in the Trash folder for user before 30 days: doveadm expunge mailbox Trash savedbefore 30d -u <user> You can use -A flag for all users and if you want to check first for the mails that match use the search/fetch commands - see doveadm-search(1): doveadm search ...


1

Script away in your favourite monitoring toolkit! You need: a scheduled job that sends a SMTP message (for instance every minute) and then monitor the recipient mailbox via POP or IMAP (every X minutes) to see if it has received any new messages in the last X minutes (and delete those to prevent the mailbox from filling up). No (new) messages ...


5

$ORIGIN defines a base value from which 'unqualified' name (those without a terminating dot) substitutions are made when processing the zone file. The @ symbol is a short-hand for the $ORIGIN in zone files. Using the short-hand @ or the full name example.com. is therefore equivalent. $ORIGIN can be specified explicitly in the zone file, but is often ...


1

We tried to deliver your message, but it was rejected by the server for the recipient domain example.com by mail.example.com If that's the A record of your OLD server as you pointed out in your question, there's your answer. You can't send email to your "Gmail for Work" account (let's say bob@example.com) and expect your old mail server that isn't ...


-2

This seems to be related to the SMTP server you are using to send email. Not the MX record the rest of us are using to send you emails. There isn't a lot of information in your question but the error 550 relay not permitted by administrator is pretty clear. Your SMTP server is refusing to relay emails using the credentials you provided.


1

As @masegaloeh suggested, here's what I did : In main.cf smtpd_sender_restrictions = check_sender_access mysql:/etc/postfix/mysql-virtual_sender.cf This tells postfix to perform the check_sender_access restriction on every sender before mail is sent. mysql:/etc/postfix/mysql-virtual_sender.cf contains the necessary SQL query to perform the check. If the ...


0

That log only shows that xinetd received a request on the port that is associated to smtp and sent it to the smtp process. Since you're on centos, if you want to see user login activity you'll have to look at the /var/log/wtmp file using the utmpdump command.


0

This line only tell us that you are getting a connection to xinited server "awaking" the smtp server by a connection requested form the given ip. Take a look on the smtp server log on what is the operation the daemon is being requested. The provided information won't give us any clue regarding what you ask, and is likely to be voted down if you don't add ...


5

Does it mean that someone is using my username (MYEMAIL@example.com) to send spam? YES This log line was the proof of it. Aug 4 11:09:17 mail postfix/smtpd[71597]: 1AE3B7EC3D: client=unknown[59.88.35.206], sasl_method=PLAIN, sasl_username=MYEMAIL@example.com As you have permit_sasl_authenticated in main.cf, then you authorize anyone who knows your ...


4

The log shows that someone has obtained the password for the mail account MYEMAIL@MYDOMAIN.COM and is using it to send SPAM through the server. The entry at time 11:09:17 shows a successful SASL authentication from IP address 59.88.35.206 with username MYEMAIL@MYDOMAIN.COM. The entry at 11:09:30 shows reception and queuing of a message with sender address ...


0

Our problem was caused by this script: https://github.com/hbattat/verifyEmail edit for context: I added the above script to our server to try and validate emails since we had so many bouncing emails, this script will go to the remote host check for mx records then try and interface with the email server and find out whether the specified email address ...


1

After hours and reading that the lookup result is discarded for a minimum of eight times, I finally realized, that the stored funciton I use to check the existence of a user returns 0 when no matching entry is found. And that means to Postfix, well, that the user was found.


2

The log entries you posted don't appear to show an outgoing delivery attempt. The e-mail to email@gmail.com looks like it got delivered locally, which would tend to indicate something extremely screwed up in virtual_domains, since your mail server appears to think that it should receive mail for gmail. Beyond that, who knows what mysteries mail-in-a-box ...


3

In short, include will normally just result in a match (if pass) or otherwise a non-match for negative results (or possibly an error in error conditions). The specific action, beyond pass / non-pass, in the included record is irrelevant. From the include section of the SPF spec: +---------------------------------+---------------------------------+ | ...


2

Let me quote the other excellent answer by James Sneeringer from the other question:mail loops back to myself | postfix This happens when domain.com has an MX record (or, in the absence of an MX, an A record) that points to your Postfix server, but your Postfix server is not configured to accept mail for that domain. From the quote above, basically ...



Top 50 recent answers are included