I went to the mxtoolbox site and, indeed, the system is now blacklisted

at 11 sites. I didn't see any way to get off the blacklists now that

the system is properly configured. Is there a way to do this? Ie, how

do I remove it from those lists?

These have to be done one at a time.  Go to each blacklist and it should tell you how this is done.  In some cases a blacklist has no method of being removed, it's either done automatically after X period of no spam or manually when the operator finally decides you are no longer spamming.

 

You're right - it only accepts mail if it arrives to

something@tugraz.at, not if it is addressed to

something@mail.tugraz.at. I guess that means I cannot enter a fixed IP

in Mercury for this domain, right?

Yes, however you might talk to the people running the mail.tugraz.at server about accepting literal addresses.   It's generally not that big a change to the system setup and they can still put these into the MX queue for the tugraz.at server.

The server is up again since a few days. I'm currently in Australia therefore it took me a while to get it fixed.Sorry for the inconvenience!

Best regards,

Nico

I tried using IMAP but the client I use is Windows Live Mail.  I keep getting an error message 80070057 using IMAP w/ Merc. and have narrowed it down to the the windows option of "Use the deleted folder for IMAP accounts".  If it is unchecked IMAP works great but you can't retrieve any deleted messages.  But, if checked an error message keeps popping up when clicking on any IMAP folder.

 

How do I use an alias to run a rule when I don't want to change the actual email address?  I've tried using the actual address x.xxx@domain.org as the alias and pointing it to the general rule but I get an error telling me that "the address x.xxx@domain.org is not known at this site".  I've also used a local user name and that seems to work.  I receive the email on the client and see that the message was sent to my blackberry but the message never makes to the hand held device.

Turn on session logging for MercD and capture a log of an attempt.

Turn off session logging again as it can eat up disk space.

Examine the log for clues as to what the problem is.

[quote user="Davife"]

They would send messages from the PHP script.  The recipient would then be able to reply to the 'alias' address.  In reading the alias documentation, I think that will work however, I have 3 more questions.

1) Can I add a new user through a PHP script?

[/quote]

 By aliasing the @yourdomain address to their real (own external) address you could avoid having to create local users.

[quote]

2) If so, can I create an alias at that time or do I have to use MALIAS?

3) Are the messages forwarded via the alias mechanism available so that I can show a record of all messages between 2 users on the website?

[/quote]

Yes. You would create a global filter rule that 'Always' triggers and 'Copy' each mail to a local user (called say "ARCHIVE") that you can access via your own mail client, via IMAP might be a good choice.

It's a known bug and it will be fixed in version 4.73 that is now being prepared.

/Rolf

Update: I tried connecting via secure connection with my Windows Mobile device while I was watching the SMTP server window.  It shows 2 failed login attempts each time I attempted to send a message:

Connection from xxx.xxx.xxx.xxx

(High ASCII characters)

 

Connection from xxx.xxx.xxx.xxx

EHLO Inbox

QUIT

 

 

There are lots of links around about file access problems in Windows 7. Have a look at this one, for instance, or try to google for it:

http://www.addictivetips.com/windows-tips/windows-7-access-denied-permission-ownership/

/Rolf

There are a number of different actions available to a rule set. "Copy" makes a copy of the original message in the selected local mailbox. "Move" writes the message to a local mailbox and ends handling of the message. So always copy to user1 and always move to user2 should cover it. 

/Rolf 

I posted a question a while back here: http://community.pmail.com/forums/thread/19136.aspx

I think I have found why this has been happening occasionally. I found that the most recent one that caused this build up of messages that said they could not be sent - which related to one message in particular) was sent from an ID in Pegasus that I rarely use. I did a bit of digging into this and discovered that at some point somehow the sender's mail address and reply to address had been deleted from the Options and Internet Options. This would explain a rejection or failure to send, I imagine.

I am posting this as it could help someone in the future.

I have no idea why an id would lose these settings but that would be another topic for the Pegasus Mail forum another day. The point is that I have discovered the reason for some of my messages never arriving at their destination and the build up of messages in the Mercury Queue folder.

Cheers!

Ellie

This is a common problem. You need to tell the socket stack not re-use the socket, f.ex. by setting the socket idle timout on your session to a very low value (like 1 second).

This is what it looks like when coding C# in .NET

MailMessage msgMail = new MailMessage(); 
msgMail.To.Add("address"); 
msgMail.Body = "test"; 
SmtpClient Client = new SmtpClient(); /* uses settings from web.config */
Client.ServicePoint.MaxIdleTime = 1; /* without this the connection is idle too long */
Client.Send(msgMail); 
msgMail.Dispose();

A download link has been sent!

In most cases the X-Envelope-To header will provide the wanted information, but move and copy rules bypass that. To make the forward action work as expected you would need to add a header with a different name, for instance X-Rcpt-To, before the rule with the forward action.

/Rolf

 

Thank you!

Stefan. 

You can't with an SMTP transaction filter as it is the From: address in the message body.

The SMTP MAIL FROM that you are checking with your rule is <> as reported in the Return-path: header

From transflt.mer:

[quote]# "operation" can be:
#
#    'H' for an expression applied to the client's "HELO" greeting
#    'D' for deferred HELO processing; these filters will only be
#        applied if the client does not issue a successful AUTH after
#        issuing HELO but before issuing any other command. Otherwise,
#        these filters are the same as 'H' filters. They allow a user
#        on a system that might otherwise be rejected to redeem the
#        connection by authenticating his identity.
#    'S' for an expression applied to the subject line of the message
#    'R' for an expression applied to each SMTP RCPT command
#    'M' for an expression applied to the SMTP MAIL FROM: command[/quote]

You can use a general filter rule during Core Processing to match the From: address in the body and delete it.

Thank you for the reply. I did have debug logging enabled in SpamHalter while I was troubleshooting the problem and it was enabled on the configuration page.

I was able to trick the program into operating once or twice which proved it was alive, but nothing further. I've removed it from the system and moved on to other issues.

Thanks again for the suggestions.

If that was real authentication data please change it ASAP!

/Rolf 

When Outlook and Exchange communicate they use a proprietary (and complex) MS-RPC based messaging protocol (unless you set them up to use IMAP or POP3, losing all the advanced capabilities of both). RPC does not work well across firewalls, that's why now Outlook supports RPC over HTTP. Basically, it tunnels the proprietary RPC communication inside HTTP, to allow for using Outlook outside the firewall without the need of using a VPN to contact the Exchange server. There is now way you can use it with Mercury, it is a standard SMTP/IMAP/POP server, it doesn't "speak" Exchange protocol.

I'm confused that it appears to be talking to the AVG anti-virus POP3 server but then, when it fails, the sign-off comes back as being from the Exchange server. Have you tried disabling the AVG POP3 server while testing?